- architecture.md — Layer admission rules, naming conventions, directory structure, and MVP release gate
How skills interact with each other and with the user. Read these before writing a new skill.
- interaction-contract.md — The five-stage skeleton (Intake, Route, Plan, Confirm, Execute) every user-facing skill follows
- artifact-contracts.md — The canonical handoff artifacts between skills, with producers and consumers
- skill-format-contract.md — Required
SKILL.mdfrontmatter fields and sections
JSON schemas for the artifacts live under .claude/skills-impl/shared/contracts/.
- governance.md — How the system stays correct: the governance loop, the Quark-only validation boundary, and the eval upstream evidence rule
- skills_catalog.md — Brief introduction to every user-facing Quark skill (grouped by backend and layer), plus notes and tips on what to watch out for when invoking them