[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AD0DM489QEVQ01M9GNMSXE":3,"skill-same:01M7AD0DM489QEVQ01M9GNMSXE":44},{"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7AD0DM489QEVQ01M9GNMSXE","documentation-style-docs",null,"Use when creating or updating project documentation in the same architecture and writing style as FogStages.md: title + visual block, index, introduction, implementation plan, code locations table, TODO, and limitations\u002Fbugs. Trigger on requests like create docs, write documentation, add design document, feature spec, system write-up, or architecture note.","JesterWizard\u002FSkillSystem_FE7","JesterWizard","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F164426396?v=4","01M7ACZD32AVSPDR22QKQR5HNY","01M7ACZD478KR9RA07QGPHE24H",4,"CC0-1.0","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fdocumentation-style-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documentation-style-docs\ndescription: \"Use when creating or updating project documentation in the same architecture and writing style as FogStages.md: title + visual block, index, introduction, implementation plan, code locations table, TODO, and limitations\u002Fbugs. Trigger on requests like create docs, write documentation, add design document, feature spec, system write-up, or architecture note.\"\n---\n\n# Documentation Style Docs\n\nCreate markdown documentation that mirrors the structure, tone, and readability patterns used in `docs\u002FFeatures\u002FFogStages.md`.\n\n## Use This Skill When\n\n- The user asks to create new documentation.\n- The user asks to rewrite or expand a feature\u002Fdesign doc.\n- The user requests a technical write-up intended for contributors.\n\n## Output Contract\n\nProduce a markdown file with the following sections and order unless the user asks for a different structure.\n\n1. H1 title with a concise, memorable phrase.\n2. Optional centered visual block (gif\u002Fimage) using HTML if an asset exists.\n3. Horizontal rule.\n4. Index section with anchor links to major sections.\n5. Introduction section.\n6. Plan section describing behavior and design intent.\n7. Code Locations section as a table.\n8. TODO section.\n9. Limitations & Bugs section.\n\n## Style Rules\n\n- Keep language practical and contributor-focused.\n- Explain player-facing impact first, then implementation details.\n- Prefer short paragraphs and compact bullet lists.\n- Use tables for behavior matrices and file responsibilities.\n- Use clear section headings and predictable ordering.\n- Keep claims concrete and verifiable in code.\n\n## Architecture Pattern\n\nFollow this architecture pattern by default.\n\n- Introduction: problem statement, why current behavior is weak, and design goal.\n- Plan: staged model or system model with an explicit legend\u002Ftable.\n- Code Locations: map each feature slice to concrete function names and file paths.\n- TODO: leave explicit placeholders for future follow-up.\n- Limitations & Bugs: document known constraints and invite issue reports.\n\n## Code Locations Table Format\n\nUse this 3-column format when possible.\n\n| Feature | Location | Description |\n|--------|----------|-------------|\n| Feature slice | `FunctionName` in `path\u002Fto\u002Ffile.c` | What this code is responsible for |\n\n## Authoring Workflow\n\n1. Identify the target mechanic\u002Fsystem and its player-facing goals.\n2. Locate the relevant implementation files and core entry-point functions.\n3. Build a behavior table for visibility states, stages, or modes.\n4. Draft sections in the standard order.\n5. Verify links and symbols match repository names exactly.\n\n## Quality Checklist\n\n- Headings and index anchors are valid.\n- File\u002Ffunction references exist in the repository.\n- Behavior table has no ambiguous state transitions.\n- TODO and limitations are present even if brief.\n- Tone matches contributor documentation, not marketing copy.\n\n## Default Template\n\nIf the user does not provide a custom structure, start from:\n\n- `.github\u002Fskills\u002Fdocumentation-style-docs\u002Ftemplates\u002FDocumentationStyleTemplate.md`","# Documentation Style Docs\n\nCreate markdown documentation that mirrors the structure, tone, and readability patterns used in `docs\u002FFeatures\u002FFogStages.md`.\n\n## Use This Skill When\n\n- The user asks to create new documentation.\n- The user asks to rewrite or expand a feature\u002Fdesign doc.\n- The user requests a technical write-up intended for contributors.\n\n## Output Contract\n\nProduce a markdown file with the following sections and order unless the user asks for a different structure.\n\n1. H1 title with a concise, memorable phrase.\n2. Optional centered visual block (gif\u002Fimage) using HTML if an asset exists.\n3. Horizontal rule.\n4. Index section with anchor links to major sections.\n5. Introduction section.\n6. Plan section describing behavior and design intent.\n7. Code Locations section as a table.\n8. TODO section.\n9. Limitations & Bugs section.\n\n## Style Rules\n\n- Keep language practical and contributor-focused.\n- Explain player-facing impact first, then implementation details.\n- Prefer short paragraphs and compact bullet lists.\n- Use tables for behavior matrices and file responsibilities.\n- Use clear section headings and predictable ordering.\n- Keep claims concrete and verifiable in code.\n\n## Architecture Pattern\n\nFollow this architecture pattern by default.\n\n- Introduction: problem statement, why current behavior is weak, and design goal.\n- Plan: staged model or system model with an explicit legend\u002Ftable.\n- Code Locations: map each feature slice to concrete function names and file paths.\n- TODO: leave explicit placeholders for future follow-up.\n- Limitations & Bugs: document known constraints and invite issue reports.\n\n## Code Locations Table Format\n\nUse this 3-column format when possible.\n\n| Feature | Location | Description |\n|--------|----------|-------------|\n| Feature slice | `FunctionName` in `path\u002Fto\u002Ffile.c` | What this code is responsible for |\n\n## Authoring Workflow\n\n1. Identify the target mechanic\u002Fsystem and its player-facing goals.\n2. Locate the relevant implementation files and core entry-point functions.\n3. Build a behavior table for visibility states, stages, or modes.\n4. Draft sections in the standard order.\n5. Verify links and symbols match repository names exactly.\n\n## Quality Checklist\n\n- Headings and index anchors are valid.\n- File\u002Ffunction references exist in the repository.\n- Behavior table has no ambiguous state transitions.\n- TODO and limitations are present even if brief.\n- Tone matches contributor documentation, not marketing copy.\n\n## Default Template\n\nIf the user does not provide a custom structure, start from:\n\n- `.github\u002Fskills\u002Fdocumentation-style-docs\u002Ftemplates\u002FDocumentationStyleTemplate.md`",{"name":5,"description":7},"main","b0f8a46e7eb03e690c3965dbe08b10b1bada7364",".cursor\u002Fskills\u002Fdocumentation-style-docs",0,"https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7","https:\u002F\u002Fgithub.com\u002FJesterWizard","2026-09-07 02:17:07",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add JesterWizard\u002FSkillSystem_FE7 --skill documentation-style-docs",{"tool":36,"command":37},"bunx","bunx skills add JesterWizard\u002FSkillSystem_FE7 --skill documentation-style-docs",{"tool":39,"command":40},"pnpm","pnpm dlx skills add JesterWizard\u002FSkillSystem_FE7 --skill documentation-style-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fdocumentation-style-docs\u002FSKILL.md",true,[],[45,52,59,66,73,78],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7AD0HNWAZ0QK1ZKDM7WTRVR","implement-skill","Resolves a named FE7 skill to its file pack and edits only those paths. Use when the user wants to implement, enable, port, wire, fix, add, install, or debug a skill (Nullify, Provoke, Adept, etc.).","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fimplement-skill\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M7AD09G3JN4Z7DRG7QY84PA2","caveman","Ultra-compressed communication AND thinking. Always use extreme (ultra) caveman to minimize tokens in both reasoning and replies. Cuts output ~65% and thinking tokens by skipping recap, option-lists, and filler thought. Use when user says \"caveman mode\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", \"extreme caveman\", or invokes \u002Fcaveman. Also auto-triggers when token efficiency is requested.","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fcaveman\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M7AD06EWF2TM1D2HPAQD8KPP","stay-within-limits","Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fstay-within-limits\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7AD02NZX9W1V2XVTKWARR6M","quick-recap","Use when adding or following the red\u002Fyellow\u002Fgreen final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fquick-recap\u002FSKILL.md",[],[],{"skillNo":74,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7ACZZTMSRS96D0H2FNM35T0","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplement-skill\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7ACZWMWHQMFG0D82K2AVZPZ","efficient-frontier","Apply the same orchestration as `\u002Fefficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.","https:\u002F\u002Fgithub.com\u002FJesterWizard\u002FSkillSystem_FE7\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fefficient-frontier\u002FSKILL.md",[],[]]