start

A read-only starting command that examines a project and reports which parts of a UI design workflow are currently available.

In plain words
What is it for?
Use it to detect the project framework, styling approach, design tokens, brief, and available UI workflow commands.
Why use it?
It gives newcomers a clear orientation and recommended next action before they start changing the code.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/educlopez/ui-craft/start
Clone the repo
git clone --depth 1 https://github.com/educlopez/ui-craft
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,371 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.01371
Opus 5 $0.00027 $0.00685
Sonnet 5 $0.00011 $0.00274
Haiku 4.5 $0.00005 $0.00137

Measured 2d ago against content hash a5446d535290, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

start scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cli/assets/claude/commands/start.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

  1. Project detection (read-only).
  2. A "what's available now" map across the three usage layers.
  3. 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.

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 96 lines · 54 tokens per session scan A a5446d535290

Subscribe to this mod's changes

start is a command published in the GitHub repository educlopez/ui-craft (298 stars, last pushed 13d ago), licensed MIT. It adds 54 tokens to every session and 1,371 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.