Skip to content

.cursor/rules/archon.mdc

Source location: docs/source-files/.cursor/rules/archon.mdc — this page is a rendered mirror; the file is the source of truth.


Archon Decoupling Rules

Archon is a project-agnostic, platform-agnostic meta-capability framework. soul.md (core) and its soul/*.md extensions can be copied directly into any project on any AI coding platform without modification. Commands and agents require only the first-line path prefix to be adapted by the export script (.cursor/.claude/, etc.).

Responsibility Matrix

FileRoleMay contain project specifics?
soul.mdUniversal engineering principles (core, section-scoped hot path)
soul/delivery.mdUniversal delivery-mode extension (loaded by demand)
soul/review.mdUniversal review-mode extension (loaded by plan/review)
archon-demand.mdUniversal delivery workflow
archon-review.mdUniversal review workflow
archon-reviewer.mdUniversal review protocol
archon-*/SKILL.mdUniversal or framework-adjacent Archon skills
blink-dispatch/SKILL.mdUniversal subagent dispatch gate
external-agent-patterns/SKILL.mdUniversal external-framework evaluation guard
docs/archon/*.mdPortable framework reference docs
docs/archon/templates/*.mdProject-state templates and schema contracts❌ for filled project facts; placeholders/examples only
.archon/domain-lenses/**Universal lens/tool contracts
.archon/contracts/*.yamlPortable governance contracts
drift.md rules sectionUniversal drift mechanism
drift.md log sectionThis project's delivery records
manifest.mdThis project's hot context carrier
debt.mdThis project's active debt gate index
memos.mdThis project's stakeholder memory hot index
decisions.mdThis project's ADR ledger

Prohibited Content in Universal Files

Project Specifics (Absolutely Prohibited in Universal Files)

  • Concrete technology/framework names from the adopting project stack
  • Concrete project file paths
  • Concrete shell commands from the adopting project
  • Concrete package names from the adopting project
  • Concrete metric numbers from the adopting project

Platform Path Prefixes (Tiered Restrictions)

File.cursor/, .claude/, etc. platform pathsNote
soul.md / soul/*.md❌ Fully prohibitedPure philosophy, zero path references; use abstract terms ("platform rules directory", etc.)
Command first line✅ AllowedBridge line — declares soul.md, soul/*.md extension, and manifest.md locations; mechanically converted by export script
Command body❌ ProhibitedUse short names (manifest.md, drift.md, debt.md); AI infers the archon directory from the bridge line
Agents❌ ProhibitedUse "in the archon directory" and similar relative descriptions; main agent resolves actual paths when constructing sub-agent prompts
Rules✅ Allowed (frontmatter declaration).mdc / .md formats are inherently platform-specific; converted wholesale by export script

Correct Phrasing

❌ Coupled✅ Decoupled
Specific language strictness modeThe project's type system at its strictest mode
Specific linter rule/package namesLinter + architecture boundary rules
Concrete validation commandThe validation command declared in the manifest
Specific test framework + library namesTest framework + component test library
Concrete source directory nameProject source directory
Concrete quality threshold numberQuality gate thresholds defined in the manifest
.cursor/rules/Platform rules directory
.cursor/skills/Platform skills directory
{platform}/archon/debt.mddebt.md (use short name in body)

Required Post-Edit Check

After every modification to an Archon universal file, scan line by line to confirm no project-specific content or platform-specific paths were introduced (per the tiered restrictions above). Project-state files (manifest.md, drift.md log rows, debt.md, memos.md, decisions.md) may contain project facts, but they must not be copied into portable framework docs unless rewritten as generic examples. The reviewer's checklist already includes this check.

Released under the Apache-2.0 License.