Archcore Plugin for AI agents
The plugin adds Archcore skills to your coding agent for planning, documentation, and review. It uses the CLI and the same project documents.
Install plugin
The install script adds the CLI and the plugin when your host CLI is on PATH. Cursor needs plugin setup in its Plugins panel.
If you installed your host later, use its setup step below.
What the plugin adds
Ask in plain language, or use these four shortcuts in order: init, plan, document, review.
/archcore:initRead the repository and create its initial project documents.
/archcore:planScope a feature or refactor before implementation.
/archcore:documentRecord a decision or document existing code.
/archcore:reviewCheck the branch against recorded decisions and rules. Flag stale documents too.
Context between commands
Session hooks provide a recap of project decisions and work in progress. On hosts with pre-write hooks, applicable rules and specs arrive before edits. Other hosts read project context through MCP.
Check your agent’s setup requirements
The plugin runs in four hosts. MCP registration and hooks differ between them.
- Claude Code
- The plugin registers MCP automatically.
- Cursor 2.5+
- Install in the Plugins panel, then register MCP for your project.
- Codex CLI 0.117+
- MCP registration is automatic. Hook availability depends on the installed Codex version and its hooks setting.
- GitHub Copilot CLI
- Run archcore init --agent copilot in each project to connect MCP. VS Code agent mode does not load this plugin.
Keep the instructions you already use
Keep CLAUDE.md, AGENTS.md, .cursor/rules, and docs/. Ask your agent to turn a useful section into an Archcore document, then review the result.
“Turn the database decision in CLAUDE.md into an Archcore ADR.”
Plugin FAQ
Do I need to install the CLI separately?
Yes. The plugin calls archcore from your PATH; it does not download the CLI. Install the CLI once, then follow the host-specific steps above.
Which agents are supported?
Claude Code, Cursor 2.5+, Codex CLI 0.117+, and GitHub Copilot CLI. Cursor needs MCP registration; Copilot needs project-level wiring. The host table above explains these differences.
What are the plugin's commands?
/archcore:init, /archcore:plan, /archcore:document, and /archcore:review. They cover setup, planning, recording decisions, and checking changes. You can also ask in plain language.
Can I use my own CLI install?
Yes. Put your chosen archcore binary on PATH before starting the coding agent. You can use an installed release or a build from source.
Where do my docs live?
In .archcore/ inside your repository, as Markdown with YAML frontmatter. You review and commit them with your code. Your coding agent's provider settings govern any context it sends to its model.