by diego3g
Design skills for AI agents: /craft-setup writes your design brief, /craft designs screens with every state from your design system and reviews them. Works with Paper, Figma or HTML.
# Add to your Claude Code skills
git clone https://github.com/diego3g/craftGuides for using ai agents skills like craft.
See how craft compares with popular alternatives.
craft is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by diego3g. Design skills for AI agents: /craft-setup writes your design brief, /craft designs screens with every state from your design system and reviews them. Works with Paper, Figma or HTML. It has 76 GitHub stars.
craft's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/diego3g/craft" and add it to your Claude Code skills directory (see the Installation section above).
craft is primarily written in JavaScript. It is open-source under diego3g on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh craft against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
Ask your agent for "a pricing page" and, with craft installed, it works like a careful designer:
It stops for your "yes" where it matters and writes its decisions down for next time.
Install craft as a plugin. Inside a Claude Code session:
/plugin marketplace add diego3g/craft
/plugin install craft@craft
/craft:craft, /craft:craft-setup and so on.claude plugin update craft@craft.In Claude Desktop or claude.ai, go to Customize › Plugins › Add › Add marketplace, then enter diego3g/craft.
Install the skills with the skills CLI:
npx skills add diego3g/craft
It asks which agents to install into. You can also name the agent yourself:
| Agent | Command |
|---|---|
| Codex | npx skills add diego3g/craft -a codex |
| OpenCode | npx skills add diego3g/craft -a opencode |
| Cursor | npx skills add diego3g/craft -a cursor |
| Gemini CLI | npx skills add diego3g/craft -a gemini-cli |
| GitHub Copilot | npx skills add diego3g/craft -a github-copilot |
| Windsurf | npx skills add diego3g/craft -a windsurf |
-g to install for every project instead of only the current one.npx skills update to update later.These agents don't run the session-start hook. Paste the routing below into your AGENTS.md so the agent still picks the right skill.
## Design skills
Before responding to anything that designs, reviews or changes a UI, check this table and use the skill.
First look whether DESIGN.md exists at the project root.
- No DESIGN.md and a design task → craft-setup, then craft
- Design / create / redesign a page, screen, flow or element → craft
- "Options", "alternatives", "I don't like it" → craft-explore
- "Review", "refine", "make it better", or before showing your own design → craft-critique
- Tokens, style guide, a component, "audit" → craft-system
- "Bring our design system into <tool>", "apply the guide changes to the code" → craft-sync
- "What states are missing?" → craft-states
Small edits the person described exactly (one value, label or size): just make them.
A stop means ending your turn with the question. Never decide a stop for the person.
By hand: copy the folders in skills/ into your project's .agents/skills/, then add the routing above.
| Skill | What it does |
|---|---|
craft-setup |
Interviews you one question at a time: product, audience and voice, mood, brand, references, constraints. It then writes DESIGN.md and builds the foundations (tokens and base components). |
craft |
The main command, for designing a page, screen, flow or element. It confirms the scope, then for each screen lists the states, draws with your system's pieces and checks the result. |
craft-states |
Lists every state a screen can be in (empty, loading, error, long content, permissions, offline…) using realistic messy data, then draws and names each one. |
craft-explore |
Draws three directions that really differ in structure, interaction or density, never just new colours. They sit next to the current design, with a recommendation first. |
craft-system |
Looks after the design system: role-named tokens, interaction rules defined once, a states matrix per component, and a component index. Before a change spreads, it lists the screens the change affects. |
craft-sync |
Brings a design system that already lives in code into your design tool. Later it sends the guide's changes back to the code as a reviewed diff. |
craft-critique |
Renders the design and looks at it, then checks hierarchy, spacing, contrast, text, consistency and motion. Findings are ranked by impact. In review mode it changes nothing. |
The hidden using-craft skill does the routing: it sends each request to the right skill.
Agents with slash commands run them by name: /craft, /craft-setup… (/craft:craft, /craft:craft-setup… with the Claude Code plugin). In any agent you can also just ask in plain words.
craft-setup once per project. It writes DESIGN.md, which every other skill reads first. If your repo already has a component library or token files, craft-setup offers craft-sync instead, so nothing gets invented twice.craft. Describe what you need ("a settings page with billing and team"). It stops to confirm the scope and the list of states, then draws.craft-explore draws three directions. Pick one, or mix two.craft-critique report. craft already runs this check on its own work before showing it.craft-system). After changing the guide in your design tool, say "apply the guide changes to the code" (craft-sync).Small edits ("make the button 2px taller") skip all of this: the agent makes the change, and says so when it touches a shared piece.
DESIGN.md has eight short sections: Product, Audience and voice, Mood, Brand, References, Constraints, a dated Decisions log and Open questions. It's how Monday's decisions survive into Thursday's session.npm test # validator and hook tests
npm run check # skill format, links, no tool names outside adapters
Every skill was written test-first: scenarios ran without the skill, then with it (see tests/scenarios/). Changes to a skill should come with a scenario that fails before the change and passes after it.
The session-start hook and the "one entry skill that routes to the rest" idea come from obra/superpowers (MIT). The banner uses Departure Mono (OFL).
MIT