[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72XPCF3YHPC60MQENYADGXJ":3,"skill-same:01M72XPCF3YHPC60MQENYADGXJ":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72XPCF3YHPC60MQENYADGXJ","hads",null,"Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.","steph-frtech\u002Fclaude-code-up","steph-frtech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F198466323?v=4","01M72XD213FVQA2QXRGTJFKHE1","01M72XD227AANJ993SQTNZB1CK",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fmarketplaces\u002Fwshobson\u002Fplugins\u002Fdocumentation-standards\u002Fskills\u002Fhads\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: hads\ndescription: Use when writing technical documentation that needs to be readable by both humans and AI models, converting existing docs to HADS format, validating a HADS document, or optimizing documentation for token-efficient AI consumption.\n---\n\n# HADS Claude Skill\n**Version 1.0.0** · Human-AI Document Standard · 2026 · HADS 1.0.0\n\n---\n\n## AI READING INSTRUCTION\n\nThis skill teaches Claude how to read, generate, and validate HADS documents.\nRead all `[SPEC]` blocks before responding to any HADS-related request.\nRead `[NOTE]` blocks if you need context on intent or edge cases.\n\n---\n\n## 1. WHAT IS HADS\n\n**[SPEC]**\n- HADS = Human-AI Document Standard\n- Convention for Markdown technical documentation\n- Four block types: `**[SPEC]**`, `**[NOTE]**`, `**[BUG]**`, `**[?]**`\n- Every HADS document requires: H1 title, version declaration, AI manifest\n- AI manifest appears before first content section, tells AI what to read\u002Fskip\n- File extension: `.md` — standard Markdown, no tooling required\n\n---\n\n## 2. BLOCK TYPES\n\n**[SPEC]**\n```\n**[SPEC]**   Authoritative fact. Terse. Bullet lists, tables, code. AI reads always.\n**[NOTE]**   Human context, history, examples. AI may skip.\n**[BUG]**    Verified failure + fix. Required fields: symptom, cause, fix. Always read.\n**[?]**      Unverified \u002F inferred. Lower confidence. Always flagged.\n```\n\nBlock tag rules:\n- Bold, on its own line: `**[SPEC]**`\n- Content follows immediately (no blank line between tag and content)\n- Multiple blocks of different types allowed per section\n- Titled BUG blocks allowed: `**[BUG] Short description**`\n- No nesting of blocks inside blocks\n\n---\n\n## 3. REQUIRED DOCUMENT STRUCTURE\n\n**[SPEC]**\n```markdown\n# Document Title\n**Version X.Y.Z** · Author · Date · [metadata]\n\n---\n\n## AI READING INSTRUCTION\n\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified — treat with lower confidence.\n\n---\n\n## 1. First Section\n\n**[SPEC]**\n...\n```\n\nRequired elements in order:\n1. H1 title\n2. `**Version X.Y.Z**` in header (first 20 lines)\n3. AI manifest section before first content section\n4. Content sections (H2), subsections (H3)\n\n---\n\n## 4. HOW CLAUDE READS HADS\n\n**[SPEC]**\nWhen encountering a HADS document:\n1. Find and read the AI manifest first\n2. Read all `[SPEC]` blocks — these are ground truth\n3. Read all `[BUG]` blocks — always, before generating any code or config\n4. Read `[NOTE]` blocks only if `[SPEC]` is insufficient to answer the query\n5. Treat `[?]` content as hypothesis — note uncertainty in response\n\nToken optimization: for large documents, scan section headings first, then read only `[SPEC]` and `[BUG]` blocks in relevant sections.\n\n---\n\n## 5. HOW CLAUDE GENERATES HADS\n\n**[SPEC]**\nWhen asked to write documentation in HADS format:\n\n1. Start with header block (title, version, metadata)\n2. Add AI manifest — always include, never skip\n3. Organize content into numbered H2 sections\n4. For each fact: write as `[SPEC]` — terse, bullet or table or code\n5. For each \"why\" or context: write as `[NOTE]`\n6. For each known failure mode with confirmed fix: write as `[BUG]`\n7. For each unverified claim: write as `[?]`\n8. End with changelog section\n\nContent rules for `[SPEC]`:\n- Prefer bullet lists over prose\n- Prefer tables for multi-field facts\n- Prefer code blocks for syntax, formats, examples\n- Maximum 2 sentences of prose — if more needed, move to `[NOTE]`\n\nContent rules for `[BUG]`:\n- Always include: symptom, cause, fix\n- Optional: affected versions, workaround\n- Title on same line: `**[BUG] Short description**`\n\n**[NOTE]**\nWhen converting existing documentation to HADS: extract facts into `[SPEC]`, move narrative and history to `[NOTE]`, surface all known issues as `[BUG]`. Do not duplicate content between block types.\n\n---\n\n## 6. VALIDATION RULES\n\n**[SPEC]**\nA valid HADS document must have:\n- H1 title\n- `**Version X.Y.Z**` in first 20 lines\n- AI manifest before first content section\n- All block tags bold: `**[SPEC]**` not `[SPEC]` not *[SPEC]*\n- `[BUG]` blocks contain at minimum symptom + fix\n\nValidator: *(planned — not yet included in this release)*\n\n---\n\n## 7. EXAMPLE INTERACTIONS\n\n**[SPEC]**\n\nUser: *\"Write HADS documentation for this REST API\"*\n→ Generate full HADS document: header, manifest, sections with [SPEC]\u002F[NOTE]\u002F[BUG] blocks\n\nUser: *\"Convert this README to HADS format\"*\n→ Restructure existing content into HADS blocks, preserve all facts, add manifest\n\nUser: *\"Is this document valid HADS?\"*\n→ Check: H1 title, version, manifest, block tag formatting, BUG block completeness\n\nUser: *\"Summarize this HADS document\"*\n→ Read only [SPEC] and [BUG] blocks, return structured summary\n\nUser: *\"What does this API do?\"* (HADS doc provided)\n→ Read manifest, read [SPEC] blocks in relevant sections, answer directly\n\n---\n\n## 8. DESIGN INTENT\n\n**[NOTE]**\nHADS exists because AI models increasingly read documentation before humans do. The format optimizes for this reality without sacrificing human readability.\n\nKey insight: the AI manifest is the core innovation. It lets even small (7B) models know what to read and what to skip — without requiring them to reason about document structure. Explicit is better than implicit for model consumption.\n\nWhen generating HADS, think of `[SPEC]` as the API surface and `[NOTE]` as the comments. `[BUG]` blocks are the most valuable content — they represent hard-won knowledge that saves others from hitting the same wall.\n\n---\n\n## 9. QUICK REFERENCE\n\n**[SPEC]**\n```\nTag       | Bold format    | Reader  | Required content\n----------|----------------|---------|------------------\n[SPEC]    | **[SPEC]**     | AI      | Facts, terse\n[NOTE]    | **[NOTE]**     | Human   | Context, narrative\n[BUG]     | **[BUG] ...**  | Both    | Symptom + fix\n[?]       | **[?]**        | Both    | Unverified claims\n```\n\nManifest minimum:\n```markdown\n## AI READING INSTRUCTION\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified.\n```\n","# HADS Claude Skill\n**Version 1.0.0** · Human-AI Document Standard · 2026 · HADS 1.0.0\n\n---\n\n## AI READING INSTRUCTION\n\nThis skill teaches Claude how to read, generate, and validate HADS documents.\nRead all `[SPEC]` blocks before responding to any HADS-related request.\nRead `[NOTE]` blocks if you need context on intent or edge cases.\n\n---\n\n## 1. WHAT IS HADS\n\n**[SPEC]**\n- HADS = Human-AI Document Standard\n- Convention for Markdown technical documentation\n- Four block types: `**[SPEC]**`, `**[NOTE]**`, `**[BUG]**`, `**[?]**`\n- Every HADS document requires: H1 title, version declaration, AI manifest\n- AI manifest appears before first content section, tells AI what to read\u002Fskip\n- File extension: `.md` — standard Markdown, no tooling required\n\n---\n\n## 2. BLOCK TYPES\n\n**[SPEC]**\n```\n**[SPEC]**   Authoritative fact. Terse. Bullet lists, tables, code. AI reads always.\n**[NOTE]**   Human context, history, examples. AI may skip.\n**[BUG]**    Verified failure + fix. Required fields: symptom, cause, fix. Always read.\n**[?]**      Unverified \u002F inferred. Lower confidence. Always flagged.\n```\n\nBlock tag rules:\n- Bold, on its own line: `**[SPEC]**`\n- Content follows immediately (no blank line between tag and content)\n- Multiple blocks of different types allowed per section\n- Titled BUG blocks allowed: `**[BUG] Short description**`\n- No nesting of blocks inside blocks\n\n---\n\n## 3. REQUIRED DOCUMENT STRUCTURE\n\n**[SPEC]**\n```markdown\n# Document Title\n**Version X.Y.Z** · Author · Date · [metadata]\n\n---\n\n## AI READING INSTRUCTION\n\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified — treat with lower confidence.\n\n---\n\n## 1. First Section\n\n**[SPEC]**\n...\n```\n\nRequired elements in order:\n1. H1 title\n2. `**Version X.Y.Z**` in header (first 20 lines)\n3. AI manifest section before first content section\n4. Content sections (H2), subsections (H3)\n\n---\n\n## 4. HOW CLAUDE READS HADS\n\n**[SPEC]**\nWhen encountering a HADS document:\n1. Find and read the AI manifest first\n2. Read all `[SPEC]` blocks — these are ground truth\n3. Read all `[BUG]` blocks — always, before generating any code or config\n4. Read `[NOTE]` blocks only if `[SPEC]` is insufficient to answer the query\n5. Treat `[?]` content as hypothesis — note uncertainty in response\n\nToken optimization: for large documents, scan section headings first, then read only `[SPEC]` and `[BUG]` blocks in relevant sections.\n\n---\n\n## 5. HOW CLAUDE GENERATES HADS\n\n**[SPEC]**\nWhen asked to write documentation in HADS format:\n\n1. Start with header block (title, version, metadata)\n2. Add AI manifest — always include, never skip\n3. Organize content into numbered H2 sections\n4. For each fact: write as `[SPEC]` — terse, bullet or table or code\n5. For each \"why\" or context: write as `[NOTE]`\n6. For each known failure mode with confirmed fix: write as `[BUG]`\n7. For each unverified claim: write as `[?]`\n8. End with changelog section\n\nContent rules for `[SPEC]`:\n- Prefer bullet lists over prose\n- Prefer tables for multi-field facts\n- Prefer code blocks for syntax, formats, examples\n- Maximum 2 sentences of prose — if more needed, move to `[NOTE]`\n\nContent rules for `[BUG]`:\n- Always include: symptom, cause, fix\n- Optional: affected versions, workaround\n- Title on same line: `**[BUG] Short description**`\n\n**[NOTE]**\nWhen converting existing documentation to HADS: extract facts into `[SPEC]`, move narrative and history to `[NOTE]`, surface all known issues as `[BUG]`. Do not duplicate content between block types.\n\n---\n\n## 6. VALIDATION RULES\n\n**[SPEC]**\nA valid HADS document must have:\n- H1 title\n- `**Version X.Y.Z**` in first 20 lines\n- AI manifest before first content section\n- All block tags bold: `**[SPEC]**` not `[SPEC]` not *[SPEC]*\n- `[BUG]` blocks contain at minimum symptom + fix\n\nValidator: *(planned — not yet included in this release)*\n\n---\n\n## 7. EXAMPLE INTERACTIONS\n\n**[SPEC]**\n\nUser: *\"Write HADS documentation for this REST API\"*\n→ Generate full HADS document: header, manifest, sections with [SPEC]\u002F[NOTE]\u002F[BUG] blocks\n\nUser: *\"Convert this README to HADS format\"*\n→ Restructure existing content into HADS blocks, preserve all facts, add manifest\n\nUser: *\"Is this document valid HADS?\"*\n→ Check: H1 title, version, manifest, block tag formatting, BUG block completeness\n\nUser: *\"Summarize this HADS document\"*\n→ Read only [SPEC] and [BUG] blocks, return structured summary\n\nUser: *\"What does this API do?\"* (HADS doc provided)\n→ Read manifest, read [SPEC] blocks in relevant sections, answer directly\n\n---\n\n## 8. DESIGN INTENT\n\n**[NOTE]**\nHADS exists because AI models increasingly read documentation before humans do. The format optimizes for this reality without sacrificing human readability.\n\nKey insight: the AI manifest is the core innovation. It lets even small (7B) models know what to read and what to skip — without requiring them to reason about document structure. Explicit is better than implicit for model consumption.\n\nWhen generating HADS, think of `[SPEC]` as the API surface and `[NOTE]` as the comments. `[BUG]` blocks are the most valuable content — they represent hard-won knowledge that saves others from hitting the same wall.\n\n---\n\n## 9. QUICK REFERENCE\n\n**[SPEC]**\n```\nTag       | Bold format    | Reader  | Required content\n----------|----------------|---------|------------------\n[SPEC]    | **[SPEC]**     | AI      | Facts, terse\n[NOTE]    | **[NOTE]**     | Human   | Context, narrative\n[BUG]     | **[BUG] ...**  | Both    | Symptom + fix\n[?]       | **[?]**        | Both    | Unverified claims\n```\n\nManifest minimum:\n```markdown\n## AI READING INSTRUCTION\nRead `[SPEC]` and `[BUG]` blocks for authoritative facts.\nRead `[NOTE]` only if additional context is needed.\n`[?]` blocks are unverified.\n```\n",{"name":5,"description":7},"main","900bb95bbe72cdb94af6f5a620aa5081264b7b6d",".claude\u002Fmarketplaces\u002Fwshobson\u002Fplugins\u002Fdocumentation-standards\u002Fskills\u002Fhads",0,"https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up#readme","https:\u002F\u002Fgithub.com\u002Fsteph-frtech","2026-05-16 00:03:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add steph-frtech\u002Fclaude-code-up --skill hads",{"tool":37,"command":38},"bunx","bunx skills add steph-frtech\u002Fclaude-code-up --skill hads",{"tool":40,"command":41},"pnpm","pnpm dlx skills add steph-frtech\u002Fclaude-code-up --skill hads","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fmarketplaces\u002Fwshobson\u002Fplugins\u002Fdocumentation-standards\u002Fskills\u002Fhads\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M72Y1BY6X8TX3DS19Y04NEBQ","example","One-line summary of what this skill does","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002Fskills\u002Fexample\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M72Y1A38EYR8S9P1MBYDAQTW","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuperpowers__writing-plans\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M72Y174QSV1B5NV1E4KWHQBR","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuperpowers__using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M72Y14SQRHHMKG316HGB2CGK","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuperpowers__test-driven-development\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M72Y127BCPRH3BRKPJC3Q3G2","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuperpowers__systematic-debugging\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M72Y1090GJA6B67KPD60WPHH","subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fsteph-frtech\u002Fclaude-code-up\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsuperpowers__subagent-driven-development\u002FSKILL.md",[],[]]