[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E1BTSRZMPTXVD95MB7FA01":3,"skill-same:01M6E1BTSRZMPTXVD95MB7FA01":79},{"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":30,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M6E1BTSRZMPTXVD95MB7FA01","teach-impeccable",null,"One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.","AkaraChen\u002Faghub","AkaraChen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F85140972?v=4","01M6E197RY34TPAFK03227R387","01M6E197X876C4624H0VJC1E5H",270,"MIT","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fteach-impeccable\u002FSKILL.md",[17,22,27],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":28,"categoryName":29,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000039","教师与教育",[31,32,33,34,35,36,37,38,39,40,41,42,43],"teach","impeccable","teach impeccable","design","config","setup","guidelines","run","file","context","ai config","time","project","2026-11-10 10:12:30",false,"---\nname: teach-impeccable\ndescription: One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.\nuser-invocable: true\n---\n\nGather design context for this project, then persist it for all future sessions.\n\n## Step 1: Explore the Codebase\n\nBefore asking questions, thoroughly scan the project to discover what you can:\n\n- **README and docs**: Project purpose, target audience, any stated goals\n- **Package.json \u002F config files**: Tech stack, dependencies, existing design libraries\n- **Existing components**: Current design patterns, spacing, typography in use\n- **Brand assets**: Logos, favicons, color values already defined\n- **Design tokens \u002F CSS variables**: Existing color palettes, font stacks, spacing scales\n- **Any style guides or brand documentation**\n\nNote what you've learned and what remains unclear.\n\n## Step 2: Ask UX-Focused Questions\n\nask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:\n\n### Users & Purpose\n\n- Who uses this? What's their context when using it?\n- What job are they trying to get done?\n- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)\n\n### Brand & Personality\n\n- How would you describe the brand personality in 3 words?\n- Any reference sites or apps that capture the right feel? What specifically about them?\n- What should this explicitly NOT look like? Any anti-references?\n\n### Aesthetic Preferences\n\n- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)\n- Light mode, dark mode, or both?\n- Any colors that must be used or avoided?\n\n### Accessibility & Inclusion\n\n- Specific accessibility requirements? (WCAG level, known user needs)\n- Considerations for reduced motion, color blindness, or other accommodations?\n\nSkip questions where the answer is already clear from the codebase exploration.\n\n## Step 3: Write Design Context\n\nSynthesize your findings and the user's answers into a `## Design Context` section:\n\n```markdown\n## Design Context\n\n### Users\n\n[Who they are, their context, the job to be done]\n\n### Brand Personality\n\n[Voice, tone, 3-word personality, emotional goals]\n\n### Aesthetic Direction\n\n[Visual tone, references, anti-references, theme]\n\n### Design Principles\n\n[3-5 principles derived from the conversation that should guide all design decisions]\n```\n\nWrite this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place.\n\nThen ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github\u002Fcopilot-instructions.md. If yes, append or update the section there as well.\n\nConfirm completion and summarize the key design principles that will now guide all future work.\n","Gather design context for this project, then persist it for all future sessions.\n\n## Step 1: Explore the Codebase\n\nBefore asking questions, thoroughly scan the project to discover what you can:\n\n- **README and docs**: Project purpose, target audience, any stated goals\n- **Package.json \u002F config files**: Tech stack, dependencies, existing design libraries\n- **Existing components**: Current design patterns, spacing, typography in use\n- **Brand assets**: Logos, favicons, color values already defined\n- **Design tokens \u002F CSS variables**: Existing color palettes, font stacks, spacing scales\n- **Any style guides or brand documentation**\n\nNote what you've learned and what remains unclear.\n\n## Step 2: Ask UX-Focused Questions\n\nask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:\n\n### Users & Purpose\n\n- Who uses this? What's their context when using it?\n- What job are they trying to get done?\n- What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)\n\n### Brand & Personality\n\n- How would you describe the brand personality in 3 words?\n- Any reference sites or apps that capture the right feel? What specifically about them?\n- What should this explicitly NOT look like? Any anti-references?\n\n### Aesthetic Preferences\n\n- Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)\n- Light mode, dark mode, or both?\n- Any colors that must be used or avoided?\n\n### Accessibility & Inclusion\n\n- Specific accessibility requirements? (WCAG level, known user needs)\n- Considerations for reduced motion, color blindness, or other accommodations?\n\nSkip questions where the answer is already clear from the codebase exploration.\n\n## Step 3: Write Design Context\n\nSynthesize your findings and the user's answers into a `## Design Context` section:\n\n```markdown\n## Design Context\n\n### Users\n\n[Who they are, their context, the job to be done]\n\n### Brand Personality\n\n[Voice, tone, 3-word personality, emotional goals]\n\n### Aesthetic Direction\n\n[Visual tone, references, anti-references, theme]\n\n### Design Principles\n\n[3-5 principles derived from the conversation that should guide all design decisions]\n```\n\nWrite this section to `.impeccable.md` in the project root. If the file already exists, update the Design Context section in place.\n\nThen ask the user directly to clarify what you cannot infer. whether they'd also like the Design Context appended to .github\u002Fcopilot-instructions.md. If yes, append or update the section there as well.\n\nConfirm completion and summarize the key design principles that will now guide all future work.\n",{"name":5,"description":7,"user-invocable":49},true,"main","2a846f29fb144c9e738f1c79a4a9f17c2f5d0c19",".agents\u002Fskills\u002Fteach-impeccable",19,"https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub","https:\u002F\u002Faghub.akr.moe","https:\u002F\u002Fgithub.com\u002FAkaraChen","https:\u002F\u002Fakr.moe","button painter, string concatenator, log alchemist.\r\n\r\nNo slop, no lag.","2026-11-10 06:35:07",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add AkaraChen\u002Faghub --skill teach-impeccable",{"tool":66,"command":67},"bunx","bunx skills add AkaraChen\u002Faghub --skill teach-impeccable",{"tool":69,"command":70},"pnpm","pnpm dlx skills add AkaraChen\u002Faghub --skill teach-impeccable","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fteach-impeccable\u002FSKILL.md",[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"index.json","REFERENCE","参考文档",520,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-auth-jwt-signing-verify\u002Findex.json",[80,95,117,128,138,146],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":44},"01M6E1C5XRWJGK1FTMBYBP72EP","vercel-react-best-practices","Vercel React Best Practices","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002Ffixtures\u002F.agents\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[90,91,92,93,94],"vercel","react best practices","react","vercel react best practices","best practices",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":44},"01M6E1C1S4GGD447NC3B3B7KKQ","init-deep","Generate hierarchical AGENTS.md and ensure paired CLAUDE.md files for codebases. Creates root AGENTS.md + CLAUDE.md plus complexity-scored subdirectory files. Use when user asks to \"generate AGENTS.md files\", \"create codebase knowledge base\", \"run \u002Finit-deep\", or wants comprehensive project documentation. Supports update mode (default) and --create-new flag to regenerate from scratch.","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finit-deep\u002FSKILL.md",[],[102,103,104,105,106,107,108,38,109,110,43,111,112,113,114,115,116],"init","init deep","deep","user","documentation","create","generate","update","knowledge","use","complexity","files","default","base","knowledge base",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":44},"01M6E1BY84HFA0FF0W0APPNYH6","typeset","Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography.","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftypeset\u002FSKILL.md",[],[119,124,125,126,105,111,127],"typography","type","text","readability",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":44},"01M6E1BQH59R5H8XA4MH3S083N","quieter","Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic.","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fquieter\u002FSKILL.md",[],[130,135,105,111,136,137],"quality","aesthetic","intensity",{"skillNo":139,"name":140,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":44},"01M6E1BMJ7PNFPXD8SRCQ6WH1S","project-form-patterns","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fproject-form-patterns\u002FSKILL.md",[],[43,144,145],"project form patterns","patterns",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":44},"01M6E1BHEDVTPKC1KS7A7B0VGZ","polish","Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.","https:\u002F\u002Fgithub.com\u002FAkaraChen\u002Faghub\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpolish\u002FSKILL.md",[],[148,153,154,155,156,157,158,135,105,111,159,160,161],"detail","go","launch","shipping","issues","micro","good","alignment","review"]