Skills
9Files
0Frontend Design
Build and polish web UI that does not look templated: an aesthetic direction before the first component, React structure and performance, purposeful motion, and a review against interface guidelines and worst-case data before shipping.
Skills, all imported unmodified:
frontend-designfrom https://github.com/anthropics/skills (Apache-2.0): design direction for new UI.redesign-existing-projectsfrom https://github.com/leonxlnx/taste-skill (MIT): audit and upgrade an existing UI.web-design-guidelines,vercel-react-best-practices,vercel-composition-patternsfrom https://github.com/vercel-labs/agent-skills (MIT): UI review, React and Next.js performance, component APIs.emil-design-eng,animate,review-animations,break-uifrom https://github.com/emilkowalski/skills (MIT): interaction polish, motion, and stress-testing a component with worst-case data.
The Playwright MCP server lets the agent open the page and look at what it built.
Start with a UI request ("design a pricing page", "redesign this dashboard", "review my UI", "break this card component").
Prerequisites: Node.js for the Playwright MCP server and a running dev server to look at; nothing else. web-design-guidelines fetches its rules from GitHub when it runs.
Not affiliated with the skills' authors. The React skills assume React or Next.js; the design skills work with any stack.
AGENTS.md
Frontend design
- In a project with a design system, tokens or a component library, use them: follow the
frontend-designskill's direction only where the project has no decision of its own, and never introduce a second styling approach. - For new UI start from the
frontend-designskill; to improve existing UI start from theredesign-existing-projectsskill and keep the behaviour unchanged.
Agents
0- Nothing here yet
MCP servers
1- playwright