Agent skill

Start

by educlopez in educlopez/ui-craft

Front door. An agent skill from educlopez/ui-craft.

MITAuto-check passedFrontend & Design

Install Start

skills CLI
$ npx skills add educlopez/ui-craft --skill start -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install educlopez/ui-craft start --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/educlopez/ui-craft.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/start .claude/skills/start && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
start
GitHub stars
371
Token cost
~1.5k tokens
SKILL.md length
653 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Front door. An agent skill from educlopez/ui-craft.

  • Works in 4 steps: Detect (read-only) → Report the three layers → Recommend ONE next step → …
  • Asks for start on their UI
  • SKILL.md covers ORCHESTRATE-ONLY RULE, Step 1 — Detect (read-only), Step 2 — Report the three layers and Step 3 — Recommend ONE next step, plus 2 more sections
  • Calls npx

What it does

Start is an agent skill from educlopez/ui-craft. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design. The repository describes itself as: Design engineering system for AI coding agents — ship UI with craft-level quality. Install as an agent skill. The licence is MIT.

When your agent uses it

  • Asks for start on their UI
  • Mentions start alongside design / UI / frontend work

Example prompts

  • “/start”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Detect (read-only)
  2. Report the three layers
  3. Recommend ONE next step
  4. Hand off

What it can do on your machine

Read from SKILL.md and the folder at commit ceecc8e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Start loads about 1.5k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 653 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from educlopez/ui-craft at commit ceecc8e, republished under its MIT licence (© educlopez). 653 words, ~1,451 tokens.

Download SKILL.mdSave it as .claude/skills/start/SKILL.md (or your agent's skills folder).
name
start
description
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.
<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

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:

  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:

SignalHow to detectUsed for
Framework / stylingpackage.json deps, config files, file extensions — Tailwind, CSS Modules, styled-components/Emotion, vanilla CSS, Vue/Svelte/Astro SFCConfirm ui-craft adapts to this stack
Token spineCSS vars (--color-*, --accent-*, --font-*), Tailwind theme.extend, a token fileGate: is /tokens needed?
Brief.ui-craft/brief.md exists?Gate: is /brief needed?
External design contractDESIGN.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?
HarnessClaude Code (plugin/skill) vs .codex/.cursor/.gemini/.opencode/.agents mirrorWhich layers are reachable (agents/MCP are Claude Code / MCP-client only)
Existing UIare 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.


Show full SKILL.md (329 more words)Show less

Step 3 — Recommend ONE next step

Pick the single highest-value next action from detected state. Use this decision order:

  1. No brief, non-trivial project → recommend /brief ("anchor every later decision to your product's principles — 5 min, writes .ui-craft/brief.md").
  2. Brief exists, no token spine → recommend /tokens ("establish the 3-layer token spine so builds match a system, not inline guesses").
  3. Brief + tokens exist, building something net-new → recommend /sddesign <surface> (full pipeline) or /craft <surface> (one-shot) — ask which.
  4. 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.
  5. About to ship / merge → recommend /finalize (10-pass gate) and, for CI, npx ui-craft-detect or the score_ui MCP 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. /start writes 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.

© educlopez, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/start of educlopez/ui-craft.

Open the folder on GitHubat commit ceecc8e

Compare with similar skills

Start next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Start compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Start this skilleduclopez/ui-craft371—~1.5kAutomated safety check: PassMIT
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0
React Doctormakeplane/plane61k12 repos~657Automated safety check: PassAGPL-3.0
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone

Similar skills

  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    61k GitHub starsUsed in 12 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 tokens
    Frontend & DesignAuto-check passed

More from educlopez/ui-craft

All 13 skills in this repo
  • Finalize

    educlopez/ui-craft

    Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy.

    371 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Friction Log

    educlopez/ui-craft

    File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent.

    371 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed
  • Remember

    educlopez/ui-craft

    Record a learned design constraint from a correction into the project brief.

    371 GitHub stars~585 tokensUpdated 1 mo ago
    Auto-check passed
  • Sddesign

    educlopez/ui-craft

    Full spec-driven pipeline — walks brief → tokens → shape (spec) → craft (build) → converge → ship in one guided run.

    371 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Tokens

    educlopez/ui-craft

    Audit or establish the project's 3-layer token spine. An agent skill from educlopez/ui-craft.

    371 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Shape

    educlopez/ui-craft

    Wireframe-first pass — outputs an ASCII layout + state list + content inventory + question list before any code.

    371 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Start

What does Start do?

Front door. An agent skill from educlopez/ui-craft. Start is an agent skill from educlopez/ui-craft. Front door.

When should I use Start?

Start fits situations like: asks for start on their UI; mentions start alongside design / UI / frontend work.

How do I install Start in Claude Code?

Run `npx skills add educlopez/ui-craft --skill start -a claude-code`. Or copy the skill folder (.codex/skills/start in educlopez/ui-craft) into .claude/skills/start in your project. Claude Code loads it when a task matches its description.

How do I install Start in Codex?

Run `npx skills add educlopez/ui-craft --skill start -a codex`. Or copy the skill folder (.codex/skills/start in educlopez/ui-craft) into .agents/skills/start in your project. Codex loads it when a task matches its description.

Can I use Start in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add educlopez/ui-craft --skill start -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/start, .gemini/skills/start, .github/skills/start and .opencode/skills/start in your project.

What does Start need to run?

Going by SKILL.md and its folder, Start needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Start access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Start safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Start use?

Start is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Start use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Start?

Skills that share tags, products or a category with Start: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Start?

educlopez (a GitHub user) maintains it in educlopez/ui-craft, which has 371 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 3, 2026.

Source: educlopez/ui-craft on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.