frontend-design
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.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- frontend-design
- description
- 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.
02 资源文件 1
- 参考文档references/ux-principles.md8.6 KB
03 SKILL.md 正文
<!-- Generated by Paved plugin paved@2.29.0 from core.development.frontend-design@0.1.3; edit Paved Core instead. -->
Frontend design
When to use
Use in feature or bug workflows when the planned change affects how people see or use a frontend interface. For backend-only changes or fixes that preserve the interface, record the skill as not applicable with the reason.
Required context
Read the request and acceptance criteria. When available, use product and architecture context, the feature map, project rules, verification profile, and selected technology knowledge. If design-system or brand guidance exists in the repository, treat it as the source of truth.
Preconditions
Know what the interface is for and who uses it. If the purpose, audience, or a material visual choice is unclear and cannot be inferred from project context, ask the user before committing to a direction.
Procedure
- State the user need and the part of the interface in scope. Separate requested behavior from assumptions about appearance.
- Inspect nearby screens, shared components, design tokens, content and interaction patterns. Preserve them unless the request or evidence calls for a change.
- In the workflow plan, record a compact direction for the relevant dimensions: visual hierarchy, color, type, spacing and layout, content, and interaction or motion. Tie each choice to the brief or project context; omit dimensions the task does not affect. For a substantial interface or flow, make the direction concrete with named palette colors, type roles, a layout concept, and a rough wireframe when it helps compare options. Keep small changes proportional; do not create a design-system deliverable for a one-off fix.
- Review the direction against the user's goals and relevant UX principles before coding.
Use the checklist in
references/ux-principles.mdto identify applicable principles, the concrete design choice they inform, and any tradeoff. Treat laws and heuristics as evidence-informed guides, not universal formulas; prioritize user research, accessibility, product context and explicit user direction when they conflict. Check whether visual choices are grounded in this product's subject, audience, and purpose, or are defaults that could be pasted into an unrelated interface. Keep a familiar or fashionable choice when the brief, evidence, or established system supports it; do not apply a blacklist of styles as a substitute for judgment. - Implement with the project's existing components and conventions. Write interface copy from the user's perspective in clear, specific terms. Use active labels that name the result of an action, keep terms consistent through a flow, and make errors and empty states explain what happened or what the user can do next. Keep copy and decoration useful to the task; do not add motion without a user-facing purpose.
- Inspect the rendered result at the relevant screen sizes and states. Review screenshots or previews while refining when available. Reserve the strongest visual emphasis for something important to the task, and remove or justify elements that compete with it or add no meaning. Check keyboard operation, visible focus, readable contrast, and reduced-motion behavior. Use the project's visual review tools when available; otherwise report what could not be checked.
- Compare the result with the plan, refine mismatches, then run the applicable verification checks. Record visual review evidence when available and list any remaining gaps.
When the interface or user flow changes, scan every group in the UX principles catalog, include relevant principles and their consequences in the design review, and briefly explain why a group does not apply when it might reasonably be expected. For substantial flow redesigns, address every group. Do not force an individual principle onto an unrelated choice.
Tools
Use the applicable project's preview, browser or screenshot tools when they are configured. If none are available, inspect the implementation and run the project's available checks; do not claim visual behavior was verified without seeing it.
Rules
core.architecture.follow-existing-patterns applies when choosing how the interface fits
the project's existing structure and conventions.
Verification
Required: unit when the changed interface has testable behavior. Recommended: e2e for
important user flows, plus the project's configured build and static-analysis checks.
Evidence
Record the relevant check results, the diff, and a screenshot or browser observation when the environment supports visual review. Explain any unverified screen size or state.
Completion criteria
- The interface change addresses the stated user need and follows the approved design direction.
- Substantial visual choices and interface copy are grounded in the product and user context.
- Relevant responsive states and interaction/accessibility basics were checked, or their verification gaps are recorded.
- The rendered result was critiqued and unnecessary visual noise was removed or justified.
- Applicable tests and checks pass, and no unrelated visual changes remain.
Failure modes
| Failure | Signal | Response |
|---|---|---|
| Aesthetic direction is guessed | Purpose, audience or brand choices are unsupported | Read project context or ask the user before implementation |
| 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 |
| Existing design system is bypassed | New styles or components duplicate established patterns | Reuse the existing system or document why the task needs a change |
| 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 |
| Visual quality is claimed without review | No rendered view or interaction was inspected | Run available visual checks or report the gap |
References
- UX principles reference — practical design implications, limits, and research sources for relevant interaction and perception principles.
- Frontend Design skill — inspiration for subject-grounded choices and a plan-review-build-critique loop; this Paved procedure is original.
Paved integration
Use the project-local Paved contract as the source of truth. Discover state with node "${CLAUDE_PLUGIN_ROOT}/scripts/paved.mjs" status --json, load only relevant .paved/project/ context, and invoke verification with node "${CLAUDE_PLUGIN_ROOT}/scripts/paved.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.
04 同仓库更多 Skills
sample-skill
Does a sample task. Use when a sample is needed.
unexplained-contract
Does a sample task. Use when a sample is needed.
shell-block
Does a sample task. Use when a sample is needed.
project-identifier
Does a sample task. Use when a sample is needed.
oversized
Does a sample task. Use when a sample is needed.
no-activation
Does a sample task.