[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758NF5ASE70Q8VHAJCJDTEF":3,"skill-same:01M758NF5ASE70Q8VHAJCJDTEF":49},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M758NF5ASE70Q8VHAJCJDTEF","cognitive-doc-design",null,"Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.","davidcoachdev\u002Fdcfiles","davidcoachdev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69812733?v=4","01M758C4BR16TAV1N47W319E9V","David H. Caycedo Blum.","01M758C4CCZA2ZYGA0BGMXCDRH",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fcognitive-doc-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: cognitive-doc-design\ndescription: \"Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## When to Use\n\nLoad this skill when creating or editing documentation that people need to understand quickly, retain, or use during review.\n\nUse it especially for:\n\n- PR descriptions and review notes.\n- Contributor or maintainer guides.\n- Architecture, workflow, or onboarding docs.\n- Any doc that currently feels long, dense, or hard to scan.\n\n## Critical Patterns\n\n| Pattern | Rule |\n|---------|------|\n| Lead with the answer | Put the decision, action, or outcome first. Context comes after. |\n| Progressive disclosure | Start with the happy path, then add details, edge cases, and references. |\n| Chunking | Group related information into small sections. Keep flat lists short. |\n| Signposting | Use headings, labels, callouts, and summaries so readers know where they are. |\n| Recognition over recall | Prefer tables, checklists, examples, and templates over prose that must be remembered. |\n| Review empathy | Design docs so reviewers can verify intent without reconstructing the whole story. |\n\n## Documentation Shape\n\nUse this default structure unless the repo already provides a stronger template:\n\n```markdown\n# \u003COutcome-oriented title>\n\n\u003COne paragraph: what changed, who it helps, and why it matters.>\n\n## Quick path\n\n1. \u003CFirst action>\n2. \u003CSecond action>\n3. \u003CVerification or expected result>\n\n## Details\n\n| Topic | Decision |\n|-------|----------|\n| \u003Carea> | \u003Cconcise explanation> |\n\n## Checklist\n\n- [ ] \u003CReader can confirm this>\n- [ ] \u003CReader can confirm that>\n\n## Next step\n\n\u003CLink or action that continues the workflow.>\n```\n\n## PR and Review Docs\n\nWhen documenting a PR, reduce reviewer burnout by making the review path explicit:\n\n- State what to review first.\n- State what is intentionally out of scope.\n- Link the previous and next PR when work is chained.\n- Keep each section focused on one decision or unit of work.\n- Use checklists for acceptance criteria and verification.\n\n## Commands\n\n```bash\n# Check markdown files changed in the current branch\ngit diff --name-only -- '*.md'\n\n# Inspect PR changed-line count for cognitive load\ngh pr view \u003CPR_NUMBER> --json additions,deletions,changedFiles\n```\n","## When to Use\n\nLoad this skill when creating or editing documentation that people need to understand quickly, retain, or use during review.\n\nUse it especially for:\n\n- PR descriptions and review notes.\n- Contributor or maintainer guides.\n- Architecture, workflow, or onboarding docs.\n- Any doc that currently feels long, dense, or hard to scan.\n\n## Critical Patterns\n\n| Pattern | Rule |\n|---------|------|\n| Lead with the answer | Put the decision, action, or outcome first. Context comes after. |\n| Progressive disclosure | Start with the happy path, then add details, edge cases, and references. |\n| Chunking | Group related information into small sections. Keep flat lists short. |\n| Signposting | Use headings, labels, callouts, and summaries so readers know where they are. |\n| Recognition over recall | Prefer tables, checklists, examples, and templates over prose that must be remembered. |\n| Review empathy | Design docs so reviewers can verify intent without reconstructing the whole story. |\n\n## Documentation Shape\n\nUse this default structure unless the repo already provides a stronger template:\n\n```markdown\n# \u003COutcome-oriented title>\n\n\u003COne paragraph: what changed, who it helps, and why it matters.>\n\n## Quick path\n\n1. \u003CFirst action>\n2. \u003CSecond action>\n3. \u003CVerification or expected result>\n\n## Details\n\n| Topic | Decision |\n|-------|----------|\n| \u003Carea> | \u003Cconcise explanation> |\n\n## Checklist\n\n- [ ] \u003CReader can confirm this>\n- [ ] \u003CReader can confirm that>\n\n## Next step\n\n\u003CLink or action that continues the workflow.>\n```\n\n## PR and Review Docs\n\nWhen documenting a PR, reduce reviewer burnout by making the review path explicit:\n\n- State what to review first.\n- State what is intentionally out of scope.\n- Link the previous and next PR when work is chained.\n- Keep each section focused on one decision or unit of work.\n- Use checklists for acceptance criteria and verification.\n\n## Commands\n\n```bash\n# Check markdown files changed in the current branch\ngit diff --name-only -- '*.md'\n\n# Inspect PR changed-line count for cognitive load\ngh pr view \u003CPR_NUMBER> --json additions,deletions,changedFiles\n```\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"gentleman-programming","1.0","main","5dc86f90a5cbe45db3acd917825461b3ed6937fb","config\u002F.config\u002Fopencode\u002Fskills\u002Fcognitive-doc-design",0,"https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev","🌐 Apasionado por crear soluciones web escalables y eficientes. \r\n🧑‍🏫 Coach Dev.\r\n💻 Frontend Dev. \r\n🎚️Backend Dev.\r\n📊 Agile\u002FScrum.\r\n🚀100% remoto.","2026-08-26 07:28:05",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add davidcoachdev\u002Fdcfiles --skill cognitive-doc-design",{"tool":41,"command":42},"bunx","bunx skills add davidcoachdev\u002Fdcfiles --skill cognitive-doc-design",{"tool":44,"command":45},"pnpm","pnpm dlx skills add davidcoachdev\u002Fdcfiles --skill cognitive-doc-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fcognitive-doc-design\u002FSKILL.md",true,[],[50,57,64,71,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7740FETMZY1VTYAEFY1TWY7","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M773ZZM9V68SA1AKP4WF4J29","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M773ZJFR90CQAY0N9QR40QVP","x-bookmark-quote-posts","Workflow para revisar bookmarks de X\u002FTwitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fx-bookmark-quote-posts\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M773Z2RGV3786FV310SDB0YD","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","MIT","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M773YJH3KDSW467CSS63CSRJ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M773Y3S3H2CPRK5S8YFHWB5C","work-unit-commits","Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.","https:\u002F\u002Fgithub.com\u002Fdavidcoachdev\u002Fdcfiles\u002Fblob\u002Fmain\u002Fconfig\u002F.config\u002Fopencode\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[]]