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).
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- framework-skill
- description
- 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).
03 SKILL.md 正文
framework-skill — the {aios}-volume index/router (stage 4 of skill2framework)
Ported 2026-07-10 from the proven doc-mirror
generate-framework-skillprompt-skill (score 1.00, FULL_E2E 2026-06-03). Vocabulary update: the generated skill is named{aios}-volume(a SkillVolume — the per-AIOS pattern book; "{aios}-nomicon" is the legacy name). Not itself E2E-scored yet.
The framework skill is an INDEX + DECISION-TREE ROUTER that sits on top of an AIOS: it shows the tree of skills + rules + how they relate (a diagram), tells the agent what to do when, and routes into the AIOS dir. It links the chapter + the plugin.
Steps
- Index the AIOS: read every skill (name + WHAT/WHEN), the rules, the system doc; build the skill tree + the rules table + the relationship DIAGRAM (reproduce/distill the AIOS's own diagram; ASCII or mermaid).
- Write the decision tree: situation → the skill to use; copy-pasteable, not prose.
- Write
SKILL.md(frontmattername: {aios}-volume; keyword-dense WHAT/WHEN): what-this-framework-is ¶ (point at the chapter + plugin) → the index + diagram → the decision tree → ROUTING (explicit paths into the AIOS's skills/rules) → links. - Report: confirm EVERY skill found is indexed (list them), a diagram exists, a decision tree exists, routing paths are real.
Hard constraints
Index + router only — point at the AIOS's skills (canonical reference), never duplicate their content. Ground everything in the actual files; invent nothing.
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).
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).
assemble-chapter
WHAT: assemble a framework CHAPTER from the two rendered blog posts — run skill2framework.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).