What is the frontend design direction skill?
Frontend design direction is a skill in the affaan-m/ECC repo. Before an AI coding agent writes UI, it fixes the purpose, audience, tone and one memorable detail, records an evidence contract with viewports and content states, then checks the rendered result with a bundled script.
Frontend design direction is a folder in the ECC repository with one SKILL.md. Its description says it sets an ECC-specific direction for production UI work such as dashboards, landing pages, components and visual tools.
The skill is for the moment when UI works but feels flat, generic or mismatched to the audience. It asks for a deliberate choice of direction before any code, then a rendered check afterwards.
What changes in your agent's output
- The agent states purpose, audience, tone and one memorable detail before touching a file.
- Dense, quiet tools stay dense and scannable instead of being forced into a marketing hero layout.
- Loading, empty, error, partial, success and permission states each get a trigger, feedback and next action.
- Existing project tokens, components and icon libraries are reused before a new visual system appears.
- Common generated patterns such as purple gradients, decorative blobs and cards inside cards are avoided.
Who it is for
Best for
- Interfaces that work but read as templated or off-brand for the product domain.
- Dashboards and tools that people use repeatedly, where scanning speed matters more than spectacle.
- Teams that want a written contract and screenshots as proof before a UI change is called done.
Not for
- Quick throwaway prototypes, because the evidence record and rendered checks add real work.
- Replacing Anthropic's own frontend design skill. ECC says it does not rebundle that one.
- Producing WordPress pages. It edits front-end code in your project.
Use it with UiChemy
This skill shapes the build in your repository. If the finished interface has to live on WordPress, UiChemy Composer writes editable HTML, CSS and JS inside the page builder. Click Get Started on uichemy.com.
How to install Frontend Design Direction Skill: Choose a UI Direction First
npx [email protected] setupSetup can be rerun later to update ECC or change scope. A manual route is also described in the README: clone the repository and copy the skill folder you want.Check the prerequisites
The README asks for Node.js 18 or newer. The Claude Code plugin route also needs Git and Claude Code 2.1 or newer on your PATH.
Run the guided setup
Run
npx [email protected] setupand follow the prompts. It installs the ECC plugin, which carries the whole skill library, not this skill on its own.Choose one install method
The README warns against stacking install methods in the same harness, because that can duplicate skills, commands and hooks. Pick the plugin route or a manual route, not both.
Other agents
For Codex or Kimi Code run
npx [email protected] install --guided. It lets you pick the harnesses and shows each destination before writing.Use the skill
Ask your agent to apply the frontend design direction skill to a page or component, and to write the evidence record at the end.
Check that it loaded
Ask the agent which skills it has loaded, or open your agent's skill list, and look for frontend-design-direction.
Key features
- Five-part directionPurpose, audience, tone, a memorable detail and constraints are chosen before coding. Constraints include framework, accessibility, performance, responsiveness and the existing design system.
- Domain matchingA SaaS operations tool should usually be dense, quiet and scannable, while a portfolio, game or launch page can be more expressive. The skill warns against forcing a landing page onto a daily-use tool.
- Evidence contractThe agent records the product surface, the user's job, the primary action, the hierarchy, target viewports and the reference observation behind each important choice.
- Six content statesLoading, empty, error, partial, success and permission states each need a trigger, visible feedback and a safe next action, or a recorded reason they do not apply.
- Build from the contractThe first screen is the usable experience, not marketing copy, unless asked. CSS variables or existing tokens keep the direction consistent across states.
- Anti-pattern listPurple gradients, decorative blobs, oversized cards, vague hero copy and nested cards are named as defaults to avoid, along with new dependencies added only for a flourish.
- Review checklistNine checks cover first-viewport clarity, hierarchy, text fit, contrast, icons, stable dimensions, real assets, purposeful motion and fit with repo conventions.
- Rendered finish gateKeyboard navigation, visible focus, labels, contrast, reduced motion and touch targets are checked in the rendered interface. Source inspection alone cannot pass.
- Evidence checkerA bundled Node script validates a local JSON record with viewports, passing accessibility and responsive entries, and one artifact per target viewport.
- Optional researchAn authenticated UIZZE MCP is described as optional. Nothing is sent without consent, and the local workflow works without an account.
Frequently asked questions
What is the frontend design direction skill?
It is a SKILL.md in the affaan-m/ECC repository. It tells an AI coding agent to choose a purpose, audience, tone and memorable detail before building UI, then reuse existing tokens, handle six content states and verify the rendered result at the target viewports.
How do I install frontend design direction?
The skill ships inside ECC, so you install ECC. The README's recommended route is npx [email protected] setup, which needs Node.js 18 or newer. Do not stack a plugin install and a manual install in the same agent, because the README says that can duplicate skills.
Does it work with Claude Code, Cursor and Codex?
The ECC README says it works best with Claude Code today, has native Codex and Qoder plugin paths, and offers capability-limited adapters for Cursor, OpenCode, Gemini, Zed and others. It also points to a support matrix, so check parity before assuming every feature carries over.
What is the evidence checker?
It is a Node script, check-evidence.js, shipped with the skill. You give it a local JSON record with the contract, target viewports, accessibility and responsive results, content states and rendered artifacts. It rejects incomplete, failed or untested records, but it cannot judge whether screenshots are truthful.
Is frontend design direction the same as Anthropic's frontend-design skill?
No. The skill says ECC intentionally does not rebundle the canonical Anthropic frontend-design skill and points you to anthropics/skills for it. This one is an ECC-specific direction layer with a state contract and rendered gate. See the frontend design skill page for the Anthropic version.
Does it send my screenshots or code anywhere?
The local quality gate works without an account or external service. The optional UIZZE research workflow needs your consent, sends only sanitized aggregate needs, and keeps screenshots, source code, private URLs and credentials local. If safe aggregation is unavailable, the agent continues locally.
What are alternatives to frontend design direction?
For anti-generic UI rules, see Design Taste Frontend or UI Craft. For polishing details after a direction is set, Polish covers the final pass. They differ in how much process and evidence they require.
Does it produce a WordPress page?
No. It edits the front-end code in your project. To get a finished design into WordPress, UiChemy has Composer for editable HTML, CSS and JS in the page builder, and Figma to WordPress for designs. Click Get Started on uichemy.com to begin.


