[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGKQFFWAX75TRMDA90GKEN":3,"skill-same:01M6JGKQFFWAX75TRMDA90GKEN":71},{"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":28,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6JGKQFFWAX75TRMDA90GKEN","article-outline",null,"Outline before draft — the text's purpose, its Diátaxis type, audience, style forks and sections, agreed before a word of body text. Use when a text (article, doc page, guide, report) is being planned, or when a draft is about to start without an agreed type and reader.","muratovv\u002Fai-hats","muratovv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7502801?v=4","01M6JGCBN4KEJX012GPJVSH04T","Fedor Muratov","01M6JGCBSNMN7CW3RGTPPE0MN2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Farticle-outline\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"outline","article","article outline","report","start","doc","Word","text","page","reader","guide","use","draft","type","style","about","2026-11-10 10:12:30",false,"---\nname: article-outline\ndescription: >-\n  Outline before draft — the text's purpose, its Diátaxis type, audience,\n  style forks and sections, agreed before a word of body text. Use when a\n  text (article, doc page, guide, report) is being planned, or when a\n  draft is about to start without an agreed type and reader.\nlicense: MIT\n---\n\n# Article Outline\n\nSettle what the text is, whom it serves and how it will be styled before\ndrafting. The outline is the text's plan; the draft follows it.\n\n## When to Use\n\n- A text is being planned, or a draft is about to start and nobody has said\n  what type it is and who reads it. A draft that already exists is\n  `prose-review`'s job.\n- With a task card, the outline is its own `## Outline` section in the plan,\n  written and agreed before the draft starts. It ADDS that section — it never\n  fills one that already has an owner (Requirements, Steps): an outline is the\n  text's own shape, not the task's requirements or its work breakdown.\n  Without a card it goes to chat and is agreed there before the draft.\n\n## Procedure\n\n1. **Purpose.** One sentence: who reads this and what they leave with. It\n   becomes the text's lead.\n2. **Type — one Diátaxis quadrant**, held for the whole text:\n\n   | Quadrant    | The reader wants to    | Shape                                           |\n   | ----------- | ---------------------- | ----------------------------------------------- |\n   | Tutorial    | learn by doing         | ordered steps, one working result, no options   |\n   | How-to      | solve a task they have | goal → steps → verification; assumes competence |\n   | Reference   | look something up      | one structure per item, complete, no narrative  |\n   | Explanation | understand why         | argument: claim → reasons → consequences        |\n\n   A text serving two quadrants is two texts, or one with a named split.\n3. **Audience.** One line: what they already know, what they don't, what they\n   came to do. It decides which terms get defined and which steps get skipped.\n4. **Style forks** — each settled as a line in the plan, before drafting:\n   reference format (inline \u002F numbered \u002F footnote); voice (first person \u002F\n   impersonal, imperative \u002F descriptive); code blocks (the reader runs \u002F the\n   agent ran \u002F illustration only); links (first mention \u002F every mention);\n   terms source (a glossary, or \"this text defines its own\").\n5. **Sections.** One heading per reader gain, one line each: what the reader\n   gets here. No gain, no section. In a tutorial the sections are the steps;\n   in a reference they are the items.\n6. **Agree** the outline with the author. Body text starts after that.\n\n## Completion\n\n- Purpose sentence, one quadrant, audience line, style forks and sections\n  with gains are written into the plan's `## Outline` (or chat) and agreed.\n- Validation — RED: asked for \"an article about worktrees\", the agent starts\n  drafting a tutorial-explanation hybrid for an unnamed reader. GREEN: it\n  returns the outline first and asks for one decision — the quadrant.\n\n## Anti-Patterns\n\n- Drafting first and outlining backwards.\n- \"Overview\" as a section's gain.\n- Two quadrants in one text without a named split.\n- Style forks settled silently — each one costs a review round later.\n","# Article Outline\n\nSettle what the text is, whom it serves and how it will be styled before\ndrafting. The outline is the text's plan; the draft follows it.\n\n## When to Use\n\n- A text is being planned, or a draft is about to start and nobody has said\n  what type it is and who reads it. A draft that already exists is\n  `prose-review`'s job.\n- With a task card, the outline is its own `## Outline` section in the plan,\n  written and agreed before the draft starts. It ADDS that section — it never\n  fills one that already has an owner (Requirements, Steps): an outline is the\n  text's own shape, not the task's requirements or its work breakdown.\n  Without a card it goes to chat and is agreed there before the draft.\n\n## Procedure\n\n1. **Purpose.** One sentence: who reads this and what they leave with. It\n   becomes the text's lead.\n2. **Type — one Diátaxis quadrant**, held for the whole text:\n\n   | Quadrant    | The reader wants to    | Shape                                           |\n   | ----------- | ---------------------- | ----------------------------------------------- |\n   | Tutorial    | learn by doing         | ordered steps, one working result, no options   |\n   | How-to      | solve a task they have | goal → steps → verification; assumes competence |\n   | Reference   | look something up      | one structure per item, complete, no narrative  |\n   | Explanation | understand why         | argument: claim → reasons → consequences        |\n\n   A text serving two quadrants is two texts, or one with a named split.\n3. **Audience.** One line: what they already know, what they don't, what they\n   came to do. It decides which terms get defined and which steps get skipped.\n4. **Style forks** — each settled as a line in the plan, before drafting:\n   reference format (inline \u002F numbered \u002F footnote); voice (first person \u002F\n   impersonal, imperative \u002F descriptive); code blocks (the reader runs \u002F the\n   agent ran \u002F illustration only); links (first mention \u002F every mention);\n   terms source (a glossary, or \"this text defines its own\").\n5. **Sections.** One heading per reader gain, one line each: what the reader\n   gets here. No gain, no section. In a tutorial the sections are the steps;\n   in a reference they are the items.\n6. **Agree** the outline with the author. Body text starts after that.\n\n## Completion\n\n- Purpose sentence, one quadrant, audience line, style forks and sections\n  with gains are written into the plan's `## Outline` (or chat) and agreed.\n- Validation — RED: asked for \"an article about worktrees\", the agent starts\n  drafting a tutorial-explanation hybrid for an unnamed reader. GREEN: it\n  returns the outline first and asks for one decision — the quadrant.\n\n## Anti-Patterns\n\n- Drafting first and outlining backwards.\n- \"Overview\" as a section's gain.\n- Two quadrants in one text without a named split.\n- Style forks settled silently — each one costs a review round later.\n",{"name":5,"license":15,"description":7},"master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Farticle-outline",1,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add muratovv\u002Fai-hats --skill article-outline",{"tool":63,"command":64},"bunx","bunx skills add muratovv\u002Fai-hats --skill article-outline",{"tool":66,"command":67},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill article-outline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Farticle-outline\u002FSKILL.md",true,[],[72,98,123,143,167,181],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":45},"01M6PVFB1SM738R2SRSRSF7CY6","tool-evaluation-protocol","Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML\u002FLLM frameworks, testing approaches), or following up on a hype-driven recommendation.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Ftool-evaluation-protocol\u002FSKILL.md",[],[79,80,81,82,83,84,85,86,87,88,40,89,90,91,92,93,94,95,96,97],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","dependency","up","frameworks","time","project","recommendation","for","bounded","candidate",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":45},"01M6PVF7HATBEX1G7N50E2QT57","systematic-debugging","4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[105,106,107,108,79,109,110,111,112,113,40,114,115,116,117,118,119,120,121,122],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","with","bug-fix","phase",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":45},"01M6PVF3MTQN3RPF73AN34856J","skill-template","Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-template\u002FSKILL.md",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[133,134,135,136,137,112,39,40,138,117,139,140,141,95,142],"template","skill template","validation","compliance","hats","new skill","structural","canonical","which","Existing",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":45},"01M6PVF06SCV28QARM5MQPANC9","skill-optimization","Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-optimization\u002FSKILL.md",[149],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[151,152,153,154,155,156,157,158,159,160,40,161,162,163,164,165,166],"Optimization","skill optimization","components","component","issues","library","audit","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":45},"01M6PVEXM9717016T9MW82HDCT","silent-fallback-gate","PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsilent-fallback-gate\u002FSKILL.md",[],[174,175,176,177,178,179,40,180,95],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":188,"publishedAt":45},"01M6PVESM49C5NT7SB7N3F76VS","retro-to-framework","Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fretro-to-framework\u002FSKILL.md",[187],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},[189,190,191,192,154,193,194,195,160,112,40,196,197,93,198,44,199,200,201,202],"framework","retro","retro to framework","change","retrospective","projects","convert","incident","across","problem","more","skill update","single","generic"]