[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWANQTYQMAVKXJCC7G8CFH":3,"skill-same:01M6WWANQTYQMAVKXJCC7G8CFH":83},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6WWANQTYQMAVKXJCC7G8CFH","to-syllabus",null,"Turns a topic, a fixed experienced-developer audience, and a domain into a learning syllabus and a companion technical guide. Use when someone says \"syllabus this\" or asks to create a learning path framed inside a domain.","zero8urn\u002Fagentic-goo","zero8urn","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3292107?v=4","01M6MYMR6FG7W189TD21HH43N7","BDB","01M6MYMRAGFZ28K696F7PP93ZJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36],"syllabus","to syllabus","create","developer","learning","technical","guide","use","domain","framed","companion","path","when","2026-11-10 10:12:30",false,"---\nname: to-syllabus\ndescription: Turns a topic, a fixed experienced-developer audience, and a domain into a learning syllabus and a companion technical guide. Use when someone says \"syllabus this\" or asks to create a learning path framed inside a domain.\n---\n\n# To Syllabus Skill\n\nConverts three inputs — (a) a topic to learn, (b) a domain to frame it in, (c) a fixed audience (experienced developer) — into two documents that serve two different jobs:\n\n- **The Learning Syllabus** — the journey. A sequence of features (\"we build X, then Y, then Z\"), each with an outcome, the concepts it requires, the requirements, and acceptance criteria. **Zero code. STE prose. Tables for density.**\n- **The Technical Guide** — the vocabulary. Named, general coding patterns the journey requires, each explained with a minimal illustrative shape. **Code is allowed here**; it is the code reference.\n\nThe domain is a thin wrapper. Its only jobs are to make the topic fun and give the learner a finish line. It must never become the subject. If a domain would distract more than it frames, simplify it.\n\n## Fixed Audience\n\nThe learner is an **experienced developer**. The syllabus never teaches programming basics: what types are, what a function is, how loops work, and so on. The learner is trusted to work through complex requests. Modern techniques are presented as canonical — no comparisons to other languages, no \"unlearn X\" framing. Side research by the learner is their own business, not this skill's concern.\n\n## Transformation Workflow\n\n1. **Read all input first.** Absorb the topic and the domain. Do not write until both are framed. If the domain was not given, propose a **top-3 bulleted list** of candidate domains suited to the topic (game-related hints are encouraged) and use the learner's pick.\n2. **Determine the finish line.** State, in one to three STE sentences, the finished artifact and what the learner will be able to do. **No stretch goals. No deferred ideas.**\n3. **Decompose the topic into techniques.** List the modern techniques an experienced developer must know to do this topic. Order them by dependency, but keep them as techniques — **not micro-lessons**. These become the technical guide's pattern inventory.\n4. **Decompose the domain into features.** List the concrete things to build (\"we build X, then Y, then Z\"). Keep the list short. Every feature must clearly exist to serve one or more techniques; a feature that exists only to be game-like is scope creep.\n5. **Map features to techniques; run the prerequisite check.** Order the features so that each feature requires only techniques whose patterns already exist in the guide at that point. If a feature secretly needs a technique not yet introduced, reorder the features, simplify the feature, or move the technique earlier. If a technique cannot attach to any feature, drop it from the journey. This is the safety valve — keep it light, do not fragment features.\n6. **Draft the Technical Guide.** Build the named pattern inventory the journey needs. Each pattern: **What it is \u002F Why you use it \u002F The shape \u002F Watch out for**. General and illustrative; never the assembled solution.\n7. **Draft the Learning Syllabus.** One section per feature, in order. Each feature gets: **Outcome**, **Concepts** (mapped to guide sections), **Requirements**, **Acceptance Criteria**. Zero code, STE prose, tables for density. Reference guide sections by stable name.\n8. **Run the reference check.** Every concept named in the syllabus exists as a section in the guide. Every guide section is either referenced by the syllabus or marked as optional reference. Renumber or rename anything unstable.\n9. **Output the documents.** Write the syllabus and the guide to disk using the `assets` templates. No preamble, no explanation — just the documents.\n\n## Syllabus Rules\n\n**Lift-out test.** Every requirement must still make sense when read alone in a ticket or a note without its surrounding week. If a line depends on hidden context, rewrite it until it stands alone.\n\n**Single-claim rule.** Each requirement carries one behavior. Split combined ideas unless they are inseparable parts of one behavior.\n\n### No-Code Rule (structural)\n\nThe syllabus **never contains code fences** — not even one-liners. The `assets\u002Fsyllabus-template.md` has no code slot, so there is nowhere for code to go. Behavior is described in STE prose and in tables, exactly enough to act as a contract.\n\nAllowed inside the syllabus (prose only):\n- Function and type names, referenced as named things, e.g. *\"a function named `renderBoard` that takes the `GameState` and returns a string.\"*\n- Body-level behavior details in prose, e.g. *\"the function loops over the map's `y` then `x`, and in the inner loop it emits the entity glyph at that coordinate if one exists, otherwise the tile glyph.\"*\n\n### Function-Contract Rule\n\nA requirement for a function states, in prose: what it takes, what it returns, and **what happens inside it**. It must rely only on types and functions that already exist from earlier features — never on a type or function that has not been introduced. If a requirement needs something new, that something belongs in an earlier feature or a new Concepts row.\n\n### Acceptance-Criteria Rule\n\nEvery week ends with an acceptance-criteria table. The table is the contract: it must be specific enough that a developer can verify the week without asking a human. Vague phrases such as *\"print the tiles to the screen\"* are rejected; they are replaced with the full behavior. See the example in `references\u002Fexample-syllabus-week.md`.\n\n### Reference-Named Rule\n\nWhen a requirement depends on a coding pattern, it names the pattern and the technical guide section, e.g. *\"model the action as a Discriminated Union (Technical Guide → Discriminated Union).\"* If a pattern is complex, the syllabus points at the guide section rather than explaining the pattern itself — the guide is where code belongs.\n\n## Technical Guide Rules\n\n**Pattern, not implementation.** The guide contains named, general patterns — vocabulary. It never contains the assembled solution to the journey (no working `reduce`, no finished loop, no assembled engine). Assembly is the learner's job, done against the syllabus requirements. The line is: *patterns and their minimal illustrative shapes* yes; *the project's assembled code* no.\n\n**Illustration may use the domain.** A pattern's minimal example may use domain-shaped data (e.g. a `tileKinds` literal union) to make the pattern concrete. It must still read as the general technique, not as a project file.\n\n**Stable names.** Every pattern gets a short, stable name that the syllabus references verbatim. Keep section headings stable; the syllabus links to them by name.\n\n**Per-pattern structure**\n- **What it is**: one to two sentences.\n- **Why you use it**: the situation it solves.\n- **The shape**: a minimal, general code example.\n- **Watch out for**: the common mistakes.\n\n**STE is looser here** than in the syllabus. Richer prose and code are expected. Plain-English clarity still trumps cleverness.\n\n## STE (Simplified Technical English) Rules\n\nApplies most strictly to the syllabus.\n\n- Use short sentences and imperative constructions where natural.\n- Use the same word for the same thing; do not rename a concept mid-document.\n- Remove vague adjectives (`big`, `nice`, `easy`, `simple`). Say what is observable instead.\n- Prefer concrete verbs: *build, returns, loops, rejects, increments*.\n- Type names, function names, and section names are technical names — they are allowed and must be written exactly.\n- If a sentence can be read two ways, split or reword it until it cannot.\n\n## Omission Rules\n\n| Section | Omit When... |\n|---|---|\n| Journey Goal | Never omit — the finish line is required. |\n| A weekly Concepts table | A feature genuinely introduces no new concept (rare; the guide reference is still expected). |\n| A weekly Verification line | The Acceptance Criteria already fully covers verification (prefer omitting over repeating). |\n| Technical Guide optional-reference marks | No pattern is purely optional context. |\n\n## Output Behavior\n\n- Use the formats in `assets\u002Fsyllabus-template.md` and `assets\u002Ftechnical-guide-template.md`.\n- Preserve Markdown heading levels and section ordering.\n- Omit empty optional sections instead of leaving placeholder text behind.\n- Do not include analysis, rationale, or meta commentary about how the documents were produced.\n- When the topic or domain is contradictory, choose the most constrained reading that still fits the repeated signals.\n- The syllabus and technical guide are two separate documents. Do not merge them.\n\n## File Output\n\nWrite both finished documents to disk rather than printing them to the conversation.\n\n**Default output paths**:\n- Syllabus: `docs\u002F\u003Ctopic-slug>-syllabus.md`\n- Technical guide: `docs\u002F\u003Ctopic-slug>-technical-guide.md`\n\n**Filename derivation**: the topic, lowercased, spaces replaced with hyphens, special characters stripped.\n\n**If a destination folder does not exist**: create it before writing the documents.\n","# To Syllabus Skill\n\nConverts three inputs — (a) a topic to learn, (b) a domain to frame it in, (c) a fixed audience (experienced developer) — into two documents that serve two different jobs:\n\n- **The Learning Syllabus** — the journey. A sequence of features (\"we build X, then Y, then Z\"), each with an outcome, the concepts it requires, the requirements, and acceptance criteria. **Zero code. STE prose. Tables for density.**\n- **The Technical Guide** — the vocabulary. Named, general coding patterns the journey requires, each explained with a minimal illustrative shape. **Code is allowed here**; it is the code reference.\n\nThe domain is a thin wrapper. Its only jobs are to make the topic fun and give the learner a finish line. It must never become the subject. If a domain would distract more than it frames, simplify it.\n\n## Fixed Audience\n\nThe learner is an **experienced developer**. The syllabus never teaches programming basics: what types are, what a function is, how loops work, and so on. The learner is trusted to work through complex requests. Modern techniques are presented as canonical — no comparisons to other languages, no \"unlearn X\" framing. Side research by the learner is their own business, not this skill's concern.\n\n## Transformation Workflow\n\n1. **Read all input first.** Absorb the topic and the domain. Do not write until both are framed. If the domain was not given, propose a **top-3 bulleted list** of candidate domains suited to the topic (game-related hints are encouraged) and use the learner's pick.\n2. **Determine the finish line.** State, in one to three STE sentences, the finished artifact and what the learner will be able to do. **No stretch goals. No deferred ideas.**\n3. **Decompose the topic into techniques.** List the modern techniques an experienced developer must know to do this topic. Order them by dependency, but keep them as techniques — **not micro-lessons**. These become the technical guide's pattern inventory.\n4. **Decompose the domain into features.** List the concrete things to build (\"we build X, then Y, then Z\"). Keep the list short. Every feature must clearly exist to serve one or more techniques; a feature that exists only to be game-like is scope creep.\n5. **Map features to techniques; run the prerequisite check.** Order the features so that each feature requires only techniques whose patterns already exist in the guide at that point. If a feature secretly needs a technique not yet introduced, reorder the features, simplify the feature, or move the technique earlier. If a technique cannot attach to any feature, drop it from the journey. This is the safety valve — keep it light, do not fragment features.\n6. **Draft the Technical Guide.** Build the named pattern inventory the journey needs. Each pattern: **What it is \u002F Why you use it \u002F The shape \u002F Watch out for**. General and illustrative; never the assembled solution.\n7. **Draft the Learning Syllabus.** One section per feature, in order. Each feature gets: **Outcome**, **Concepts** (mapped to guide sections), **Requirements**, **Acceptance Criteria**. Zero code, STE prose, tables for density. Reference guide sections by stable name.\n8. **Run the reference check.** Every concept named in the syllabus exists as a section in the guide. Every guide section is either referenced by the syllabus or marked as optional reference. Renumber or rename anything unstable.\n9. **Output the documents.** Write the syllabus and the guide to disk using the `assets` templates. No preamble, no explanation — just the documents.\n\n## Syllabus Rules\n\n**Lift-out test.** Every requirement must still make sense when read alone in a ticket or a note without its surrounding week. If a line depends on hidden context, rewrite it until it stands alone.\n\n**Single-claim rule.** Each requirement carries one behavior. Split combined ideas unless they are inseparable parts of one behavior.\n\n### No-Code Rule (structural)\n\nThe syllabus **never contains code fences** — not even one-liners. The `assets\u002Fsyllabus-template.md` has no code slot, so there is nowhere for code to go. Behavior is described in STE prose and in tables, exactly enough to act as a contract.\n\nAllowed inside the syllabus (prose only):\n- Function and type names, referenced as named things, e.g. *\"a function named `renderBoard` that takes the `GameState` and returns a string.\"*\n- Body-level behavior details in prose, e.g. *\"the function loops over the map's `y` then `x`, and in the inner loop it emits the entity glyph at that coordinate if one exists, otherwise the tile glyph.\"*\n\n### Function-Contract Rule\n\nA requirement for a function states, in prose: what it takes, what it returns, and **what happens inside it**. It must rely only on types and functions that already exist from earlier features — never on a type or function that has not been introduced. If a requirement needs something new, that something belongs in an earlier feature or a new Concepts row.\n\n### Acceptance-Criteria Rule\n\nEvery week ends with an acceptance-criteria table. The table is the contract: it must be specific enough that a developer can verify the week without asking a human. Vague phrases such as *\"print the tiles to the screen\"* are rejected; they are replaced with the full behavior. See the example in `references\u002Fexample-syllabus-week.md`.\n\n### Reference-Named Rule\n\nWhen a requirement depends on a coding pattern, it names the pattern and the technical guide section, e.g. *\"model the action as a Discriminated Union (Technical Guide → Discriminated Union).\"* If a pattern is complex, the syllabus points at the guide section rather than explaining the pattern itself — the guide is where code belongs.\n\n## Technical Guide Rules\n\n**Pattern, not implementation.** The guide contains named, general patterns — vocabulary. It never contains the assembled solution to the journey (no working `reduce`, no finished loop, no assembled engine). Assembly is the learner's job, done against the syllabus requirements. The line is: *patterns and their minimal illustrative shapes* yes; *the project's assembled code* no.\n\n**Illustration may use the domain.** A pattern's minimal example may use domain-shaped data (e.g. a `tileKinds` literal union) to make the pattern concrete. It must still read as the general technique, not as a project file.\n\n**Stable names.** Every pattern gets a short, stable name that the syllabus references verbatim. Keep section headings stable; the syllabus links to them by name.\n\n**Per-pattern structure**\n- **What it is**: one to two sentences.\n- **Why you use it**: the situation it solves.\n- **The shape**: a minimal, general code example.\n- **Watch out for**: the common mistakes.\n\n**STE is looser here** than in the syllabus. Richer prose and code are expected. Plain-English clarity still trumps cleverness.\n\n## STE (Simplified Technical English) Rules\n\nApplies most strictly to the syllabus.\n\n- Use short sentences and imperative constructions where natural.\n- Use the same word for the same thing; do not rename a concept mid-document.\n- Remove vague adjectives (`big`, `nice`, `easy`, `simple`). Say what is observable instead.\n- Prefer concrete verbs: *build, returns, loops, rejects, increments*.\n- Type names, function names, and section names are technical names — they are allowed and must be written exactly.\n- If a sentence can be read two ways, split or reword it until it cannot.\n\n## Omission Rules\n\n| Section | Omit When... |\n|---|---|\n| Journey Goal | Never omit — the finish line is required. |\n| A weekly Concepts table | A feature genuinely introduces no new concept (rare; the guide reference is still expected). |\n| A weekly Verification line | The Acceptance Criteria already fully covers verification (prefer omitting over repeating). |\n| Technical Guide optional-reference marks | No pattern is purely optional context. |\n\n## Output Behavior\n\n- Use the formats in `assets\u002Fsyllabus-template.md` and `assets\u002Ftechnical-guide-template.md`.\n- Preserve Markdown heading levels and section ordering.\n- Omit empty optional sections instead of leaving placeholder text behind.\n- Do not include analysis, rationale, or meta commentary about how the documents were produced.\n- When the topic or domain is contradictory, choose the most constrained reading that still fits the repeated signals.\n- The syllabus and technical guide are two separate documents. Do not merge them.\n\n## File Output\n\nWrite both finished documents to disk rather than printing them to the conversation.\n\n**Default output paths**:\n- Syllabus: `docs\u002F\u003Ctopic-slug>-syllabus.md`\n- Technical guide: `docs\u002F\u003Ctopic-slug>-technical-guide.md`\n\n**Filename derivation**: the topic, lowercased, spaces replaced with hyphens, special characters stripped.\n\n**If a destination folder does not exist**: create it before writing the documents.\n",{"name":5,"description":7},"main","454c51c0c7f4b36be2000915748cca72cf53ddd5",".agents\u002Fskills\u002Fto-syllabus","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo","https:\u002F\u002Fgithub.com\u002Fzero8urn","zero8urn.github.io","2026-11-07 23:02:14",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add zero8urn\u002Fagentic-goo --skill to-syllabus",{"tool":55,"command":56},"bunx","bunx skills add zero8urn\u002Fagentic-goo --skill to-syllabus",{"tool":58,"command":59},"pnpm","pnpm dlx skills add zero8urn\u002Fagentic-goo --skill to-syllabus","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002FSKILL.md",true,[63,69,73,79],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"assets\u002Fsyllabus-template.md","ASSET","资产文件",2348,"https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002Fassets\u002Fsyllabus-template.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"assets\u002Ftechnical-guide-template.md",1548,"https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002Fassets\u002Ftechnical-guide-template.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fexample-syllabus-week.md","REFERENCE","参考文档",4060,"https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002Freferences\u002Fexample-syllabus-week.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fexample-technical-guide-patterns.md",5263,"https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-syllabus\u002Freferences\u002Fexample-technical-guide-patterns.md",[84,101,134,154],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":37},"01M6WWAHG7HBE3KDQ4PREES7QX","to-icebox","Transforms a stream of thoughts, rough conversation, or scattered ideas into a structured feature request document. Use when someone says \"icebox this\".","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fto-icebox\u002FSKILL.md",[],[91,31,92,93,94,95,96,97,98,99,100,36],"to icebox","document","conversation","feature request","ideas","structured","feature","transforms","stream","request",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":115,"publishedAt":37},"01M6WWABC3V41GVRB4Z13T54NJ","righting-software","Juval Löwy's \"The Method\" (Righting Software, 2019) as an operating procedure. Decompose a system by axes of volatility, never by functionality; classify components into the fixed taxonomy (Client, Manager, Engine, ResourceAccess, Resource, Utilities); validate by call chains; then design the project that builds it. Use when the user asks for system design, architecture review, service decomposition, \"The Method\", volatility-based decomposition, or asks how long\u002Fcostly a build will be.","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frighting-software\u002FSKILL.md",[107,112],{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":113,"categoryName":114,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[116,117,31,118,119,120,121,122,123,124,125,126,127,128,129,36,130,131,132,133],"software","righting software","never","decompose","system","system design","call","taxonomy","project","as","Volatility","long","operating","for","architecture review","design","components","architecture",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":37},"01M6WWA5448YBVWMJJ1J2X2YZV","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdocumentation-writer\u002FSKILL.md",[],[141,142,143,144,145,146,147,29,148,149,150,151,152,116,153],"documentation writer","documentation","writer","high","technical documentation","framework","quality","technical writer","expert","documentation expert","structure","authoring","principles",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":37},"01M6WWA0S1MVFR8KXGBXHDBKPK","defensive-architecture-pr-review","Reviews pull request diffs against a legacy codebase using Juval Löwys Volatility-Based Decomposition (The Method). Detects architectural decay, leakage of business-rule volatility, and boundary infractions","https:\u002F\u002Fgithub.com\u002Fzero8urn\u002Fagentic-goo\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdefensive-architecture-pr-review\u002FSKILL.md",[],[161,162,163,164,165,133,166,167,168,126,169,170,171,172,173,174,175,100,176],"defensive architecture pr review","defensive","review","pr","pr review","diffs","pull request","pull","boundary","business","Legacy","decomposition","rule","reviews","codebase","decay"]