[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGMFZ5PY7P2FG1STT8AGPB":3,"skill-same:01M6JGMFZ5PY7P2FG1STT8AGPB":67},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6JGMFZ5PY7P2FG1STT8AGPB","design-direction",null,"Show a numbered prototype and hold it until the supervisor picks. Use when starting or redesigning a screen, and when a first pass would look the same on any similar brief.","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\u002Fdesign-direction\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40],"design","direction","design direction","prototype","brief","first","supervisor","use","look","show","screen","it","2026-11-10 10:12:30",false,"---\nname: design-direction\ndescription: >-\n  Show a numbered prototype and hold it until the supervisor picks.\n  Use when starting or redesigning a screen, and when a first pass\n  would look the same on any similar brief.\nlicense: MIT\n---\n\n# Design Direction\n\nTurn a description into a numbered prototype, and wait until the supervisor picks.\n\n## When to Use\n\n- Filing the picked prototype is `design-system`. The quality pass is `ui-ux-review`.\n- A named taste (`high-end-visual-design`, brutalist, minimalist) is a separate call, and only when the brief asks for that style by name.\n- Skip when the supervisor already picked a prototype and the task is to file it.\n\n## Procedure\n\n1. Write the description: the subject, who it is for, and the job of this piece. One sentence each. When the brief does not say, ask before filling the gap.\n2. Make a prototype of the element you reworked. Name the additions it uses. Palette, type, and each color scheme the piece uses are the usual ones. One scheme is a complete answer. Name any other addition the piece actually rests on.\n3. Put a number on the prototype. When you show more than one, number each. The supervisor refers to a prototype by that number.\n4. Show the prototype and stop. Integration into the product waits until the supervisor picks a number or names the change. Silence is not a pick.\n\nThe prototype stays the proposal until that pick. `design-system` files the pick.\n\nOpen these when a line needs the source, and leave them as links:\n\n- `anthropics\u002Fskills`, `skills\u002Ffrontend-design\u002FSKILL.md` — the brief-wins rule and examples of an unchosen default.\n- `Leonxlnx\u002Ftaste-skill`, `skills\u002Ftaste-skill\u002Freferences\u002F` — type, color, grid, motion, critique, when the line is about that.\n- `nexu-io\u002Fopen-design`, `craft\u002Ftypography.md`, `craft\u002Fcolor.md` — when the line is choosing type or color.\n\nThe anti-list this role applies is `ui-ux-review`. `craft\u002Fanti-ai-slop.md` is the same concern written elsewhere; read it for examples, and do not add its bullets as a second list.\n\n## Completion\n\n- A numbered prototype is shown, with the reworked element and the additions it uses.\n- The supervisor has picked a number or named a change. Silence is not a pick.\n- The product was not changed in this pass.\n\n**Validation scenario (RED).** Asked for a settings screen on an accounting board, the agent produces a cream editorial hero, a small-caps pill over the title, and a reveal on every section, and integrates that into the product. The brief never asked for an editorial landing. GREEN: prototype 1, the settings screen with the element reworked for the board, the palette and type named, then a stop. No integration yet.\n\n## Anti-Patterns\n\n- Integrating into the product and calling that the prototype.\n- Showing several prototypes and not numbering them.\n- Treating the pause as optional because the prototype looks finished.\n- Shipping the cream editorial, the pill over the headline, or a reveal on every section as the look of a finished piece. Those are the common unchosen defaults, not the whole set.\n\n## Attribution\n\nProcedure written for this catalog. The move comes from `anthropics\u002Fskills` `skills\u002Ffrontend-design` (Apache-2.0) and the direction-then-show step of `Leonxlnx\u002Ftaste-skill` (MIT). Their text is not copied.\n","# Design Direction\n\nTurn a description into a numbered prototype, and wait until the supervisor picks.\n\n## When to Use\n\n- Filing the picked prototype is `design-system`. The quality pass is `ui-ux-review`.\n- A named taste (`high-end-visual-design`, brutalist, minimalist) is a separate call, and only when the brief asks for that style by name.\n- Skip when the supervisor already picked a prototype and the task is to file it.\n\n## Procedure\n\n1. Write the description: the subject, who it is for, and the job of this piece. One sentence each. When the brief does not say, ask before filling the gap.\n2. Make a prototype of the element you reworked. Name the additions it uses. Palette, type, and each color scheme the piece uses are the usual ones. One scheme is a complete answer. Name any other addition the piece actually rests on.\n3. Put a number on the prototype. When you show more than one, number each. The supervisor refers to a prototype by that number.\n4. Show the prototype and stop. Integration into the product waits until the supervisor picks a number or names the change. Silence is not a pick.\n\nThe prototype stays the proposal until that pick. `design-system` files the pick.\n\nOpen these when a line needs the source, and leave them as links:\n\n- `anthropics\u002Fskills`, `skills\u002Ffrontend-design\u002FSKILL.md` — the brief-wins rule and examples of an unchosen default.\n- `Leonxlnx\u002Ftaste-skill`, `skills\u002Ftaste-skill\u002Freferences\u002F` — type, color, grid, motion, critique, when the line is about that.\n- `nexu-io\u002Fopen-design`, `craft\u002Ftypography.md`, `craft\u002Fcolor.md` — when the line is choosing type or color.\n\nThe anti-list this role applies is `ui-ux-review`. `craft\u002Fanti-ai-slop.md` is the same concern written elsewhere; read it for examples, and do not add its bullets as a second list.\n\n## Completion\n\n- A numbered prototype is shown, with the reworked element and the additions it uses.\n- The supervisor has picked a number or named a change. Silence is not a pick.\n- The product was not changed in this pass.\n\n**Validation scenario (RED).** Asked for a settings screen on an accounting board, the agent produces a cream editorial hero, a small-caps pill over the title, and a reveal on every section, and integrates that into the product. The brief never asked for an editorial landing. GREEN: prototype 1, the settings screen with the element reworked for the board, the palette and type named, then a stop. No integration yet.\n\n## Anti-Patterns\n\n- Integrating into the product and calling that the prototype.\n- Showing several prototypes and not numbering them.\n- Treating the pause as optional because the prototype looks finished.\n- Shipping the cream editorial, the pill over the headline, or a reveal on every section as the look of a finished piece. Those are the common unchosen defaults, not the whole set.\n\n## Attribution\n\nProcedure written for this catalog. The move comes from `anthropics\u002Fskills` `skills\u002Ffrontend-design` (Apache-2.0) and the direction-then-show step of `Leonxlnx\u002Ftaste-skill` (MIT). Their text is not copied.\n",{"name":5,"license":15,"description":7},"master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fdesign-direction",1,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add muratovv\u002Fai-hats --skill design-direction",{"tool":59,"command":60},"bunx","bunx skills add muratovv\u002Fai-hats --skill design-direction",{"tool":62,"command":63},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill design-direction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fdesign-direction\u002FSKILL.md",true,[],[68,94,119,140,164,178],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":41},"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",[],[75,76,77,78,79,80,81,82,83,84,36,85,86,87,88,89,90,91,92,93],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","dependency","up","frameworks","time","project","recommendation","for","bounded","candidate",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":41},"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",[],[101,102,103,104,75,105,106,107,108,109,36,110,111,112,113,114,115,116,117,118],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","with","bug-fix","phase",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":128,"publishedAt":41},"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",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[129,130,131,132,133,108,134,36,135,113,136,137,138,91,139],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":41},"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",[146],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,150,151,152,153,154,155,156,157,36,158,159,160,161,162,163],"Optimization","skill optimization","components","component","issues","library","audit","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":41},"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",[],[171,172,173,174,175,176,36,177,91],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":41},"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",[184],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[186,187,188,189,151,190,191,192,157,108,36,193,194,89,195,196,197,198,199,200],"framework","retro","retro to framework","change","retrospective","projects","convert","incident","across","problem","about","more","skill update","single","generic"]