Skip to content
Design

Frontend Design

Develop a deliberate visual direction for a new interface or a substantial redesign.

Install with Skills CLI
npx skills add anthropics/skills --skill frontend-design

What it does

An interface can satisfy a feature list yet look like an unrelated template. Frontend Design helps an agent connect typography, layout, color, and written content to the actual product and audience.

What changes after install

  • Starts with the subject, audience, and primary job of the interface.
  • Builds and critiques a compact visual plan before implementation.
  • Encourages responsive behavior, visible focus, readable content, and restrained motion.

Install

Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.

Install with Skills CLI
npx skills add anthropics/skills --skill frontend-design

Before using Frontend Design

  • Give the agent the interface brief, target framework and existing project conventions. Running the generated interface requires that project’s own build and preview dependencies.

Read the reviewed setup instructions for the selected workflow.

When to use it

  • Designing a new landing page or interface with a clear product brief.
  • Reworking a generic-looking UI into a consistent visual direction.

When not to use it

  • Replacing an established design system during a narrowly scoped maintenance fix.

A worked example

“Design a booking page for a neighborhood pottery studio. Show class dates clearly and help first-time visitors choose a session.” Supply an actual studio photo, its wordmark, and two class records. In this example Saturday wheel throwing is full and Sunday hand building has three places. Include the duration, price and experience level for both. Ask for a page that a visitor can use with a phone on the way to the studio.

  1. Read the records and identify the decision a new visitor must make. Someone with no pottery experience needs to know which session welcomes beginners and whether they can book it. Put the class name, date, availability and action within reach of each other in the layout sketch. A beautiful photograph cannot supply a missing Sunday date.
  2. Sketch two arrangements before coding. One could use a photograph over a compact timetable; another could place a small image of the finished piece next to each class. Pick the arrangement that fits the actual number of sessions and the available photos. Giving two unrelated classes the same cropped photograph would make them harder to distinguish.
  3. Choose the palette, type roles and spacing from the studio material and the existing site. Write down what each color does, including text, background, available action and the full state. Review the choices against the brief. A clay-colored accent is defensible if it comes from the studio’s work; a terracotta button can still be hard to read against a photograph of the same clay.
  4. Build the page with the project’s existing components where they fit. Keep the supplied class names intact and attach each booking action to its own class. If a waitlist has not been supplied, show the full state without inventing a working waitlist. The user asked for an interface and supplied two records, not a new reservation service.
  5. Review the result with the real records at a narrow width. Starting from the page title, try to find the next beginner-friendly session, read its price and reach the booking action using the keyboard. If both buttons merely read “Book,” inspect their surrounding headings and the destination each receives before handing the page back.

Upstream instructions: SKILL.md.

Troubleshooting

  • The booking button belongs to Sunday but appears directly beneath Saturday on mobile. Inspect how the timetable rearranges when columns collapse. Keep the action in the same session container as its class name and date. Try a longer class title to see whether line wrapping separates the control from the information it acts on.
  • A call to action has the right color but almost no padding. Inspect the computed styles on that button and identify which component or section selector supplies its spacing. The upstream guide flags overlapping CSS selectors. Make the smallest adjustment at the right level and revisit another button using the same component.
  • Keyboard users lose their place after expanding the session details. Tab through the controls and watch the focus indicator against the actual background. Check the next tab stop after expansion and after closing the details. Keep the expanded information readable when reduced motion is enabled; an animated reveal should not be the only way to notice the change.

How it chooses an approach

Use the brief to decide where the page should be distinctive. An image of hands shaping a vessel can anchor this particular studio page while the schedule remains plain and easy to scan. A directory of twenty class dates might instead give the timetable the most space. Pick one element that earns the attention. Repeated labels, badges and decorative numbering take space away from a decision if there are only two sessions to compare.

The skill itself is design guidance. The project determines the framework, available components and development dependencies. For an established site, inspect its booking button, type scale and date conventions first. Preserve the behaviors visitors already know. For a new interface, the short design plan can settle the page hierarchy before time goes into implementing two competing layouts.

Use content from the actual subject. A visitor deciding between wheel throwing and hand building needs different information from someone browsing a gallery. Replace a generic slogan with the supplied experience level or class duration if that answers the visitor’s next question. Leave out testimonials, discounts or availability counts unless the studio supplied them.

When to use another skill

Frontend Design guides visual and interaction choices. Web Artifacts Builder supplies a particular setup and bundling workflow when the handoff calls for a self-contained interactive artifact. If the studio wants a printed notice for its window, carry the approved class names, dates and venue into a static layout instead. A printed piece has no booking button, so the studio must supply the destination it wants printed.

What to check after it runs

  • Open the page at a narrow phone width and read both complete class names, dates, prices and availability states. Check the longest class title against the button below it. Rotate or resize the viewport and look for clipped words or a schedule that requires sideways scrolling.
  • Starting from the top of the page, use only the keyboard to find Sunday, open its details and reach the booking action. Check the visible focus indicator over both the photograph and the plain background. Confirm that the full Saturday class cannot accidentally start a Sunday booking.
  • Compare the displayed schedule with the two supplied records. Follow each working action to its destination and check the class identifier where the receiving page exposes it. A correct URL with the wrong session parameter would send a visitor to the wrong class.
  • Inspect the page with reduced motion enabled. The availability and price should be readable immediately, and showing or hiding details should leave focus in a predictable place. Capture a narrow and a wide view and use them to explain any remaining limitation to the studio.

More in Design

Related skills in other categories

FAQ

Does this skill provide a ready-made component library?
No. Its focus is design direction and critique. The implementation still uses the framework and components chosen for the project.
Will it always add unusual fonts or animation?
No. The source prioritizes the brief and deliberate choices, with restrained motion and accessible, responsive behavior.