project-spinelisted

# Project Spine — orientation Project Spine is a context compiler. It takes a **client brief** (`brief.md`), an **existing repo**, and optional **design-system inputs** (`design-rules.md`) and compiles them into a machine-readable operating layer the team and coding agents can both work from. ## Conceptual model (memorise this) ``` brief.md ─┐ repo/ ─┼──▶ spine.json ──▶ AGENTS.md + CLAUDE.md + copilot-instructions.md + project-spine.mdc design.md ┘ architecture-summary.md scaffold-plan.md · route-inventory.md · component-plan.md qa-guardrails.md · sprint-1-backlog.md · rationale.md ``` Key properties: - **Deterministic.** Same inputs → same `spine.json` hash. No LLM calls in the compile pipeline. - **Source-pointed.** Every generated rule carries `source: { kind, pointer }` traceable to `brief.md#…`, `repo-profile#…`, `template:…/…`, or `inferred:…`. - **Drift-aware.** An `export-manifest.json` records sha256 of every input and export; `spine drift check` detects when reality drifts from what was compiled. ## When to reach for this tool Match any of these and use a Project Spine skill: - User wants to **create or refresh `AGENTS.md` / `CLAUDE.md` / `.github/copilot-instructions.md` / `.cursor/rules/project-spine.mdc`** for a real project. - User mentions a **client kickoff**, **agency starter**, or **project brief**. - User asks how to **save templates across projects** or **onboar