Cursor integration
A2C supports AI tools such as Cursor through repository rules, prompt packs, optional adapter wrappers, and (when shipped) the a2c-vscode-extension thin client.
Product surfaces
| Surface | Repository | Package | Role |
|---|---|---|---|
| Engine + AI workflows | a2c-workflow | a2c_core | Orchestration, schemas, contracts |
| CLI | a2c-workflow | a2c_cli | Headless commands — also bundled in extension |
| TUI | a2c-workflow | a2c_tui | Textual interactive UI |
| IDE extension | a2c-vscode-extension | — | Webviews, host shims — invokes bundled CLI (ADR-0007) |
Cursor is a VS Code–compatible host. The extension targets Cursor without duplicating workflow logic in extension code.
Method-repo design (a2c-workflow)
| Layer | Location | Role |
|---|---|---|
| Canonical docs | docs/, AGENTS.md | Authoritative policy |
| Rules | rules/ | Machine-usable constraints |
| Prompts | prompts/ | Bounded execution instructions |
| Shared adapters | cursor/rules/*.mdc | Thin pointers for consuming projects |
| Repo governance | .cursor/rules/*.mdc | Rules for editing this repo only |
Plain Markdown is preferred over tool-specific lock-in. Adapters summarize and link — they do not duplicate full policy inline. Runtime assets live in a2c-workflow (ADR-0005).
Bootstrap in a consuming project
- Copy or mount
AGENTS.md,rules/,templates/,prompts/froma2c-workflow - Materialize
cursor/rules/adapters (copy or symlink script) - Add project-local
.cursor/rules/overlays for exceptions - Point agents at the project's commit plan under
plans/ - Verify ADR-0000 exists
Agent execution constraints
A2C treats AI as an ergonomic layer over architecture and contracts — not a substitute for them. See workflow/ai-principles.md for the short mental model.
Instruct agents to:
- start from specs and accepted ADRs
- generate docs before code
- scaffold only approved structure
- proceed in small phases per the commit plan
- stop after the planned batch
- avoid speculative extras
- use
adr(<category>): ...for architectural decisions
Prompt entry points
| Task | Prompt |
|---|---|
| New project bootstrap | pathname:///a2c-assets/prompts/bootstrap/master-bootstrap.md |
| Docs-first phase | pathname:///a2c-assets/prompts/bootstrap/docs-first-bootstrap.md |
Inputs intake (drafts in inputs/) | pathname:///a2c-assets/prompts/bootstrap/inputs-intake.md — see workflow/inputs-intake.md |
| Legacy repo adoption | pathname:///a2c-assets/prompts/bootstrap/legacy-adoption.md — see workflow/legacy-adoption.md |
| ADR work | pathname:///a2c-assets/prompts/phases/adr-create-update.md |
| Implementation batch | pathname:///a2c-assets/prompts/phases/implementation-batch.md |
@ references in Cursor
You do not need to copy prompt bodies into chat. Type @ and pick the prompt file (or path), then add a one-line task:
@prompts/bootstrap/inputs-intake.md
Start batch-intake-00: inventory inputs/ and produce a migration plan.
When A2C method assets are mounted at tools/ai-rules/, use @tools/ai-rules/prompts/bootstrap/inputs-intake.md instead. See workflow/inputs-intake.md.
Updating after workflow version bump
When a2c-workflow releases a new version:
- Review changelog and ADR updates upstream
- Update mounted or copied assets in the consumer
- Add a superseding ADR if the project adopts a new major workflow version