explain-something-fractally
Skillchain — ac:fractal-top-pass → ac:fractal-per-part-pass → cor:fractal-explainer → FractalExplanation
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- explain-something-fractally
- description
- Skillchain — ac:fractal-top-pass → ac:fractal-per-part-pass → cor:fractal-explainer → FractalExplanation
02 资源文件 1
- 参考文档chain.json352 B
03 SKILL.md 正文
explain-something-fractally — compiled skillchain
Compiled by
skillchain.py. Orchestrates 3 step(s) composing 3 skill(s). Dependencies (validated present at compile time):fractal-explainer,fractal-per-part-pass,fractal-top-pass
Execute the steps below in order. Carry each step's result forward; where a step references {var}, substitute the captured value from the named earlier step.
Step 1 — invoke skill fractal-top-pass
ExplainSomethingFractally top-pass AC — the LFP roll-up outer loop — give the one-breath Overview, enumerate EVERY part (the expected-complete set), define each part, roll up to the least fixed point → hold Compose (the whole reads as one figured-out thing).
Invoke the fractal-top-pass skill (no extra input)
Step 2 — invoke skill fractal-per-part-pass
ExplainSomethingFractally per-part AC — the fractal move — take one Part, define its what/when/how/utility, ask whether it needs its own pass → hold RecurseOrClose (re-enter this same chain on the part, or close it; the explanation is done only when every branch has closed — the fixed point).
Invoke the fractal-per-part-pass skill (no extra input)
Step 3 — invoke skill fractal-explainer
Chain-of-reasoning (spoken, ends in a decision) — explain anything as an LFP roll-up — overview, enumerate the parts, define each part (what/when/how/utility), recurse into any part that needs its own pass until the fixed point closes, then compose the whole granularly.
Invoke the fractal-explainer skill (no extra input)
Done
Return the final step's output as the result of this chain.
04 同仓库更多 Skills
skill2framework
Turn an already-built AIOS/package into a framework chapter — narrative blog + deep-dive blog → chapter → {aios}-volume index skill → plugin → folded into the author's SkillTome.
package-plugin
WHAT: package a framework as a Claude Code PLUGIN (its operational face) — run skill2framework.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).
narrative-blog
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 skill2framework.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).
framework-skill
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).
fold-into-tome
WHAT: the TERMINAL stage — fold a finished framework into the author's SkillTome (the top-level holder + search of all their frameworks) by running skill2framework.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).
deepdive-blog
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).