[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF2C08N7EAT2G74S70JXWV":3,"skill-same:01M7DF2C08N7EAT2G74S70JXWV":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7DF2C08N7EAT2G74S70JXWV","frontend-design",null,"Design or critique a user-facing interface using the product, audience and project context. Use when creating or materially changing a page, component, layout, visual hierarchy, typography, color or motion; skip backend-only changes and fixes with no interface impact.","andersonmrodrigues\u002Fpaved","andersonmrodrigues","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F13907380?v=4","01M7DEV3FP2VMQZ3FP2FP1TK1C","Anderson Rodrigues","01M7DEV3GC2QAQBW4FMNT98H48",1,"MIT","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fpaved\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: frontend-design\ndescription: >-\n  Design or critique a user-facing interface using the product, audience and project context. Use when creating or materially changing a page, component, layout, visual hierarchy, typography, color or motion; skip backend-only changes and fixes with no interface impact.\n---\n\n\u003C!-- Generated by Paved plugin paved@2.29.0 from core.development.frontend-design@0.1.3; edit Paved Core instead. -->\n# Frontend design\n\n## When to use\n\nUse in feature or bug workflows when the planned change affects how people see or use a\nfrontend interface. For backend-only changes or fixes that preserve the interface, record\nthe skill as not applicable with the reason.\n\n## Required context\n\nRead the request and acceptance criteria. When available, use product and architecture\ncontext, the feature map, project rules, verification profile, and selected technology\nknowledge. If design-system or brand guidance exists in the repository, treat it as the\nsource of truth.\n\n## Preconditions\n\nKnow what the interface is for and who uses it. If the purpose, audience, or a material\nvisual choice is unclear and cannot be inferred from project context, ask the user before\ncommitting to a direction.\n\n## Procedure\n\n1. State the user need and the part of the interface in scope. Separate requested behavior\n   from assumptions about appearance.\n2. Inspect nearby screens, shared components, design tokens, content and interaction\n   patterns. Preserve them unless the request or evidence calls for a change.\n3. In the workflow plan, record a compact direction for the relevant dimensions: visual\n   hierarchy, color, type, spacing and layout, content, and interaction or motion. Tie each\n   choice to the brief or project context; omit dimensions the task does not affect.\n   For a substantial interface or flow, make the direction concrete with named palette\n   colors, type roles, a layout concept, and a rough wireframe when it helps compare options.\n   Keep small changes proportional; do not create a design-system deliverable for a one-off fix.\n4. Review the direction against the user's goals and relevant UX principles before coding.\n   Use the checklist in `references\u002Fux-principles.md` to identify applicable principles,\n   the concrete design choice they inform, and any tradeoff. Treat laws and heuristics as\n   evidence-informed guides, not universal formulas; prioritize user research, accessibility,\n   product context and explicit user direction when they conflict. Check whether visual\n   choices are grounded in this product's subject, audience, and purpose, or are defaults\n   that could be pasted into an unrelated interface. Keep a familiar or fashionable choice\n   when the brief, evidence, or established system supports it; do not apply a blacklist of\n   styles as a substitute for judgment.\n5. Implement with the project's existing components and conventions. Write interface copy\n   from the user's perspective in clear, specific terms. Use active labels that name the\n   result of an action, keep terms consistent through a flow, and make errors and empty states\n   explain what happened or what the user can do next. Keep copy and decoration useful to the\n   task; do not add motion without a user-facing purpose.\n6. Inspect the rendered result at the relevant screen sizes and states. Review screenshots\n   or previews while refining when available. Reserve the strongest visual emphasis for\n   something important to the task, and remove or justify elements that compete with it or\n   add no meaning. Check keyboard\n   operation, visible focus, readable contrast, and reduced-motion behavior. Use the\n   project's visual review tools when available; otherwise report what could not be checked.\n7. Compare the result with the plan, refine mismatches, then run the applicable verification\n   checks. Record visual review evidence when available and list any remaining gaps.\n\nWhen the interface or user flow changes, scan every group in the UX principles catalog,\ninclude relevant principles and their consequences in the design review, and briefly explain\nwhy a group does not apply when it might reasonably be expected. For substantial flow\nredesigns, address every group. Do not force an individual principle onto an unrelated\nchoice.\n\n## Tools\n\nUse the applicable project's preview, browser or screenshot tools when they are configured.\nIf none are available, inspect the implementation and run the project's available checks;\ndo not claim visual behavior was verified without seeing it.\n\n## Rules\n\n`core.architecture.follow-existing-patterns` applies when choosing how the interface fits\nthe project's existing structure and conventions.\n\n## Verification\n\nRequired: `unit` when the changed interface has testable behavior. Recommended: `e2e` for\nimportant user flows, plus the project's configured build and static-analysis checks.\n\n## Evidence\n\nRecord the relevant check results, the diff, and a screenshot or browser observation when\nthe environment supports visual review. Explain any unverified screen size or state.\n\n## Completion criteria\n\n- The interface change addresses the stated user need and follows the approved design direction.\n- Substantial visual choices and interface copy are grounded in the product and user context.\n- Relevant responsive states and interaction\u002Faccessibility basics were checked, or their\n  verification gaps are recorded.\n- The rendered result was critiqued and unnecessary visual noise was removed or justified.\n- Applicable tests and checks pass, and no unrelated visual changes remain.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Aesthetic direction is guessed | Purpose, audience or brand choices are unsupported | Read project context or ask the user before implementation |\n| A familiar template is used without a reason | Visual choices could be pasted into an unrelated product without changing their meaning | Ground the direction in the subject, audience and brief; retain familiar choices when context supports them |\n| Existing design system is bypassed | New styles or components duplicate established patterns | Reuse the existing system or document why the task needs a change |\n| Interface copy is vague or system-centered | Labels hide outcomes, terms change within a flow, or errors leave the user without a next step | Use user-facing language, name action outcomes, and make failure or empty states actionable |\n| Visual quality is claimed without review | No rendered view or interaction was inspected | Run available visual checks or report the gap |\n\n## References\n\n- [UX principles reference](references\u002Fux-principles.md) — practical design implications,\n  limits, and research sources for relevant interaction and perception principles.\n- [Frontend Design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-code\u002Fblob\u002Fmain\u002Fplugins\u002Ffrontend-design\u002Fskills\u002Ffrontend-design\u002FSKILL.md) — inspiration for subject-grounded choices and a plan-review-build-critique loop; this Paved procedure is original.\n\n\n## Paved integration\n\nUse the project-local Paved contract as the source of truth. Discover state with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" status --json`, load only relevant `.paved\u002Fproject\u002F` context, and invoke verification with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" verify --json`. Always run it from the repository being worked on, never from the plugin directory. Do not edit generated integration files or bypass Paved lifecycle and ownership checks.\n","\u003C!-- Generated by Paved plugin paved@2.29.0 from core.development.frontend-design@0.1.3; edit Paved Core instead. -->\n# Frontend design\n\n## When to use\n\nUse in feature or bug workflows when the planned change affects how people see or use a\nfrontend interface. For backend-only changes or fixes that preserve the interface, record\nthe skill as not applicable with the reason.\n\n## Required context\n\nRead the request and acceptance criteria. When available, use product and architecture\ncontext, the feature map, project rules, verification profile, and selected technology\nknowledge. If design-system or brand guidance exists in the repository, treat it as the\nsource of truth.\n\n## Preconditions\n\nKnow what the interface is for and who uses it. If the purpose, audience, or a material\nvisual choice is unclear and cannot be inferred from project context, ask the user before\ncommitting to a direction.\n\n## Procedure\n\n1. State the user need and the part of the interface in scope. Separate requested behavior\n   from assumptions about appearance.\n2. Inspect nearby screens, shared components, design tokens, content and interaction\n   patterns. Preserve them unless the request or evidence calls for a change.\n3. In the workflow plan, record a compact direction for the relevant dimensions: visual\n   hierarchy, color, type, spacing and layout, content, and interaction or motion. Tie each\n   choice to the brief or project context; omit dimensions the task does not affect.\n   For a substantial interface or flow, make the direction concrete with named palette\n   colors, type roles, a layout concept, and a rough wireframe when it helps compare options.\n   Keep small changes proportional; do not create a design-system deliverable for a one-off fix.\n4. Review the direction against the user's goals and relevant UX principles before coding.\n   Use the checklist in `references\u002Fux-principles.md` to identify applicable principles,\n   the concrete design choice they inform, and any tradeoff. Treat laws and heuristics as\n   evidence-informed guides, not universal formulas; prioritize user research, accessibility,\n   product context and explicit user direction when they conflict. Check whether visual\n   choices are grounded in this product's subject, audience, and purpose, or are defaults\n   that could be pasted into an unrelated interface. Keep a familiar or fashionable choice\n   when the brief, evidence, or established system supports it; do not apply a blacklist of\n   styles as a substitute for judgment.\n5. Implement with the project's existing components and conventions. Write interface copy\n   from the user's perspective in clear, specific terms. Use active labels that name the\n   result of an action, keep terms consistent through a flow, and make errors and empty states\n   explain what happened or what the user can do next. Keep copy and decoration useful to the\n   task; do not add motion without a user-facing purpose.\n6. Inspect the rendered result at the relevant screen sizes and states. Review screenshots\n   or previews while refining when available. Reserve the strongest visual emphasis for\n   something important to the task, and remove or justify elements that compete with it or\n   add no meaning. Check keyboard\n   operation, visible focus, readable contrast, and reduced-motion behavior. Use the\n   project's visual review tools when available; otherwise report what could not be checked.\n7. Compare the result with the plan, refine mismatches, then run the applicable verification\n   checks. Record visual review evidence when available and list any remaining gaps.\n\nWhen the interface or user flow changes, scan every group in the UX principles catalog,\ninclude relevant principles and their consequences in the design review, and briefly explain\nwhy a group does not apply when it might reasonably be expected. For substantial flow\nredesigns, address every group. Do not force an individual principle onto an unrelated\nchoice.\n\n## Tools\n\nUse the applicable project's preview, browser or screenshot tools when they are configured.\nIf none are available, inspect the implementation and run the project's available checks;\ndo not claim visual behavior was verified without seeing it.\n\n## Rules\n\n`core.architecture.follow-existing-patterns` applies when choosing how the interface fits\nthe project's existing structure and conventions.\n\n## Verification\n\nRequired: `unit` when the changed interface has testable behavior. Recommended: `e2e` for\nimportant user flows, plus the project's configured build and static-analysis checks.\n\n## Evidence\n\nRecord the relevant check results, the diff, and a screenshot or browser observation when\nthe environment supports visual review. Explain any unverified screen size or state.\n\n## Completion criteria\n\n- The interface change addresses the stated user need and follows the approved design direction.\n- Substantial visual choices and interface copy are grounded in the product and user context.\n- Relevant responsive states and interaction\u002Faccessibility basics were checked, or their\n  verification gaps are recorded.\n- The rendered result was critiqued and unnecessary visual noise was removed or justified.\n- Applicable tests and checks pass, and no unrelated visual changes remain.\n\n## Failure modes\n\n| Failure | Signal | Response |\n|---|---|---|\n| Aesthetic direction is guessed | Purpose, audience or brand choices are unsupported | Read project context or ask the user before implementation |\n| A familiar template is used without a reason | Visual choices could be pasted into an unrelated product without changing their meaning | Ground the direction in the subject, audience and brief; retain familiar choices when context supports them |\n| Existing design system is bypassed | New styles or components duplicate established patterns | Reuse the existing system or document why the task needs a change |\n| Interface copy is vague or system-centered | Labels hide outcomes, terms change within a flow, or errors leave the user without a next step | Use user-facing language, name action outcomes, and make failure or empty states actionable |\n| Visual quality is claimed without review | No rendered view or interaction was inspected | Run available visual checks or report the gap |\n\n## References\n\n- [UX principles reference](references\u002Fux-principles.md) — practical design implications,\n  limits, and research sources for relevant interaction and perception principles.\n- [Frontend Design skill](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-code\u002Fblob\u002Fmain\u002Fplugins\u002Ffrontend-design\u002Fskills\u002Ffrontend-design\u002FSKILL.md) — inspiration for subject-grounded choices and a plan-review-build-critique loop; this Paved procedure is original.\n\n\n## Paved integration\n\nUse the project-local Paved contract as the source of truth. Discover state with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" status --json`, load only relevant `.paved\u002Fproject\u002F` context, and invoke verification with `node \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fpaved.mjs\" verify --json`. Always run it from the repository being worked on, never from the plugin directory. Do not edit generated integration files or bypass Paved lifecycle and ownership checks.\n",{"name":5,"description":7},"main","1cd80f05aff924ea609012e864fa5c22c16c7d2d","plugins\u002Fclaude\u002Fpaved\u002Fskills\u002Ffrontend-design",0,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues","2026-11-14 20:09:28",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add andersonmrodrigues\u002Fpaved --skill frontend-design",{"tool":37,"command":38},"bunx","bunx skills add andersonmrodrigues\u002Fpaved --skill frontend-design",{"tool":40,"command":41},"pnpm","pnpm dlx skills add andersonmrodrigues\u002Fpaved --skill frontend-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fpaved\u002Fskills\u002Ffrontend-design\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fux-principles.md","REFERENCE","参考文档",8820,"https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Fplugins\u002Fclaude\u002Fpaved\u002Fskills\u002Ffrontend-design\u002Freferences\u002Fux-principles.md",[52,59,65,71,77,83],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7DFBWJT4T1MPBHTWT19PBEK","sample-skill","Does a sample task. Use when a sample is needed.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fvalid\u002Fsample-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DFBS6WTK30PBSW4ZS0NPWT","unexplained-contract","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Funexplained-contract\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":55,"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},"01M7DFBPJGG170V9WTMFWY73R4","shell-block","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fshell-block\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7DFBMZYR20JPTXNE5A8EFG6","project-identifier","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fproject-identifier\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DFBJ8J533DAKA3FTF54SX3","oversized","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Foversized\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DFBFAD0RYCRHTZ2JW4RX7E","no-activation","Does a sample task.","https:\u002F\u002Fgithub.com\u002Fandersonmrodrigues\u002Fpaved\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Finvalid\u002Fno-activation\u002FSKILL.md",[],[]]