メニュー
Orientation when working IN the chaincompiler repo — what the system is, where things live, and the discipline. Use when developing/extending ChainCompiler, ACCC/CORCC/SCCC, skilltree, the SI, the marketplace, or the Skill OS.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | chaincompiler |
| description | Orientation when working IN the chaincompiler repo — what the system is, where things live, and the discipline. Use when developing/extending ChainCompiler, ACCC/CORCC/SCCC, skilltree, the SI, the marketplace, or the Skill OS. |
A compiler-compiler for cognition: a closed algebra over one type, the skill dir
(<name>/SKILL.md). Every layer produces/consumes only that type.
README · ROADMAP · FEDERATION · BACKLOG · roadmap.json # project surface
assets/ · site/ · scripts/ · .github/ # roadmap SVG, site, generators, deploy
packages/ rulecatcher · chaincompiler · accc · corcc · sccc · skilltree · si · honeyc · skillchain-compiler · glyphsteer
.claude/rules/ # architecture diagrams + the discipline
rulecatcher (the gate) is vendored at packages/rulecatcher — zero deps; ./install.sh wires everything.
learn→gate→compile, construct_language(), SKILL.md packager).tree_to_mcp, scaffold_repo.chaincompiler.persona, CLI cc persona FILE) = the front-end that compiles a
glyph-persona-program (BizziBee-style: [VarDefs] legend + ⚙️ workflow + [ROLE] wrapper)
into <cogid>/SKILL.md + legend.json + a rulecatcher-gated chain. Example:
packages/chaincompiler/examples/bizzibee.txt. (Executing the ⚙️ workflow via the SI = aspirational.)packages/glyphsteer) = dual-regime retrieval steering (lexical tag facet +
dense emoji direction), legend authoring, grading; grammar.py gates codes via rulecatcher.
See the glyphsteer / glyphsteer-dense skills.See .claude/rules/10-architecture-components.md and 20-architecture-flows.md for diagrams.
When you finish a unit of work, in the SAME change: tick BACKLOG.md, update
roadmap.json status, add a ## Changelog entry in README.md, and run
python3 scripts/update_site.py. The deploy gate fails the push without a new
changelog entry. See .claude/rules/00-keeping-roadmap-and-backlog-current.md.
./install.sh (rulecatcher first, separately), then pytest in each packages/*.
WHAT: assemble a framework CHAPTER from the two rendered blog posts — run framework.assemble_chapter to copy Blog 1 + Blog 2 verbatim into a self-contained chapter dir, wire the relative cross-links + plugin/skill links + CTAs, and write the chapter.md manifest. WHEN: when Blog 1 + Blog 2 exist and need combining into the publishable chapter unit, or when the user says assemble a chapter / skill2framework (any of).
WHAT: produce Blog 2 of a framework CHAPTER — the mechanical deep-dive ('how it actually works') — for an already-built AIOS/package by reading its impl docs (README architecture sections, design docs, the code's module docstrings) and assembling a faithful mechanics-only article that links back to Blog 1. WHEN: when producing the deep-dive half of a chapter, when you need the technical how-it-works post Blog 1 links to, or when the user says blog 2 / deep dive / skill2framework (any of).
WHAT: the TERMINAL stage — fold a finished framework into the author's SkillTome (the top-level holder + search of all their frameworks) by running framework.fold_into_tome, which registers the framework as a row on a tome volume node's generated ## Frameworks table via skilltree's bind op. WHEN: when a framework package is finished and must be registered in the author's tome/volume, or when the user says fold into the tome / nomicon / skill2framework fold (any of).
WHAT: generate the FRAMEWORK SKILL for an already-built AIOS — the {aios}-volume (its SkillVolume face): one skill that indexes the AIOS's skills + rules + how they relate (as a diagram), gives a decision tree for what to do when, and ROUTES the agent into the AIOS dir. WHEN: when producing the index/router face of a framework package, or when the user says framework skill / volume / skill2framework (any of).
WHAT: produce Blog 1 of a framework CHAPTER — the narrative chapter-opener — for an already-built AIOS/package by reconstructing its journey from its own dir (CLAUDE.md, README, dev log) and FILLING framework.JourneyCore, then rendering with render_blog1 (never hand-write the blog). WHEN: when making a framework/chapter from something already built, when you need the story post that opens a chapter, or when the user says blog organ / narrative blog / skill2framework (any of).
WHAT: package a framework as a Claude Code PLUGIN (its operational face) — run framework.package_plugin to assemble plugin.json + skills/{aios}-volume/SKILL.md + the chapter bundled under resources/, with the skill's chapter links repathed to the bundle. WHEN: when a framework skill + chapter exist and need the installable plugin, or when the user says package the framework / plugin / skill2framework (any of).