frontend-design

Design, build, and review polished frontend interfaces with role-based design systems.

2|Updated May 14, 2026
One-click install
npx skills add https://github.com/AnthonyPoschen/agent-skills --skill frontend-design-anthonyposchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design
Source: https://github.com/AnthonyPoschen/agent-skills/tree/main/skills/frontend-design
Command: npx skills add https://github.com/AnthonyPoschen/agent-skills --skill frontend-design-anthonyposchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend work often ships as generic, templated UI that ignores the product's actual workflow, content states, and visual identity. This Skill guides the design and implementation of web interfaces so screens are built around the user's task, use deliberate color and type systems, support both dark and light themes, and are visually verified in a real browser before handoff. ## Core Features & Use Cases - Design consultation and durable records: Captures outcome, audience, workflow, states, constraints, and visual direction in a project DESIGN.md, with a reusable brief template for substantial flows and redesigns. - Role-based visual systems: Defines palettes by semantic roles (surfaces, ink, one accent, semantic states), compact type scales, and a single signature element, while avoiding overused AI-default aesthetics. - Screen-type guidance: Provides concrete patterns for text-heavy pages, complex forms, and data-dense dashboards, plus complete interaction states (hover, focus, loading, empty, error, success). - Browser-based visual verification: Requires inspecting the rendered interface with browser-use or computer-use tools at desktop and narrow widths in both prefers-color-scheme themes before handoff. - Use Case: When asked to restyle a settings page, the Skill establishes the design direction, implements the change within the project's existing framework, then screenshots both themes to confirm hierarchy, contrast, and state coverage. ## Quick Start Redesign the account settings page of this project with a clear visual direction, then verify it in the browser in both dark and light themes.

Frequently Asked Questions about frontend-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a frontend interface that doesn't look like generic AI output?▼

Write a compact plan before coding: 4-6 named hex colors with roles, a characterful display face plus body face, a layout concept, and one signature element. Avoid the common AI-default clusters like cream with terracotta or dark gray with a single green accent unless the brief specifically justifies them.

How to implement dark and light themes in CSS?▼

Define both themes with the prefers-color-scheme media query so the interface follows the user's OS or browser setting. Build the palette by roles (surfaces, ink, accent, semantic states) with tonal steps, then visually inspect both schemes in a browser rather than trusting the CSS alone.

What should a design brief for a new UI flow include?▼

Capture the user outcome and primary action, audience and context, the workflow with edge cases, content and required states, constraints, visual direction with references and anti-references, and scope. The Skill provides a DESIGN.md template in references/design-brief.md for this structure.

Does this Skill work with an existing component library or CSS framework?▼

Yes. It instructs following the project's established framework, component library, CSS approach, and design tokens when they are coherent, improving only the touched surface rather than rewriting unrelated areas.

Why is screenshot inspection required instead of reviewing the code?▼

Markup and CSS are not visual proof; rendered pages reveal cramped hierarchy, accidental spacing, and weak feedback that source code hides. The Skill requires capturing desktop and narrow viewports in both themes and fixing what the screenshots show.

When should a project split DESIGN.md into multiple files?▼

Split when DESIGN.md exceeds about 1,000 lines or its areas develop independent owners and change histories. Keep the root file as a router with shared decisions and an index, moving individual briefs to lowercase kebab-case files under design/.