noam1a1

UI UX Compass — Design skill for Claude Code

Design community

Claude skill for end-to-end UI/UX: interviews first, picks from 95 design styles, maps every screen state, and plans before it codes.

How to install UI UX Compass

This entry records only its repository, not the path inside it, so there is no exact command to give. Open noam1a1/ui-ux-compass and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What UI UX Compass does

Claude skill for end-to-end UI/UX: interviews first, picks from 95 design styles, maps every screen state, and plans before it codes.

Alternatives in Design

  • Mckinsey Deck — Build a McKinsey-style PPTX deck from a brief 566 ★
  • Design Handoff — Generate a developer handoff document from a Figma file — spacing specs, token maps, component APIs, and produ 309 ★
  • Link Building — Link Building - run one of six give-first outreach playbooks (Invoice, Source Sniping, Tombstone, Fact Decay 195 ★

README

UI/UX Compass: understand before designing, plan before building

UI/UX Compass

**An agent skill that makes Claude understand before it designs, and plan before it builds.**

Most AI-generated interfaces look fine in the happy path and fall apart everywhere else: the empty list, the slow network, the first-time user, the error screen, the phone in RTL. UI/UX Compass changes the order of work. It interviews you only as much as needed, picks a design direction from a catalog of about 95 visual styles, maps every screen and every state, and hands you a Markdown plan. **No code is written until you approve it.**

How it works

 Orient ──> Discover ──> Direction ──> Architecture ──> Plan (.md) ──> ✋ Approval ──> Build + Verify
Phase What happens
0. Orient Detects whether this is a new project, a broad improvement or a scoped change. For existing projects it audits the code first: stack, tokens, components, state handling, accessibility, RTL.
1. Discover An adaptive interview. It asks only what it can't learn from the code or your brief, in 1–3 short rounds. Non-critical gaps become explicit assumptions you can correct. It confirms the plan's language and whether you want visual previews.
2. Direction Proposes 2–3 contrasting style directions (e.g. Tech Minimalism + Bento Grid + Micro-interactions) with reasons, risks and a recommendation. Optional side-by-side visual previews. Recommends a stack for new projects.
3. Architecture Design tokens, screen inventory, Mermaid user flows, and a per-screen states table (loading, empty, error, partial, offline…), plus real UX copy, accessibility, RTL/i18n and a performance budget.
4. Plan A structured docs/ui-ux-plan.md in your language, with assumptions and open questions called out.
5. Approval gate You approve, request changes, or approve only some milestones.