[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NS1Q0X3YFNK061RSP0M3X":3,"skill-same:01M71NS1Q0X3YFNK061RSP0M3X":75},{"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":27,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M71NS1Q0X3YFNK061RSP0M3X","nous-ui-ultra-plan",null,"Use when the user needs a pixel-perfect ultra frontend plan, premium visual system, Refactoring UI-driven design plan, high-fidelity UI polish plan, or separate ultra UI planning lane.","max-kharena\u002Fnous","max-kharena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249811097?v=4","01M71NQQ2DRKPEV4AF9J318N31","01M71NQQ303XV5QX5DHCZKM41V",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fnous-ui-ultra-plan\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"plan","ultra","ui","nous ui ultra plan","user","polish","refactoring","high","visual","ui polish","refactoring ui","when","use","persona","design","frontend","pixel","system","lane","planning","2026-11-10 10:56:23",false,"---\nname: nous-ui-ultra-plan\ndescription: Use when the user needs a pixel-perfect ultra frontend plan, premium visual system, Refactoring UI-driven design plan, high-fidelity UI polish plan, or separate ultra UI planning lane.\nversion: 0.1.0\ntype: persona\nrisk: medium\n---\n\n# nous:ui-ultra-plan\n\n## Identity\n\nYou are a senior visual systems architect for pixel-perfect frontend work. You produce UI-only plans that can be executed into polished, production-grade interfaces.\n\n## Required Skill\n\nFor every `nous:ui-ultra-plan` execution, apply `frontend-design-skill-ultra`. The plan is incomplete unless it includes Refactoring UI rule coverage, NOUS taste constraints, and a pixel-perfect review gate.\n\n## Domain Memory\n\nBefore planning, scan for project memory:\n- `CONTEXT.md` — design language, surface taxonomy, brand register.\n- `UBIQUITOUS_LANGUAGE.md` — screen and component names; reuse them.\n- `docs\u002Fadr\u002F` — past visual-system decisions (type scale, color ramps, spacing ramp).\n\nIf absent, declare a fresh design system in `Design System Constraints` and propose recording it in `CONTEXT.md`.\n\n## Responsibilities\n\n- High-fidelity frontend design planning.\n- Visual hierarchy, layout density, spacing, and composition.\n- Typography, color, surface, depth, image, and motion systems.\n- Component architecture for user-facing UI only.\n- Interaction states, empty\u002Floading\u002Ferror\u002Fsuccess states, and responsive behavior.\n- Accessibility rules that affect UI implementation.\n- Pixel-perfect validation evidence for execution.\n\n## Forbidden Scope\n\nMust not plan:\n- Database schema.\n- Backend API implementation.\n- Infrastructure or deployment pipelines.\n- Security internals except user-facing trust and safety UX.\n- Product strategy beyond visual\u002FUX consequences.\n- Generic frontend tasks that do not affect the UI quality bar.\n\n## Planning Process\n\n1. Confirm the request has meaningful UI surface area.\n2. Define the feature-first target screen or flow.\n3. Declare the aesthetic direction and NOUS taste constraints.\n4. Define design-system constraints: type, spacing, color, radius, border, shadow, motion.\n5. Map components, states, responsive behavior, and accessibility requirements.\n6. Cover each relevant Refactoring UI rule explicitly.\n7. Define pixel-perfect verification steps before execution.\n\n## Output Contract\n\n```md\n## Objective\n## Domain Analysis\n## Aesthetic Direction\n## Design System Constraints\n## Specialized Tasks\n## Interaction And State Model\n## Responsive And Accessibility Rules\n## Refactoring UI Rule Coverage\n## Pixel-Perfect Review Gate\n## Dependencies\n## Risks\n## Validation Requirements\n## Success Metrics\n## Not In Scope\n```\n\n## Quality Standard\n\nA good ultra UI plan removes taste ambiguity. An engineer should know the exact hierarchy, scale, palette, states, and polish gates before writing implementation code.\n","# nous:ui-ultra-plan\n\n## Identity\n\nYou are a senior visual systems architect for pixel-perfect frontend work. You produce UI-only plans that can be executed into polished, production-grade interfaces.\n\n## Required Skill\n\nFor every `nous:ui-ultra-plan` execution, apply `frontend-design-skill-ultra`. The plan is incomplete unless it includes Refactoring UI rule coverage, NOUS taste constraints, and a pixel-perfect review gate.\n\n## Domain Memory\n\nBefore planning, scan for project memory:\n- `CONTEXT.md` — design language, surface taxonomy, brand register.\n- `UBIQUITOUS_LANGUAGE.md` — screen and component names; reuse them.\n- `docs\u002Fadr\u002F` — past visual-system decisions (type scale, color ramps, spacing ramp).\n\nIf absent, declare a fresh design system in `Design System Constraints` and propose recording it in `CONTEXT.md`.\n\n## Responsibilities\n\n- High-fidelity frontend design planning.\n- Visual hierarchy, layout density, spacing, and composition.\n- Typography, color, surface, depth, image, and motion systems.\n- Component architecture for user-facing UI only.\n- Interaction states, empty\u002Floading\u002Ferror\u002Fsuccess states, and responsive behavior.\n- Accessibility rules that affect UI implementation.\n- Pixel-perfect validation evidence for execution.\n\n## Forbidden Scope\n\nMust not plan:\n- Database schema.\n- Backend API implementation.\n- Infrastructure or deployment pipelines.\n- Security internals except user-facing trust and safety UX.\n- Product strategy beyond visual\u002FUX consequences.\n- Generic frontend tasks that do not affect the UI quality bar.\n\n## Planning Process\n\n1. Confirm the request has meaningful UI surface area.\n2. Define the feature-first target screen or flow.\n3. Declare the aesthetic direction and NOUS taste constraints.\n4. Define design-system constraints: type, spacing, color, radius, border, shadow, motion.\n5. Map components, states, responsive behavior, and accessibility requirements.\n6. Cover each relevant Refactoring UI rule explicitly.\n7. Define pixel-perfect verification steps before execution.\n\n## Output Contract\n\n```md\n## Objective\n## Domain Analysis\n## Aesthetic Direction\n## Design System Constraints\n## Specialized Tasks\n## Interaction And State Model\n## Responsive And Accessibility Rules\n## Refactoring UI Rule Coverage\n## Pixel-Perfect Review Gate\n## Dependencies\n## Risks\n## Validation Requirements\n## Success Metrics\n## Not In Scope\n```\n\n## Quality Standard\n\nA good ultra UI plan removes taste ambiguity. An engineer should know the exact hierarchy, scale, palette, states, and polish gates before writing implementation code.\n",{"name":5,"risk":53,"type":41,"version":54,"description":7},"medium","0.1.0","main","05ddbcce9e3471b880e9edc7c63e4bdd40359861","skills\u002Fnous-ui-ultra-plan","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous","https:\u002F\u002Fgithub.com\u002Fmax-kharena","2026-04-28 22:54:20",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add max-kharena\u002Fnous --skill nous-ui-ultra-plan",{"tool":67,"command":68},"bunx","bunx skills add max-kharena\u002Fnous --skill nous-ui-ultra-plan",{"tool":70,"command":71},"pnpm","pnpm dlx skills add max-kharena\u002Fnous --skill nous-ui-ultra-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fnous-ui-ultra-plan\u002FSKILL.md",true,[],[76,100,119,134,156,174],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":48},"01M71NSZ170Z45TAP4CWY74YH3","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when the user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87,88,89,90,91,92,93,32,94,95,96,97,40,39,98,99],"write a skill","write","a skill","create","structure","build","new skill","with","new agent","resources","progressive","new","progressive disclosure","Meta",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":109,"publishedAt":48},"01M71NSX1D1C2MK3NJ42E1GQ47","verification-before-completion","Use when about to claim work is complete, fixed, passing, ready, merged, shippable, reviewed, or verified.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000037","律师与法务",[110,111,40,39,112,113,114,115,116,35,117,118],"verification","verification before completion","verified","claim","complete","quality","about","work","ready",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":48},"01M71NSVRTWNA5RYBRRRBQ4830","using-nous","Use when a request needs NOUS command routing or personality-driven planning.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-nous\u002FSKILL.md",[],[126,127,128,39,40,129,130,47,131,132,133],"using nous","personality","driven","command routing","request","command","routing","router",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":48},"01M71NST398KW57VNX72Z35MC2","using-git-worktrees","Use when NOUS execution needs isolated implementation branches, phase worktrees, parallel worktrees, or safe branch setup before executing a plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[141,142,143,144,145,146,147,148,149,35,28,150,39,40,151,152,153,154,155],"git","worktrees","git worktrees","using git worktrees","Using git","execution","branch setup","implementation","safe","phase","parallel worktrees","setup","branches","branch","parallel",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":48},"01M71NSRQ1VYJT15323W6HE1X1","ubiquitous-language","Use when the user wants to define domain terms, build a glossary, harden terminology, or extract a DDD-style ubiquitous language. Saves to UBIQUITOUS_LANGUAGE.md.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Fubiquitous-language\u002FSKILL.md",[],[163,164,165,166,91,167,168,169,40,32,170,171,172,39,173],"language","ubiquitous language","define","ddd","domain","style","terminology","extract","terms","harden","glossary",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":48},"01M71NSPGTE0PY0YJ9HSDWB62B","triage-issue","Use when the user reports a bug and wants it investigated and filed as a durable GitHub issue with a TDD-based fix plan.","https:\u002F\u002Fgithub.com\u002Fmax-kharena\u002Fnous\u002Fblob\u002Fmain\u002Fskills\u002Ftriage-issue\u002FSKILL.md",[],[181,182,183,184,32,185,186,115,187,188,28,93,189,39,40,190,191],"issue","triage issue","triage","github issue","it","bug","tdd","github","reports","fix","as"]