start
Front door. Reads the current project (framework, tokens, brief, spec, harness) and reports what ui-craft can do right now, then routes you to the right next step. Run this first if you're new or unsure where to begin. No code changes. Invoke when the user asks for start on their UI, or mentions 'start' alongside design / UI / frontend work.
- Installs
- 724
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/educlopez/ui-craft --skill start- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads start automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.
Orient the user. Load the ui-craft skill, read the current project, and report what ui-craft can do right now for it. This is the front door — most people run it first.
ORCHESTRATE-ONLY RULE
This command detects state and routes. It MUST NOT build, edit, audit, or re-implement any phase logic. It contributes only:
- Project detection (read-only).
- A "what's available now" map across the three usage layers.
- One recommended next step + the command to run for it.
When the user wants to act, hand off to the real command (/brief, /tokens, /sddesign, /craft, /finalize, the review agents, etc.). Do not inline their steps.
Step 1 — Detect (read-only)
Scan the project. Do not write anything. Gather:
| Signal | How to detect | Used for |
|---|---|---|
| Framework / styling | package.json deps, config files, file extensions — Tailwind, CSS Modules, styled-components/Emotion, vanilla CSS, Vue/Svelte/Astro SFC | Confirm ui-craft adapts to this stack |
| Token spine | CSS vars (--color-*, --accent-*, --font-*), Tailwind theme.extend, a token file | Gate: is /tokens needed? |
| Brief | .ui-craft/brief.md exists? | Gate: is /brief needed? |
| External design contract | DESIGN.md or design-tokens.json at repo root (ecosystem convention some teams use) | Treat as brief + token input — read it, honor it, don't duplicate it |
| Spec | .ui-craft/spec.md exists? which surfaces? | Is there work in flight? |
| Harness | Claude Code (plugin/skill) vs .codex/.cursor/.gemini/.opencode/.agents mirror | Which layers are reachable (agents/MCP are Claude Code / MCP-client only) |
| Existing UI | are there components/pages already, or is this greenfield? | Build-new vs review/polish framing |
Keep detection fast and quiet — a few reads, no deep traversal. Report findings as a short table.
Step 2 — Report the three layers
Print what's available now, mapped to how people actually use ui-craft. Mark each layer ● active / ○ available / – not reachable in this harness.
ui-craft is a design engineering SYSTEM. You're set up for:
● Layer 1 — Just ask
Describe any UI and the agent designs with taste (anti-slop, system tokens,
real hierarchy). No command needed. This is the default and the point.
○ Layer 2 — Drive it
Slash commands for focused passes. Given THIS project:
<tailored list — see Step 3>
○ Layer 3 — Verify it
design-reviewer + a11y-auditor agents · ui-craft-mcp gates · UICraftScore · ui-craft-detect CLI.
<mark – if the harness can't reach agents/MCP, and say so>
Tailor the bullets to the detected state — don't print the generic catalog.
Step 3 — Recommend ONE next step
Pick the single highest-value next action from detected state. Use this decision order:
- No brief, non-trivial project → recommend
/brief("anchor every later decision to your product's principles — 5 min, writes.ui-craft/brief.md"). - Brief exists, no token spine → recommend
/tokens("establish the 3-layer token spine so builds match a system, not inline guesses"). - Brief + tokens exist, building something net-new → recommend
/sddesign <surface>(full pipeline) or/craft <surface>(one-shot) — ask which. - Existing UI to improve → route by intent: review →
ui-craft:design-reviewer+ui-craft:a11y-auditor(Claude Code) or/critique+/audit; polish →/polish; simplify →/distill; flat/generic →/bolder; loud/busy →/quieter; dated site to modernize →/redesign. - About to ship / merge → recommend
/finalize(10-pass gate) and, for CI,npx ui-craft-detector thescore_uiMCP tool.
Print it as one clear line:
Recommended next:
…— <one-sentence why>.
Then offer the full menu only if asked: "Want the full command list, or shall I run that now?"
Step 4 — Hand off
If the user confirms, run the recommended command. Otherwise stop — /start never acts on its own. Its job is done once the user knows where they are and where to go.
Notes
- Read-only.
/startwrites nothing and changes no code. The artifacts (brief.md,spec.md, tokens) are written by their own commands. - Harness honesty. If the project is in a non-Claude-Code harness (
.codex,.cursor, etc.), Layer 3 agents and the MCP server may not be reachable from that agent — say so plainly and point to the CLI (ui-craft-detect) as the portable verify path. - Craft-intent routing. Full-surface builds (
/craft,/sddesign) declare a Craft Read before code. If the user describes a built UI as "generic", "template-y", or "too safe", route to/bolder; if "too loud" or "too busy", route to/quieter. - Don't re-run Discovery. If a brief or spec already exists, don't interrogate the user for preferences — read the artifacts and report.
Next step: Follow the rung this run named. /start is read-only — the value is in doing the one command it picked.
FAQ
What does the start skill do?
Front door. Reads the current project (framework, tokens, brief, spec, harness) and reports what ui-craft can do right now, then routes you to the right next step. Run this first if you're new or unsure where to begin. No code changes. Invoke when the user asks for start on their UI, or mentions 'start' alongside design / UI / frontend work.
How do I install start?
Run npx skills add https://github.com/educlopez/ui-craft --skill start in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/start/ (personal) or .claude/skills/start/ (project).
Which AI agents can use start?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is start safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains start?
It is published by educlopez in educlopez/ui-craft. It has 724 recorded installs.
More from educlopez/ui-craft
ui-craft
educlopez/ui-craft
Use for UI design and implementation work to avoid generic AI-looking interfaces. Provides anti-slop rules, a required discovery phase before coding, and guidance for layout, typography, color, motion, accessibility, dashboards, tables, landing pages, theming, and polish. Trigger when editing UI code or reviewing and refining components, pages, screens, layouts, animations, responsive behavior, or design systems.
ui-craft-dense-dashboard
educlopez/ui-craft
Dense dashboard / admin / Bloomberg / Retool / data-heavy internal tools. Locked knobs: CRAFT=7, MOTION=3, DENSITY=9. IBM Plex + mono numbers, semantic palette, 4/8px grid, sparklines, tabular-nums. Trigger on: dashboard, admin panel, data-dense, analytics, Bloomberg-like, Retool-like.
audit
educlopez/ui-craft
Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table. Invoke when the user asks for audit on their UI, or mentions 'audit' alongside design / UI / frontend work.
ui-craft-minimal
educlopez/ui-craft
Minimal / clean / Linear / Notion / Vercel / whitespace-heavy UIs. Locked knobs: CRAFT=8, MOTION=3, DENSITY=2. Monochrome + one accent, Inter/Geist, hairline borders over shadows. Trigger on: minimal, clean, Linear-like, Notion-like, Vercel-like, whitespace-heavy.
ui-craft-editorial
educlopez/ui-craft
Editorial / magazine / long-form / Medium / Substack / content-heavy UIs. Locked knobs: CRAFT=9, MOTION=4, DENSITY=3. Serif display + humanist body, wide reading column, drop caps, OpenType. Trigger on: editorial, magazine, long-form, blog, Medium-like, Substack-like.
colorize
educlopez/ui-craft
Color strategy pass — introduces a single accent at 3-5 intentional placements, or reduces an over-colored UI back to 90% neutral. Use when the UI has no color identity, uses blue by default, or is shouting with too many competing accents. Invoke when the user asks for colorize on their UI, or mentions 'colorize' alongside design / UI / frontend work.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.