frontend-design · aladicf — Claude Code skill: UI without generic AI looks
Walks the agent through a decision order: task and hierarchy first, systems next, colour and decoration last. Useful when building or reworking interfaces.
npx skills add aladicf/better-web-ui --skill frontend-design -a claude-codeWhat frontend-design does
The skill sets a working order for frontend work. Start from the specific user task, not the shell around it. Then check hierarchy in grayscale — if it does not read without colour, colour will not fix it. Constrained scales for spacing, type, radius and elevation come next, and only after that does the agent add colour, depth, motion and finishing touches.
Context gathering is a separate gate. The skill wants the target audience, the use cases and the brand tone, and it states plainly that you cannot read those out of the codebase: code shows what was built, not who it is for. If no context exists in the loaded instructions, in .better-web-ui.md, or in the legacy .better-ui.md and .impeccable.md, the agent must run $setup before anything else. Worth knowing: on a fresh project with none of those files, work starts with setup rather than markup.
The library stays framework-agnostic on purpose. Precedence runs from the existing project stack, to explicit user choices, to a default matrix only for a new unspecified project. For Next.js it advises reading the bundled docs under node_modules/next/dist/docs/ instead of trusting stale memory about the installed version. Reference material covers component anatomy, shadcn/ui accelerators, and focused patterns such as accordions, carousels and complex tables.
What it helps with
- build an interface that does not look like default model output
- get hierarchy right before adding colour
- lock spacing and type scales instead of one-off tweaking
- pick a component strategy that matches the existing stack
- rework an existing page or flow without a rewrite
Example prompts for the agent
- Build the pricing page: grayscale hierarchy first, colour after
- Rework the signup form — it looks generic right now
- Run $setup and record the project context before you start
How to install frontend-design
1Skills CLI (Vercel)
npx skills add aladicf/better-web-ui --skill frontend-design -a claude-code2Manually: put the files in place
~/.claude/skills/frontend-design/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/frontend-design/
1Skills CLI (Vercel)
npx skills add aladicf/better-web-ui --skill frontend-design -a codex2Manually: put the files in place
.agents/skills/frontend-design/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aladicf/better-web-ui --skill frontend-design -a cursor2Manually: put the files in place
.cursor/skills/frontend-design/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aladicf/better-web-ui frontend-design2Manually: put the files in place
.github/skills/frontend-design/SKILL.md1Skills CLI (Vercel)
npx skills add aladicf/better-web-ui --skill frontend-design -a gemini-cli2Platform CLI
gemini skills install https://github.com/aladicf/better-web-ui --path skills/frontend-designManually: put the files in place
.devin/skills/frontend-design/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aladicf/better-web-ui --skill frontend-design -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about frontend-design
How do I install frontend-design in Claude?
Run npx skills add aladicf/better-web-ui --skill frontend-design -a claude-code. The skill file then lives at ~/.claude/skills/frontend-design/SKILL.md.
What does frontend-design do?
It gives the agent an order of operations for interface work: feature before shell, hierarchy in grayscale, constrained scales, polish last. It also requires confirmed context — audience, use cases and brand tone.
What does the skill need to work?
Project context, taken from loaded instructions, a .better-web-ui.md file at the project root, or the legacy .better-ui.md and .impeccable.md. If none of those exist, the agent runs $setup first.
Similar skills
Everything for Frontend and UI →frontend-design by other authors comes first.