Frontend Design
Ship web UIs that look intentionally designed—not generic AI layouts—by running a short design-thinking pass before implementing components, pages, or dashboards.
Overview
frontend-design is an agent skill most often used in Build (also Validate landing and prototype) that guides distinctive design thinking and implements production-grade web UI code.
Install
npx skills add https://github.com/bytedance/deer-flow --skill frontend-designWhat is this skill?
- 4-step design thinking framework: Purpose, Tone, Constraints, Differentiation before any code
- 5 aesthetic guideline areas: Typography, Color & Theme, Motion, Spatial Composition, Backgrounds & Visual Details
- Hard anti-patterns: no Inter/Roboto defaults, purple-on-white clichés, or cookie-cutter component-library-only layouts
- Commits to bold maximalist or refined minimal directions with CSS variables, motion, and layered backgrounds
- Implementation guidance to match code complexity to the chosen visual concept with deliberate polish
- 4-step design thinking framework before implementation
- 5 frontend aesthetic guideline categories (typography through backgrounds)
Adoption & trust: 2.1k installs on skills.sh; 70.7k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are shipping web UI that looks like every other gradient-and-Inter template, and you need a repeatable way to choose a real aesthetic and implement it in code.
Who is it for?
Solo builders shipping marketing pages, SaaS dashboards, or React apps who want agent-assisted design discipline and code in one pass.
Skip if: Backend-only APIs, CLI tools with no UI, or teams that already have a locked design system and only need token-compliant component assembly without creative reinterpretation.
When should I use this skill?
Building or beautifying web components, pages, dashboards, landing pages, React components, or any web UI styling when generic AI aesthetics are unacceptable.
What do I get? / Deliverables
You get a documented creative direction plus working frontend code with intentional typography, color, motion, and layout—ready to iterate or hand off to ship-phase review.
- Working frontend code for pages or components with applied aesthetic direction
- Documented tone and differentiation choices from the design-thinking pass
- CSS-level polish including typography, theme variables, motion, and background treatments
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
The skill’s core job is implementing and styling production web frontend code with explicit aesthetic rules, which maps to the Build phase shelf. Triggers center on components, pages, dashboards, React, and CSS beautification—canonical frontend work in the build/frontend subphase.
Where it fits
Define a bold landing aesthetic and implement HTML/CSS before you commit to full product build.
Prototype a dashboard or app shell with intentional typography and motion so user tests reflect real brand feel.
Implement React components and pages with the skill’s anti-pattern rules so the shipped UI does not look template-generated.
Re-run aesthetic checks when polishing UI after feature-complete but before launch QA.
How it compares
Use as a design-and-build workflow skill, not a Figma plugin or component marketplace—think structured taste rules plus implementation, not asset downloads alone.
Common Questions / FAQ
Who is frontend-design for?
Indie and solo builders using Claude Code, Cursor, Codex, or similar agents who implement their own web UI and want help escaping generic AI-looking frontends.
When should I use frontend-design?
Use it when building or restyling web components, dashboards, landing pages, or React views—especially during Validate for landing/prototype polish and during Build for production frontend passes.
Is frontend-design safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and your org’s policy before enabling it in automated agents with repo write access.
SKILL.md
READMESKILL.md - Frontend Design
Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this