[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RQ2HA8TRSD1A1FD2F60QS":3,"skill-same:01M77RQ2HA8TRSD1A1FD2F60QS":48},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77RQ2HA8TRSD1A1FD2F60QS","cognitive-doc-design",null,"Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.","janpereira-dev\u002FskillsCurate","janpereira-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6440548?v=4","01M6KKKXBFFK7QF5Y2JFXN35FF","Jan Pereira","01M77ND31QCT5KM25E1SW71M8F",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcognitive-doc-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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","ba43a4e7e8b0fd6b150b14bcb48978ec40879a28",".agents\u002Fskills\u002Fcognitive-doc-design","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev","IT Leader, Scrum Master, FullStack Developer, SEO\u002FSEM Master #Angular #React\r\n","2026-07-13 03:04:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add janpereira-dev\u002FskillsCurate --skill cognitive-doc-design",{"tool":40,"command":41},"bunx","bunx skills add janpereira-dev\u002FskillsCurate --skill cognitive-doc-design",{"tool":43,"command":44},"pnpm","pnpm dlx skills add janpereira-dev\u002FskillsCurate --skill cognitive-doc-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcognitive-doc-design\u002FSKILL.md",true,[],[49,56,63,70,78,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M77T9KN6TEJMPPTQZDEB4K61","zustand-5","Zustand 5 state management patterns. Trigger: When managing React state with Zustand.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzustand-5\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M77T9GN2GABPPWDGDCXJ6QWK","zod-4","Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fzod-4\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77T98A9R6PK155P71VX9MND","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\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwork-unit-commits\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77T9505TGQGWHGAYVXGE2KS","web-quality-audit","Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".","MIT","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-quality-audit\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77T8YRVRNK8W4MG63XM80NK","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\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":74,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77T8CEPQFZRRNGBYZX46P4Y","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002Fjanpereira-dev\u002FskillsCurate\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvercel-react-view-transitions\u002FSKILL.md",[],[]]