Design System
WrongStack/WrongStack
Use this skill BEFORE writing or restyling ANY user-facing interface.
Builds distinctive, production-grade UIs that avoid generic AI aesthetics.
Install Frontend Design
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avibebuilder/claude-prime frontend-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/frontend-design .claude/skills/frontend-design && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .claude/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-designType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avibebuilder/claude-prime frontend-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/frontend-design .agents/skills/frontend-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .agents/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avibebuilder/claude-prime frontend-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/frontend-design .cursor/skills/frontend-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .cursor/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/avibebuilder/claude-prime.git --path .claude/skills/frontend-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avibebuilder/claude-prime frontend-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/frontend-design .gemini/skills/frontend-design && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .gemini/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install avibebuilder/claude-prime frontend-designInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/frontend-design .github/skills/frontend-design && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .github/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avibebuilder/claude-prime --skill frontend-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avibebuilder/claude-prime frontend-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/frontend-design .opencode/skills/frontend-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontend-design" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/frontend-design into .opencode/skills/frontend-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-design", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontend-design- GitHub stars
- 120
- Token cost
- ~2.1k tokens
- SKILL.md length
- 928 words
- Files
- 7 (incl. scripts, references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Builds distinctive, production-grade UIs that avoid generic AI aesthetics.
- Works in 4 steps: Start with the smallest query that… → Use auto-detection first; add --domain… → Add --stack when framework-specific… → …
- The user wants to build
- SKILL.md covers Design Thinking, Frontend Aesthetics Guidelines, Design Intelligence and Gotchas, plus 1 more section
- Runs Python scripts from its folder; calls python3
What it does
Frontend Design is an agent skill from avibebuilder/claude-prime. Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Use whenever the user wants to build, restyle, or give visual direction to any interface — pages, dashboards, landing pages, components, onboarding flows, mobile screens, or design systems — even without an explicit 'design' request. Also triggers for: picking an aesthetic direction, improving the look of a dull/generic existing page, adding visual personality, or choosing colors/typography. Includes a bundled design intelligence database…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts and reference files (for example `references/design-system-generation.md`, `references/quality-checklist.md` and `scripts/core.py`).
It sits in Frontend & Design, covering Cross-platform mobile apps, Typography and CSS and styling. It works with React, Vue.js, Flutter and Next.js. The repository describes itself as: You've heard Claude Code can do amazing things. Skills, hooks, agents, memory systems — but who has time to figure all that out? Claude Prime sets it up for you in one command. The licence is MIT.
When your agent uses it
- The user wants to build
- Give visual direction to any interface — pages
- Onboarding flows
- Design systems — even without an explicit design request
Example prompts
- “design”
- “Use the frontend-design skill to build distinctive, production-grade UIs that avoid generic AI aesthetics”
- “/frontend-design”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Start with the smallest query that captures the product or interface type.
- Use auto-detection first; add --domain only when you know what kind of answer you need.
- Add --stack when framework-specific implementation details matter.
- Synthesize the retrieved guidance into one cohesive direction instead of pasting disconnected search results into the final answer.
What it can do on your machine
Read from SKILL.md and the folder at commit 80bcfa4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontend Design loads about 2.1k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 161 tokens; SKILL.md has 928 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from avibebuilder/claude-prime at commit 80bcfa4, republished under its MIT licence (© avibebuilder). 928 words, ~2,105 tokens.
Download SKILL.mdSave it as
.claude/skills/frontend-design/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- frontend-design
- description
- Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Use whenever the user wants to build, restyle, or give visual direction to any interface — pages, dashboards, landing pages, components, onboarding flows, mobile screens, or design systems — even without an explicit 'design' request. Also triggers for: picking an aesthetic direction, improving the look of a dull/generic existing page, adding visual personality, or choosing colors/typography. Includes a bundled design intelligence database for concrete guidance across web (React, Next.js, Vue, Tailwind) and mobile (React Native, Flutter, SwiftUI).
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 to spacing, typography, and subtle details. Elegance comes from executing the vision well.
Design Intelligence
Use the bundled design search tooling when you need concrete guidance that should shape implementation rather than generic inspiration.
Reach for .claude/skills/frontend-design/scripts/search.py when you need any of the following:
- a style direction that fits a product category or audience
- a color system, typography pairing, or chart recommendation
- UX or accessibility guidance for a specific interface problem
- stack-specific frontend advice for React, Next.js, Vue, Tailwind, and other supported stacks
- a full design-system recommendation grounded in the bundled dataset
Skip the search when the user already gave a precise visual direction and the implementation path is obvious.
Show full SKILL.md (358 more words)Show less
Search Workflow
- Start with the smallest query that captures the product or interface type.
- Use auto-detection first; add
--domainonly when you know what kind of answer you need. - Add
--stackwhen framework-specific implementation details matter. - Synthesize the retrieved guidance into one cohesive direction instead of pasting disconnected search results into the final answer.
Quick Start
# Auto-detect the best domain from a concise query
python3 .claude/skills/frontend-design/scripts/search.py "glassmorphism dark mode"
# Ask for a specific kind of guidance
python3 .claude/skills/frontend-design/scripts/search.py "healthcare saas" --domain colors
# Add framework context when implementation details matter
python3 .claude/skills/frontend-design/scripts/search.py "responsive layout" --stack html-tailwindHigh-Value Defaults
Treat these as strong defaults, not blind rules:
- Prefer SVG icon systems over emoji so the UI feels product-grade and stylistically consistent.
- Keep clickable elements obviously interactive, including pointer cues where the platform expects them.
- Protect readability first; contrast and hierarchy matter more than visual gimmicks.
- In light mode, translucent surfaces need enough opacity to stay legible.
- Floating elements look more intentional when they breathe instead of touching viewport edges.
- Prefer hover treatments that preserve layout stability unless movement is a deliberate part of the concept.
References
references/design-system-generation.md— use when the user wants a full design-system or style-guide recommendation for a project type (e.g. "SaaS dashboard", "e-commerce luxury", "fintech app") assembled from multiple search domainsreferences/quality-checklist.md— use as the final self-critique pass before delivering UI work
Gotchas
- Defaulting to safe choices: Inter font + blue primary + white background is AI slop. Be distinctive.
- Using search as decoration: Retrieved guidance should change the design system or implementation decisions, not just add buzzwords.
- Inconsistent design system: Don't mix unrelated tokens or visual languages. Commit to one system throughout.
- Ignoring contrast ratios: WCAG AA minimum. Beautiful but unreadable is a failure.
- Purple gradients: The #1 AI cliché. Avoid unless specifically requested.
- Interaction polish gaps: Missing hover/focus states or weak affordances make even strong visuals feel unfinished.
Data Source
Remote: ui-ux-pro-max-skill
Available domains include styles, colors, typography, charts, products, landing, ux, icons, ui-reasoning, and web-interface. Supported stacks include html-tailwind, react, nextjs, astro, vue, nuxtjs, nuxt-ui, svelte, swiftui, react-native, flutter, shadcn, and jetpack-compose.
Search uses a cached BM25 ranking script over the remote dataset, so prefer concise, concrete queries over long prompt-like paragraphs.
Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.
© avibebuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts, references) in .claude/skills/frontend-design of avibebuilder/claude-prime.
- SKILL.md
- references/design-system-generation.md
- references/quality-checklist.md
- scripts/.gitignore
- scripts/core.py
- scripts/search.py
- scripts/tests/test_search.py
Open the folder on GitHubat commit 80bcfa4
Compare with similar skills
Frontend Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontend Design this skillavibebuilder/claude-prime | 120 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Design SystemWrongStack/WrongStack | 368 | — | ~3.9k | Automated safety check: Pass | MIT | |
| UI UX Pro Maxmajiayu000/spellbook | 286 | — | ~442 | Automated safety check: Pass | MIT | |
| UI UX Pro Maxsaoudi-h/solar-icons | 182 | 18 repos | ~11k | Automated safety check: Notes | Custom licence | |
| UI UX Pro Maxshobcoder/shob | 577 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Frontend UI StandardsMaxHan7/frontend-ui-standards-skill | 106 | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
UI UX Pro Max
majiayu000/spellbook
A skill your agent uses when planning, building, designing, code review, refactor, fixing, improving, optimizing, enhancing, or checking UI/UX work.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
UI UX Pro Max
shobcoder/shob
UI/UX design intelligence expert for web and mobile applications.
Frontend UI Standards
MaxHan7/frontend-ui-standards-skill
A skill your agent uses when implementing, refactoring, or reviewing frontend UI across SwiftUI, React, React Native, Flutter, web, or mobile apps.
UI/UX Design System Advisor
Galaxy-Dawn/claude-scholar
Turns a vague UI request into a concrete design system with style, palette, typography and layout guidance from a search script, plus stack-specific implementation advice.
More from avibebuilder/claude-prime
All 19 skills in this repoDiagnose
avibebuilder/claude-prime
Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.
Media Processor
avibebuilder/claude-prime
Specialized visual and multimedia processing tools. An agent skill from avibebuilder/claude-prime.
Skill Creator
avibebuilder/claude-prime
A skill your agent uses when the user wants to work on a Claude Code skill file (SKILL.md): writing one from scratch, testing whether an existing one works well, running evals or benchmarks…
Self Evolve
avibebuilder/claude-prime
The single config quality skill. An agent skill from avibebuilder/claude-prime.
Cook
avibebuilder/claude-prime
Implement, build, create, or add any feature, endpoint, page, component, or functionality.
Prime Sync
avibebuilder/claude-prime
Syncs Claude config between prime repo and target projects. An agent skill from avibebuilder/claude-prime.
Related
Categories
Questions about Frontend Design
What does Frontend Design do?
Builds distinctive, production-grade UIs that avoid generic AI aesthetics. Frontend Design is an agent skill from avibebuilder/claude-prime. Builds distinctive, production-grade UIs that avoid generic AI aesthetics.
When should I use Frontend Design?
Frontend Design fits situations like: the user wants to build; give visual direction to any interface — pages; onboarding flows; design systems — even without an explicit design request.
How do I install Frontend Design in Claude Code?
Run `npx skills add avibebuilder/claude-prime --skill frontend-design -a claude-code`. Or copy the skill folder (.claude/skills/frontend-design in avibebuilder/claude-prime) into .claude/skills/frontend-design in your project. Claude Code loads it when a task matches its description.
How do I install Frontend Design in Codex?
Run `npx skills add avibebuilder/claude-prime --skill frontend-design -a codex`. Or copy the skill folder (.claude/skills/frontend-design in avibebuilder/claude-prime) into .agents/skills/frontend-design in your project. Codex loads it when a task matches its description.
Can I use Frontend Design in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avibebuilder/claude-prime --skill frontend-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-design, .gemini/skills/frontend-design, .github/skills/frontend-design and .opencode/skills/frontend-design in your project.
What does Frontend Design need to run?
Going by SKILL.md and its folder, Frontend Design needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Frontend Design access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Frontend Design safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Frontend Design use?
Frontend Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontend Design use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Frontend Design?
Skills that share tags, products or a category with Frontend Design: Design System (WrongStack/WrongStack, 368 stars), UI UX Pro Max (majiayu000/spellbook, 286 stars), UI UX Pro Max (saoudi-h/solar-icons, 182 stars) and UI UX Pro Max (shobcoder/shob, 577 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontend Design?
avibebuilder (a GitHub organization) maintains it in avibebuilder/claude-prime, which has 120 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on May 16, 2026.
Source: avibebuilder/claude-prime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.