Take 01
Discover.
Read the project before touching it: routes, tokens, fonts, assets, constraints and the ambition the brief really asks for.
You getYour constraints, scoped and written down
Premium Frontend Director is an open-source Agent Skill for Claude Code, Codex and compatible agents. It guides them to art-direct a frontend, build it, and prove it in a real browser against 11 named quality gates.
Same object. New light. Direction decides what changes, and what stays.
Not another prompt for prettier buttons. A disciplined workflow that takes a project from raw material to a directed, proven experience, in five takes.
Take 01
Read the project before touching it: routes, tokens, fonts, assets, constraints and the ambition the brief really asks for.
You getYour constraints, scoped and written down
Take 02
Three experientially distinct directions, one chosen with reasons, and a signature moment that can be verified.
You getA creative brief with one chosen direction
Take 03
A DESIGN.md with tokens, states, motion and acceptance criteria. The system is written down before it is built.
You getDESIGN.md in your project
Take 04
Vertical slices in your existing stack. For ambitious work the defining viewport is prototyped first, reviewed, and only then scaled.
You getA working implementation, not a mockup
Take 05
Real browsers at 375, 768, 1440 and 1920, when browser tooling is available. Every gate is reported as pass, fail or not run.
You getGate results with evidence
Creative concepts, typography, composition and an unmistakable point of view.
Production-minded components, semantic markup and intentional interactions.
Real browser inspection, device coverage and explicit quality gates. No imaginary scores.
Use $premium-frontend-director to redesign this frontend. Audit the current repository, select a creative ambition mode, propose three brand-appropriate directions, prototype the defining moment, implement one coherent system, review actual desktop and mobile rendering, and report objective quality gates.
The prompt is the one suggested in the skill. The log shows the order of the workflow, not the result of a real run.
Every run is reported against 11 named gates, each marked pass, fail or not run. Nothing is claimed without evidence.
Read the quality gatesPremium Frontend Director is an Agent Skill: instructions your coding agent reads. It is not a template, a component library or a hosted service. Core is the only required install.
Decides which specialist tools your agent may consult.
Premium and Studio are not installed with Core. Each companion uses its own installer, and a missing companion never stops Core from running. The agent reports each one as used, not available or not needed.
Decides how far the visual result should travel.
The profile chooses tools. The ambition chooses the transformation. Any pairing is valid: Core with Immersive, Premium with Expressive, Studio with Refined. Immersive does not require Premium, and none of the ambitions requires WebGL.
Your setupCore + ExpressiveInstall it Setup: Core profile, Expressive ambition.
Install the skill and give your next frontend project a point of view. Open source under MIT, designed for Claude Code, Codex and other Agent Skills-compatible agents.
Setup: Core + Expressive Change
Open a terminal in the root of your own frontend project, not in this site or the skill repository, and run:
npx skills add AVL05/premium-frontend-director --skill premium-frontend-director -a claude-code-g unless you want a global install.Any agent that recognises SKILL.md can use the skill. Run npx skills add AVL05/premium-frontend-director --skill premium-frontend-director without -a and pick your agent in the installer.
Claude Code can alternatively install it as a plugin, instead of the command above and never both. Run inside Claude Code: /plugin marketplace add AVL05/premium-frontend-director then /plugin install premium-frontend-director@premium-frontend-director-marketplace. Marketplace notes
List the project’s skills, open a new Claude Code session, then ask it:
npx skills listList the installed project skills. Confirm whether premium-frontend-director is registered and invocable in this session. Do not change any files.
A folder on disk is not proof. The skill is installed when the agent itself says it is registered and invocable. If it is not, restart the agent and check that the installer targeted Claude Code at project scope. Troubleshooting
Name the skill in your prompt. This one is written for Core + Expressive:
Use $premium-frontend-director with the Core profile and Expressive ambition. Audit this project's existing UI and goals. Propose three different art directions, implement the best-fitting one in the current framework, document design.md, inspect mobile and desktop rendering when possible, and report actual PASS / FAIL / NOT RUN quality gates. Preserve existing behavior. Do not install anything else without permission.
The skill does not guarantee a particular result. Real-browser checks need browser tooling in your agent or project; without it those gates are reported as NOT RUN. The quality gates
Optional, and possible at any time: the same project, nothing reinstalled. Install each one in your project with its own installer. There is no single command for all of them.
UI UX Pro Max. Research: searchable style, palette and typography data to inform the direction. Has its own CLI. Python 3 is needed for its search scripts.
npx ui-ux-pro-max-cli init --ai claudeTaste Skill. Art direction: one primary aesthetic voice for the direction phase. Skills CLI. Check upstream for its current browser and Node requirements.
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend -a claude-codeImpeccable. Critique and polish: an independent review pass before sign-off. Has its own installer. Hooks are optional and need your approval.
npx impeccable installWeb Design Guidelines. UI code and UX heuristics review. It is not a Lighthouse run and not a judgement of the art. Skills CLI.
npx skills add vercel-labs/agent-skills --skill web-design-guidelines -a claude-codeThen open a new session and ask the agent to name the skills it can actually invoke: “Name the available skills and tell me which of them you can actually invoke in this session. Do not change any files.”
Design System Patterns. Design tokens and reusable component architecture for larger interfaces. Skills CLI.
npx skills add wshobson/agents --skill design-system-patterns -a claude-codeVercel React Best Practices. React and Next.js performance guidance. Skip it for any other stack. Skills CLI. Confirm the current skill name upstream first.
npx skills add vercel-labs/agent-skills --listResponsive Design. A specialist for when responsive layouts need one. Skills CLI.
npx skills add wshobson/agents --skill responsive-design -a claude-codeAccessibility Compliance. A dedicated accessibility specialist, when the project warrants one. Skills CLI.
npx skills add wshobson/agents --skill accessibility-compliance -a claude-codeTailwind Design System. A Tailwind-specific component system. Only for projects that use Tailwind. Skills CLI.
npx skills add wshobson/agents --skill tailwind-design-system -a claude-codeStudio builds on Premium and is not an install-everything bundle. Pick the entries that match your stack. Profiles and prerequisites