diego3g/craft

using-craft

Use when starting any conversation, before responding to any request that involves designing, reviewing or changing a UI, a screen, a page, a flow, a component or a style guide.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/diego3g/craft --skill using-craft

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

<SUBAGENT-STOP> If you were dispatched as a subagent to do one specific task, ignore this skill and do the task. </SUBAGENT-STOP>

<EXTREMELY-IMPORTANT> If there is even a small chance that a design skill applies to what you are about to do, invoke it before you respond, including before clarifying questions, before reading files and before drawing anything.

A design skill that applies is not optional. Small edits are the only exception (see below). </EXTREMELY-IMPORTANT>

How

  1. Check the routing table below. The one thing to look at first is whether DESIGN.md exists at the project root; it decides between craft-setup and craft. Don't guess it.
  2. Invoke the skill with your Skill tool, and announce: "Using <skill> to <purpose>."
  3. Follow it exactly, including its stops for the person's approval. A stop means ending your turn with the question, which is always possible, even in a headless or one-shot session. Never decide a stop for the person.

Routing table

The situationSkill
Any request to design, create, mock up or redesign a page, screen, flow or elementcraft
A design task in a project with no `DESIGN.md` at its rootcraft-setup first (it offers to import a design system already in code), then craft
"Set up the design", "define our style / brand / guidelines"craft-setup
"Options", "alternatives", "other directions", "I don't like it", "rethink this"craft-explore
"Review", "refine", "polish", "make it better", "feels off", or you are about to show your own designcraft-critique
Tokens, the style guide, a new or changed component, "make consistent", "audit"craft-system
"Import / bring our design system, tokens or components into <tool>"; "apply / push / sync the guide's changes to the code"craft-sync
"What states are missing?", "is this ready for dev?"craft-states

A reusable piece for the system ("we need a date picker component") goes to craft-system; something on a specific page goes to craft. These are craft's skills (prefixed craft: in the Claude Code plugin); prefer them over same-named skills from elsewhere.

Priority

  1. craft-setup before craft when there is no DESIGN.md. Reviews, options for an existing screen, audits and state questions don't need a brief: they work from what's already there.
  2. craft before its sub-skills: it calls craft-states, craft-explore, craft-system, craft-sync and craft-critique at the right moment, so don't start them yourself in the middle of a craft run.
  3. craft-critique is the last step before you show anything you made.

Small edits: no process

A change the person described exactly (one value, one label, one element's size, one colour, a typo) is made directly. No skill, no states list, no options.

  • If the thing is shared (a button style used on many screens), change it once where it is defined, and say which screens it affects. Don't open a full design pass for it.
  • If you're unsure whether it's small, it isn't. Use the table.

Red flags

ThoughtReality
"It's just a quick mockup, I'll skip the process"A quick mockup is still a design. The states list takes a minute. Use craft.
"There's no DESIGN.md, but the request is clear enough"Without a brief, every screen invents its own style. craft-setup first; the person can say "skip".
"I'll draw it now and review it later"Showing unreviewed work trains the person to do your review. craft-critique runs before you show.
"I know which states it needs"You know the happy path. craft-states lists the rest.
"Let me read the files first, then decide on a skill"Skills tell you what to read. Decide first.
"This is a small change" (to a new page)A new page is never a small change.
"The session can't wait for answers, so I'll decide and list my calls"End your turn with the question. Deciding for them is the one thing the stops exist to prevent.

Other agents

Where this skill isn't loaded automatically, put the routing table above in your AGENTS.md (or the equivalent) so the agent sees it at the start of every session.

同じリポジトリから

関連する Skills

すべての Skills
diego3g
コミュニティ

craft

Use when asked to design, create, mock up or redesign one or more pages, screens, flows or UI elements, or when the person runs /craft (/craft:craft in the Claude Code plugin).

1時間の導入数
2
GitHub Stars
366
更新日
11月17日
diego3g
コミュニティ

craft-critique

Use when asked to review, critique, refine or polish a design or screen, when something "feels off", "looks busy" or "isn't good yet", after finishing a screen and before showing it, or before handing a design to code.

1時間の導入数
2
GitHub Stars
309
更新日
11月17日
diego3g
コミュニティ

craft-explore

Use when asked for options, alternatives, variations, directions or "a few ideas" for a screen, flow or element, when the person rejects a design or says they don't like it, or says "rethink this", "try something else" or "design both so I can pick".

1時間の導入数
2
GitHub Stars
309
更新日
11月17日
diego3g
コミュニティ

craft-setup

Use when a request to design or create a page, screen or element starts in a project with no DESIGN.md at its root, when the person asks to set up, define or start the design, style, brand or guidelines of a product, or runs /craft-setup (/craft:craft-setup in the Claude Code plugin).

1時間の導入数
2
GitHub Stars
309
更新日
11月17日