Frontend Design
Install this when you want an agent to ship distinctive, production-grade web UI with a deliberate aesthetic instead of generic template styling.
Overview
frontend-design is an agent skill most often used in Build (also Validate prototype, Ship review) that creates distinctive, production-grade web interfaces with intentional aesthetics instead of generic AI styling.
Install
npx skills add https://github.com/am-will/codex-skills --skill frontend-designWhat is this skill?
- Design-thinking gate: purpose, tone, constraints, and a bold differentiation hook before coding
- Commits to an extreme aesthetic direction (minimal, brutalist, editorial, retro-futuristic, etc.) rather than default gr
- Produces real working frontend code with meticulous visual detail
- Explicitly avoids generic “AI slop” aesthetics and cookie-cutter layouts
- Frames requirements as component, page, or full-application builds with audience context
- Design-thinking framework with four decision pillars: Purpose, Tone, Constraints, Differentiation
Adoption & trust: 1.3k installs on skills.sh; 941 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You asked for a web UI and keep getting polished but interchangeable “AI slop” that does not match your product’s personality or audience.
Who is it for?
Solo builders who need a bold, cohesive visual system for a landing page, app shell, or component library and want working code—not mood boards only.
Skip if: Pure backend/API work, CLI tools with no UI, or cases where an approved design system forbids any visual exploration.
When should I use this skill?
The user asks to build web components, pages, or applications and wants high design quality that avoids generic AI aesthetics.
What do I get? / Deliverables
You get implemented frontend code anchored to a clear aesthetic direction, with creative choices that make the interface memorable and on-brand.
- Working frontend interface code with a defined aesthetic direction
- Documented design rationale (purpose, tone, differentiation) in the implementation thread
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Most interface construction happens in Build, but the skill’s design-thinking gate is equally valuable while scoping clickable prototypes before full implementation. Components, pages, and applications are frontend deliverables; the skill explicitly targets web interface code quality and visual identity.
Where it fits
Shape a clickable landing prototype with a committed retro-futuristic tone before you invest in full app build.
Implement a dashboard shell where typography and layout reinforce a luxury/refined brand for solo SaaS users.
Refresh a marketing page so share screenshots look intentional rather than template-generated.
How it compares
A design-led implementation workflow—not a component catalog integration or automated Lighthouse perf pass.
Common Questions / FAQ
Who is frontend-design for?
Indie founders and developers using coding agents to build web components, pages, or apps who care about distinctive visual quality.
When should I use frontend-design?
In Validate (prototype) to nail tone before build; in Build (frontend) for production UI; when refreshing Launch-facing pages that must stand out in search and social previews.
Is frontend-design safe to install?
Check the Security Audits panel on this Prism page and the skill’s LICENSE.txt terms before adding it to your agent stack.
SKILL.md
READMESKILL.md - Frontend Design
This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. ## Design Thinking Before coding, understand the context and commit to a BOLD aesthetic direction: - **Purpose**: What problem does this interface solve? Who uses it? - **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction. - **Constraints**: Technical requirements (framework, performance, accessibility). - **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember? **CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity. Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is: - Production-grade and functional - Visually striking and memorable - Cohesive with a clear aesthetic point-of-view - Meticulously refined in every detail ## Frontend Aesthetics Guidelines Focus on: - **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font. - **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes. - **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise. - **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density. - **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays. NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character. Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations. **IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention t