educlopez/ui-craft

start

Front door.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/educlopez/ui-craft --skill start

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

<!-- 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.


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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
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.

1시간 설치 수
2
GitHub Stars
450
업데이트
11월 6일
educlopez
커뮤니티

ui-craft-dense-dashboard

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.

1시간 설치 수
2
GitHub Stars
450
업데이트
11월 6일
educlopez
커뮤니티

adapt

Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says \"make it responsive\" / \"fix mobile layout\". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work.

1시간 설치 수
1
GitHub Stars
394
업데이트
10월 19일
educlopez
커뮤니티

animate

Motion design pass — adds purposeful animations or removes excessive ones, respecting MOTIONINTENSITY and the project's animation stack. Use when the user asks to add animation, \"make it feel smoother\", fix janky transitions, or trim motion that's distracting. Invoke when the user asks for animate on their UI, or mentions 'animate' alongside design / UI / frontend work.

1시간 설치 수
1
GitHub Stars
394
업데이트
10월 19일