ZacharyZhang-NY
86aa6fdb29
Skills no longer come from the user's ~/.agents library - most users have none, and the CEO branch that compiled the entire catalogue into its prompt overflowed the model context (1.1MB) and failed every CEO run. - Bundle "built-in skills/" with the app (extraResources) and stage it at startup into <profile>/builtin-skills as one dir-per-skill copy - both bundle shapes (SKILL.md dirs and flat category .md files) normalize into the same importable layout - Import the staged catalogue per org at startup and inside onboarding, so the CEO's first run already carries it - Forced house style: resolveRuntimeSnapshot unions the humanizer skill into every agent's runtime (CEO included) as a resolution rule - no binding row to forget, delete, or bypass; revoke_skill refuses it - CEO staffs hires with skills: hire_agent accepts a skills array, grant_skill/revoke_skill adjust later, list_skills now shows descriptions from skill frontmatter - Kill the c_suite compile-all branch; everyone resolves bindings-only, capped at 200k chars with omissions named in the prompt - Remove the Skills settings page and its import/sync/test IPC surface; drop ~/.agents discovery and the AGENTCOMPANY_NEW_SKILLS_ROOT seam in favor of AGENTCOMPANY_NEW_BUILTIN_SKILLS_DIR - Tests: staging/import/forced-resolution/cap units, real-bundle CI check, e2e asserts the tab is gone and the catalogue self-imports
39 lines
729 B
Markdown
39 lines
729 B
Markdown
# Cursor Integration
|
|
|
|
Converts the full Agency roster into Cursor `.mdc` rule files. Rules are
|
|
**project-scoped** — install them from your project root.
|
|
|
|
## Install
|
|
|
|
```bash
|
|
# Run from your project root
|
|
cd /your/project
|
|
/path/to/agency-agents/scripts/install.sh --tool cursor
|
|
```
|
|
|
|
This creates `.cursor/rules/<agent-slug>.mdc` files in your project.
|
|
|
|
## Activate a Rule
|
|
|
|
In Cursor, reference an agent in your prompt:
|
|
|
|
```
|
|
@frontend-developer Review this React component for performance issues.
|
|
```
|
|
|
|
Or enable a rule as always-on by editing its frontmatter:
|
|
|
|
```yaml
|
|
---
|
|
description: Expert frontend developer...
|
|
globs: "**/*.tsx,**/*.ts"
|
|
alwaysApply: true
|
|
---
|
|
```
|
|
|
|
## Regenerate
|
|
|
|
```bash
|
|
./scripts/convert.sh --tool cursor
|
|
```
|