← ClaudeAtlas

thalarch-project-brainlisted

Maintains an opt-in, repository-local project knowledge layer for stable architecture, invariants, decisions, regressions, commands, design rules, and project-scoped experience. Use when a project is revisited repeatedly and durable context would reduce rediscovery. Current repository/runtime evidence always outranks the brain; entries carry provenance/freshness; stale facts are retired; secrets and private chain-of-thought are forbidden; and repository files are created or changed only when durable project memory is explicitly authorized.
LUC4N3X/antigravity-thalarch · ★ 2 · AI & Automation · score 65
Install: claude install-skill LUC4N3X/antigravity-thalarch
# Thalarch Project Brain A Project Brain is a **compact project-specific knowledge index**, not a replacement for the source code, tests, repository instructions, or current runtime evidence. ## 1. Activation and authorization Use when: - the repository is worked on repeatedly; - important invariants are expensive to rediscover; - regressions recur; - architecture or product decisions need durable rationale; - project-specific workflows/commands repeatedly matter. Do not create `.thalarch/brain/` automatically during ordinary work. A repository-local durable sink is an external mutation and requires user/project authorization. ## 2. Canonical layout When authorized, prefer this small inspectable layout: ```text .thalarch/brain/ project.md invariants.md decisions.md regressions.md playbooks.md design.md # only when the project has meaningful visual/product rules memory.sqlite3 # optional indexed project memory ``` Do not create empty files merely to satisfy the layout. Add only surfaces the project actually needs. If the repository already has authoritative architecture/decision/runbook documentation, reference or update that system instead of creating a competing source of truth. ## 3. What belongs where ### `project.md` Stable project identity and navigation: - language/framework/toolchain facts with provenance; - important modules/boundaries; - authoritative repository rule files; - verified build/test/lint commands; - pointers to dee