A collection of production-grade design and development skills for AI coding agents. Each skill encodes opinionated best practices for creating professional, accessible, and performant user interfaces.
Design Craft provides standardized skill files that can be loaded into AI agent systems to guide UI/UX code generation. These skills act as "expert knowledge" that helps agents produce polished, production-ready interfaces rather than generic AI-generated output.
| Skill | Target Agent | Primary Stack | Description |
|---|---|---|---|
| v0 | v0 by Vercel | Next.js, Tailwind, shadcn/ui | Vercel's AI assistant defaults |
| claude | Claude (Anthropic) | Framework-agnostic | Anthropic's Claude coding assistant |
| gemini | Gemini (Google) | React, Tailwind | Google's Gemini AI assistant |
| lovable | Lovable | Vite, TanStack, shadcn/ui | Lovable's AI development platform |
Skills can be loaded as context/system prompts. Each skill is a self-contained markdown file with YAML frontmatter for metadata.
# Clone the repository
git clone https://github.com/headline-design/design-craft.git
# Or fetch individual skills directly
curl -O https://raw.githubusercontent.com/headline-design/design-craft/main/v0/SKILL.mdEach skill follows a standardized format:
---
name: skill-name
description: When to trigger this skill (used by agent harnesses for routing)
version: 1.0.0
---
# Skill Content (Markdown)Direct File Loading:
# Python example
with open('v0/SKILL.md', 'r') as f:
skill_content = f.read()
system_prompt = f"Use these design guidelines:\n\n{skill_content}"As MCP Memory:
Skills can be stored in agent memory systems (like v0's v0_memories/ directory) for persistent access.
As System Prompt Extension:
// JavaScript example
import { readFileSync } from 'fs';
const skill = readFileSync('claude/SKILL.md', 'utf-8');
const messages = [
{ role: 'system', content: skill },
{ role: 'user', content: userMessage }
];All skills follow a consistent structure for predictability:
1. Design Philosophy - Core principles and aesthetic direction
2. Color System - Token structure, 3-5 color rule, gradients
3. Typography - Font pairing, scale, line heights
4. Layout & Spacing - Grid systems, spacing scale, responsive
5. Component Architecture - File structure, composition patterns
6. Tailwind CSS Patterns - Class ordering, utility patterns
7. Accessibility - Semantic HTML, focus, ARIA, contrast
8. Performance - Image optimization, code splitting, data fetching
9. Code Organization - Project structure, naming conventions
10. UI/UX Principles - Hierarchy, states, feedback, empty states
11. Common Patterns - Hero, feature grid, bento, forms, navigation
12. Anti-Patterns - What to avoid (the "AI tells")
13. Quick Reference - Pre-ship checklist
These principles are shared across all skills:
Every design uses exactly 3-5 colors: 1 primary brand color, 2-3 neutrals, and 1-2 accents. This constraint forces cohesion.
Limit to 2 font families maximum. More creates visual chaos. Display font for headings, readable sans-serif for body.
Always design for 375px width first, then scale up using responsive breakpoints.
Never use direct colors (bg-white, text-black). Everything flows through semantic design tokens (bg-background, text-foreground).
Split code into logical components. No monolithic 500+ line files. Composition over configuration.
Every interactive element needs: default, hover, focus, active, disabled. Async elements add: loading, error, success.
Semantic HTML, keyboard navigation, visible focus states, and sufficient contrast are baseline correctness, not polish.
These patterns immediately signal "AI-generated" and should be avoided:
- Purple/pink gradient on every CTA
bg-white,text-blackinstead of semantic tokens- More than 2 font families
- Missing focus states
<div onClick>instead of<button>- Lorem ipsum or placeholder images in shipped code
- Desktop-first responsive design
- Fetching data in useEffect
- Abstract decorative gradient blobs
- Generic copy ("Get Started", "Learn More")
- Color-only error indication (must include icon)
- Create a new directory with the agent name:
agent-name/ - Add a
SKILL.mdfile following the standard structure - Include YAML frontmatter with
nameanddescription - Follow the 13-section structure outlined above
- Add the skill to the table in this README
- YAML frontmatter with
name,description - Table of contents with anchor links
- Code examples for all patterns
- Both
// ✅and// ❌examples showing good vs bad - Agent-specific stack considerations noted
- Pre-ship checklist at the end
- Summary section with core philosophy
- All code examples are syntactically correct
- No placeholder text in examples
- Consistent formatting throughout
- Links in table of contents work
- Specific, actionable guidance (not generic advice)
import openai
from pathlib import Path
skill = Path('v0/SKILL.md').read_text()
response = openai.chat.completions.create(
model="gpt-4",
messages=[
{"role": "system", "content": f"You are a UI developer. Follow these guidelines:\n\n{skill}"},
{"role": "user", "content": "Build a landing page for a SaaS product"}
]
)import anthropic
from pathlib import Path
skill = Path('claude/SKILL.md').read_text()
client = anthropic.Anthropic()
message = client.messages.create(
model="claude-sonnet-4-20250514",
max_tokens=4096,
system=f"Use these design guidelines:\n\n{skill}",
messages=[
{"role": "user", "content": "Create a dashboard component"}
]
)from langchain.prompts import ChatPromptTemplate
from langchain_openai import ChatOpenAI
from pathlib import Path
skill = Path('gemini/SKILL.md').read_text()
prompt = ChatPromptTemplate.from_messages([
("system", "You are a UI developer following these guidelines:\n\n{skill}"),
("human", "{input}")
])
chain = prompt | ChatOpenAI(model="gpt-4")
response = chain.invoke({"skill": skill, "input": "Build a feature grid"})# Copy skill to v0 memory directory
cp v0/SKILL.md v0_memories/user/skills/design.mdSkills follow semantic versioning:
- Major: Breaking changes to structure or fundamental principles
- Minor: New sections, expanded guidance, additional patterns
- Patch: Typo fixes, clarifications, small improvements
MIT License - See LICENSE for details.
Created and maintained by HEADLINE Design.
- Pick the skill matching your target agent
- Load the skill content as system context
- Start generating production-quality UI code
For questions or issues, open an issue.