AGENT SKILL

frontend-design

Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.

License 许可
Apache-2.0
最近更新
2026-07-09
Stars
★ 0
Forks
0

01 前言 Front Matter

od
{ "mode": "prototype", "craft": { "requires": [ "typography", "color", "anti-ai-slop", "state-coverage" ] }, "category": "web-artifacts", "upstream": "https://github.com/anthropics/skills/tree/main/skills/frontend-design", "design_system": { "requires": true, "sections": [ "color", "typography", "layout", "components" ] }, "example_prompt": "Design and build a production-quality SaaS analytics dashboard for a finance team, with real interaction states, refined typography, and a distinctive visual direction." }
name
frontend-design
license
Complete terms in LICENSE.txt
triggers
[ "frontend design", "ui design", "ux design", "web design", "production ui", "landing page", "dashboard design", "react component design", "frontend playbook", "restrained ui", "ui composition", "cinematic frontend", "hero page", "showcase site" ]
description
Create distinctive, production-grade frontend interfaces with strong visual direction, polished typography, considered layout, and working HTML/CSS/JS or framework code. Use for websites, landing pages, dashboards, React components, application screens, and UI beautification.

02 资源文件 6

03 SKILL.md 正文

frontend-design

Adapted from Anthropic's official frontend-design skill for Open Design.

Use this skill when the user asks to build or improve a frontend interface: a website, landing page, dashboard, application screen, HTML/CSS artifact, React/Vue/Svelte component, or a visual redesign of an existing UI.

The goal is not just "make it nicer." The goal is to ship working frontend code with a clear design point of view, strong craft, and enough product detail that the result feels designed for the user's actual context.

Workflow

  1. Understand the brief before choosing the look.

    • Identify the audience, primary job, domain, and emotional tone.
    • Note any technical constraints: framework, existing styles, accessibility, performance, export target, or responsive requirements.
    • If the repo already has design tokens, components, screenshots, or a DESIGN.md, use those as the source of truth.
  2. Commit to one specific aesthetic direction.

    • Pick a direction that fits the product: brutally minimal, editorial, luxury, playful, industrial, retro-futuristic, dense operational, calm enterprise, artful consumer, or another precise direction.
    • Make the direction concrete through typography, spacing, color, hierarchy, motion, and component shape.
    • Avoid generic AI defaults: purple-blue gradients, vague glass cards, interchangeable SaaS layouts, over-rounded cards, stock icon rows, and decorative blobs that do not serve the interface.
  3. Design the real interface, not a placeholder poster.

    • Include the controls, empty/loading/error states, tables, filters, navigation, and responsive behavior a real user would expect.
    • Use honest content. If data is unknown, label it as sample, pending, or unavailable instead of inventing claims.
    • Keep workflows efficient for the target user. Dashboards and tools should be scannable and dense enough for repeated use; marketing pages can be more expressive.
  4. Build production-grade frontend code.

    • Prefer the repository's existing framework, component conventions, icons, tokens, and styling approach.
    • For standalone artifacts, create self-contained HTML/CSS/JS unless the user asked for a framework.
    • Use semantic markup, keyboard-accessible controls, visible focus states, sensible contrast, and responsive layout constraints.
    • Use CSS variables for repeated colors, spacing, shadows, and type scale.
  5. Refine visual craft.

    • Typography: choose expressive but readable type pairings. Avoid using default system stacks as the main visual idea unless the direction is intentionally utilitarian.
    • Color: create a balanced palette with role clarity. Use accent color sparingly and deliberately.
    • Layout: use alignment, rhythm, density, and negative space intentionally. Do not let cards, panels, or labels drift.
    • Motion: add purposeful transitions for state changes, reveals, and feedback. Prefer transforms and opacity for performance.
    • Details: use texture, borders, shadows, dividers, media, and iconography only when they support the concept.
  6. Self-review before final delivery.

    • The interface works at mobile and desktop widths.
    • Text fits its containers and does not overlap adjacent UI.
    • Interactive elements have hover/focus/active/disabled states.
    • The design avoids obvious AI-generated visual tropes.
    • The result has one memorable quality a user could describe after closing the page.

Reference library

Don't reinvent layout, spacing, state, or responsive decisions from scratch — this skill ships a reference library for the parts that recur across every frontend build:

  • references/layout-systems.md — composition archetypes (dashboard shell, split hero, data-dense table view, settings/detail layout) and when grid vs. flex is the right tool. For landing/marketing pages specifically, prefer design-templates/web-prototype's paste-ready section skeletons (references/layouts.md there) over inventing a new hero/feature-row layout here — this file covers the app-shell and dashboard layouts that skill doesn't.
  • references/spacing-discipline.md — the spacing scale, section rhythm, and negative-space rules that keep density intentional instead of accidental.
  • references/component-states.md — how to author every interactive component's state set. This cross-references craft/state-coverage.md for which states are required (loading/empty/error/populated/edge) and adds the frontend-specific authoring workflow: build and screenshot each state in isolation before wiring them into the real data flow.
  • references/responsive-strategy.md — breakpoint strategy, mobile vs. desktop-first decision rule, and container-query use cases.
  • references/before-after.md — a worked before/after: a generic AI-default dashboard fragment next to the same fragment rebuilt with this skill's workflow (named direction, all five states, spacing scale). This is a functional skill's worked example, not a single fixed rendering artifact — deliberately not shipped as a baked example.html, since this skill applies to any prototype brief rather than being itself one curated design-template deliverable (see specs/current/skills-and-design- templates.md's skills-vs-design-templates split).

Self-check checklist

  • [ ] One aesthetic direction was named explicitly (not "clean and modern") and is traceable in typography, color, and layout choices.
  • [ ] Every interactive surface renders all five required states from craft/state-coverage.md (loading, empty, error, populated, edge) — not just populated.
  • [ ] The interface works at mobile and desktop widths per references/responsive-strategy.md — verified, not assumed.
  • [ ] No generic AI tells: purple-blue gradients, vague glass cards, 3-card icon rows with filler copy, oversized rounded cards everywhere (craft/anti-ai-slop.md).
  • [ ] Text fits its containers at both narrow and wide/long content extremes (references/component-states.md's edge-state note).
  • [ ] Every focusable element has visible hover/focus/active/disabled states.
  • [ ] The result has one memorable, describable quality — not an interchangeable SaaS template.

Open Design Integration

When Open Design provides an active design system, treat it as the product's brand contract. Use the injected color, typography, layout, and component guidance first, then apply this skill's frontend craft rules where the design system is silent.

When Open Design injects craft references such as typography, color, anti-ai-slop, and state-coverage, apply those checks before finishing. If the user's brand guidance conflicts with a generic craft rule, the user's brand guidance wins.

Source

This entry consolidates three previously-separate catalogue stubs that overlapped in scope and trigger phrases — frontend-design (Anthropic), frontend-skill (OpenAI), and frontend-dev (MiniMax AI) — into one skill rather than shipping three thin, competing pointers for the same "build me a good-looking frontend" ask. None of the three shipped vendorable content beyond a short description, so the merge is a scope consolidation, not a content merge; this skill's body and references/ are original.

Example

See references/before-after.md for the worked before/after.

License

This skill is adapted from Anthropic's official skills repository. See LICENSE.txt in this folder for the upstream Apache-2.0 license terms. The frontend-skill and frontend-dev stubs folded into this entry carried no vendored content of their own (short descriptions only), so no additional license terms apply from those sources.

04 同仓库更多 Skills