Archcore Plugin

Make your AI code like it already knows your repo.

Archcore gives coding agents the architecture, rules, and prior decisions of this repo — so new changes land where your project says they belong and follow the team's conventions, automatically.

Works in Claude Code, Cursor, Codex CLI, and GitHub Copilot CLI. One source of truth, in Git.

See it work

The agent pulls in the rules and decisions that apply — no command needed — and still gives you the seven skills below for anything explicit.

Commands

Describe what you want in plain English — Archcore routes it. The slash commands below are shortcuts to the same workflows.

Command	Outcome	When to use
/archcore:init	Make your repo legible to AI agents	First-time setup — seeds a stack rule, a run-the-app guide, and imports your CLAUDE.md / AGENTS.md / .cursorrules if present
/archcore:context	Load what's already decided before you change code	Daily, before editing — pulls relevant rules, decisions, specs, patterns, and reference docs for a file, directory, or topic; or --git-changes for the rules governing your uncommitted changes
/archcore:capture	Document what already lives in code	A module, API, pipeline, or integration has tribal knowledge but no doc yet
/archcore:plan	Turn an idea into a scoped implementation plan	New feature, refactor, or initiative — pick depth with --track product|feature|sources|iso
/archcore:decide	Record a decision and (optionally) make it a team rule	A decision was made — capture rationale, consequences, and turn it into an enforced standard
/archcore:audit	Find stale, missing, or drifting docs	Health check — add --deep for a full audit, --drift for code/doc staleness
/archcore:help	Navigate the skill catalog	When you forget which command fits

Install

Archcore plugins require the Archcore CLI on PATH — it serves the MCP server the plugin talks to.

# macOS / Linux / WSL
curl -fsSL https://archcore.ai/install.sh | bash

# Windows (PowerShell 5.1+)
irm https://archcore.ai/install.ps1 | iex

Verify: archcore --version · Update: archcore update · Docs: docs.archcore.ai/cli/install

Then add the plugin in your host:

Claude Code

/plugin marketplace add archcore-ai/plugin
/plugin install archcore@archcore-plugins

Cursor — requires Cursor 2.5+. Open Plugins, paste https://github.com/archcore-ai/plugin into Search or paste link, click Add Plugin. One-time MCP setup: copy docs/cursor.mcp.example.json into ~/.cursor/mcp.json (user-scoped) or .cursor/mcp.json (project-scoped).

Codex CLI — requires Codex CLI v0.117.0+.

codex plugin marketplace add archcore-ai/plugin
codex
# then run /plugins, open Archcore, select Install plugin

GitHub Copilot CLI — installs straight from this repo's plugin subdirectory.

copilot plugin install archcore-ai/plugin:plugins/archcore

Copilot CLI only: VS Code agent mode has no self-serve plugin install, and cloud-agent sandboxes do not load plugin hooks.

On Copilot the plugin brings skills, commands, agents and hooks — but not the MCP server. Copilot launches a plugin's MCP in the plugin's own directory rather than your project (github/copilot-cli#4234), so documents would land in the plugin cache. Register it per project instead:

archcore init --agent copilot --project "$PWD"

Claude Code — load the plugin for the current session:

claude --plugin-dir /path/to/plugin

Cursor — symlink the repo into Cursor's local plugins directory and reload the window:

ln -s /path/to/plugin ~/.cursor/plugins/local/archcore
# then in Cursor: Cmd/Ctrl+Shift+P → "Developer: Reload Window"

Codex CLI — point a local marketplace at the checkout:

codex plugin marketplace add /path/to/plugin
codex plugin add archcore@archcore-plugins

GitHub Copilot CLI — load the plugin directory directly:

copilot --plugin-dir /path/to/plugin/plugins/archcore

Cursor team rollouts — Dashboard → Settings → Plugins → Team Marketplaces → Import (paste the GitHub URL).

Try these first

Open your project and try these three prompts. Each shows a different side of what your agent can now do.

Empty repo? Run /archcore:init first — it seeds a stack rule, a run-the-app guide, and optionally imports your existing CLAUDE.md / AGENTS.md / .cursorrules.

1. "Before I change anything in src/auth/, what should I know?" Your agent sees what's already decided for that path — before it touches the code.

2. "Add a new API handler and follow this repo's conventions." Your agent places the handler where your architecture says it belongs, instead of guessing.

3. "We picked PostgreSQL — record it as a team standard." The decision is captured, codified as a rule, and auto-applied to every future change in the same area. Decisions stop dying in chat scrollback.

What changes after install

❌ Without Archcore

• the agent guesses your folder structure
• re-litigates decisions your team already made
• needs the same conventions repeated in every chat
• loses project truth the moment the session ends

✅ With Archcore

• code lands where your architecture says it belongs
• respects decisions already in Git
• follows team conventions loaded automatically
• reflects new decisions as future guardrails — not markdown graveyards

The agent stops guessing and starts following the system.

Use Archcore when

• Your agent writes code, but not the way this repo expects
• Your CLAUDE.md / .cursorrules / AGENTS.md keeps growing and drifting
• You work with 2+ agents or 2+ host tools (Claude Code + Cursor + Codex + Copilot)
• You want decisions, rules, and specs in Git — not in chat scrollback

Not for — chat memory, a prompt library, or a one-shot spec-to-code generator. Archcore is a repo truth layer for coding agents, not a methodology kit.

Supported hosts

Host	Status	Install
Claude Code	Production	Plugin marketplace
Cursor	Implemented	Plugin marketplace
Codex CLI	Implemented	Plugin marketplace
GitHub Copilot CLI	Implemented	copilot plugin install (subdir spec)

Built on open standards (Agent Skills, MCP) — skills and MCP tools are shared across hosts; only manifests are host-specific.

How Archcore differs

Tool	Category	How Archcore differs
BMAD / Spec Kit / Agent OS	Methodology	Archcore stores artifacts and a living context graph; methodology kits prescribe process.
Superpowers	Methodology	Shapes agent behavior; Archcore provides canonical project knowledge any agent can read.
claude-mem / Mem0 / agentmemory	Memory	They remember what you did; Archcore stores how the system is built and what was decided.
Cline Memory Bank	Docs	Same spirit, lower ceremony. Archcore adds typed relations and validated multi-step cascades.

Pick a methodology tool for an opinionated dev flow. Pick a memory tool for session continuity. Pick Archcore when you want typed, queryable project truth that your coding agent respects on every request.

Uninstall

Claude Code: /plugin uninstall archcore@archcore-plugins Cursor: remove from plugin settings. Codex CLI: codex plugin uninstall archcore GitHub Copilot CLI: copilot plugin uninstall archcore

License & contributing

Apache-2.0 · Issues and ideas: GitHub Issues