review-council

claude-specs

A central, maintained-in-one-place set of Claude Code foundations that other repos pull from, while each repo keeps its own domain-specific agents/rules locally.

It's a Claude Code plugin marketplace. The shared layer ships as the core plugin; your repo's own .claude/ is the local layer and overrides anything in the plugin with the same name. Update centrally here, then git pull lands in every consuming repo with one command.

What core provides

• Agents (explorer, planner, builder, reviewer) — the orchestrator subagent set.
• Command (new-project) — generic sub-project scaffolder.
• Command (init-repo) — seeds a minimal starter CLAUDE.md (+ AGENTS.md pointer) for a new repo's local layer.
• Hook (secret-scan) — blocks Write/Edit/MultiEdit that contain real-looking credentials.
• Hook (session-start) — injects a concise standing directive (orchestrate · prefer existing skills/agents · define-done-then-verify · gate changes · untrusted-content baseline) at every session start.
• Skills (diagnose, write-a-skill, handoff, zoom-out, caveman) — curated engineering/productivity skills vendored from mattpocock/skills (MIT; see plugins/core/docs/THIRD-PARTY-NOTICES.md).
• PRINCIPLES.md — orchestrator model, Karpathy's 4 coding principles, universal operating rules.
• ETHOS.md — builder disposition: search-first + first principles, complete-within-scope, user sovereignty (adapted from gstack).
• settings.json — a small permission allowlist to cut routine prompts.

Install in a repo

/plugin marketplace add vmaia00/claude-specs
/plugin install core@claude-specs

Pull updates (after this repo changes)

/plugin marketplace update claude-specs

This git pulls the local clone and re-syncs the plugin. Bumping version in plugins/core/.claude-plugin/plugin.json is what signals consumers there's a new version.

Local development / testing

Point Claude Code at this folder directly instead of GitHub:

/plugin marketplace add ./claude-specs
/plugin install core@claude-specs
/reload-plugins        # after editing plugin files

Two-layer model

Layer	Lives in	Example
Shared (pulled)	this repo's core plugin	generic builder, secret-scan, principles
Local (per repo)	each repo's .claude/	domain agents/hooks that override the shared ones

See BOOTSTRAP.md to stand up a brand-new repo on these foundations.

Companion tools (install separately, not vendored)

Heavier, dependency-bearing tools that are better consumed as their own installs than vendored into core:

• claude-mem — persistent memory across sessions (captures + compresses session activity, re-injects relevant context). Install: npx claude-mem install.
• graphify — turn a codebase into a queryable knowledge graph (Tree-sitter + NetworkX; Python deps). Sends only semantic content, not raw source.

See research/insights.md for a backlog of further patterns under evaluation.

Releasing & version pinning

Auto-update (track latest) and pinning (lock a version) are opposites — set up both so you can choose per machine/repo.

Cutting a release (do this on every change):

1. Bump version in plugins/core/.claude-plugin/plugin.json. This is mandatory — if the version string doesn't change, Claude Code keeps the cached copy and consumers never see your update.
2. Commit and push main.
3. Tag the release (validates plugin.json agrees with the marketplace entry):

   claude plugin tag ./plugins/core --push -m "core %s"
   

   Creates and pushes core--v<version> (e.g. core--v0.1.1).

Track latest (default, recommended for your own machines): auto-update is enabled per marketplace via "autoUpdate": true on the claude-specs entry under extraKnownMarketplaces in ~/.claude/settings.json (or toggle it in /plugin → Marketplaces). The marketplace re-pulls main at startup; you always get the newest version.

Pin a specific repo to a version (when you want stability): add a ref (tag/branch) or sha to the plugin's source in marketplace.json. sha wins if both are set and survives branch deletion:

{ "name": "core", "source": { "source": "github", "repo": "vmaia00/claude-specs",
  "ref": "core--v0.1.1" } }

A repo using a pinned source ignores newer releases until you move the pin.