Learn to run AI agents
on real design work.
Weekly guides, prompts, and templates for designers.
Build, audit, and ship with AI.
Join 1083+ people from these companies.
From files to system. In three steps.
01
Collect your context.
Everything that defines your design work: Figma files, tokens, screenshots, docs, and the rules living in your head.
02
Systemise it.
The guides turn it into a layer your AI can read: CLAUDE.md rules, semantic tokens, patterns, voice, and templates.
03
Let agents ship.
Audits, components, docs, and reviews. One canonical system, called from any tool.
A library built for doing
Open a workflow.
See what you
can build.
The guide to understand it. The prompt to start it. The template to make it yours.
Explore a few ways to put the library to work.
Explore the full libraryA workspace your AI understands.
Give your tools the context they need before the first prompt.
- Time 45 min
- You need An AI assistant you can point at a folder.
- Set up your AI workspaceChoose your tools and run your first sanity check.
- Generate your tools.mdTurn your tool choices into a reusable context file.
- CLAUDE.md for design systemsGive your agent token conventions and component rules.
A tools.md and a CLAUDE.md your agent loads before it writes anything.
Find the gaps. Know what to fix.
Bring a repeatable structure to your next design system review.
- Time 50 min
- You need Your tokens in JSON and access to the component library.
- Audit a design system in 30 minutesWork through tokens, components, and accessibility.
- Design token audit promptFind naming issues and missing semantic layers.
- Design token audit checklistKeep naming, structure, and documentation in view.
A prioritised token audit with suggested fixes, ordered by what breaks first.
Take the design into working code.
Connect your design context, review the output, and document it.
- Time 1 hour
- You need Figma edit access and a repo you can branch.
- From Figma to code with MCPBring design context into your coding workflow.
- Design-to-code review checklistCheck tokens, responsiveness, and accessibility.
- Component documentation generatorExplain props, usage, and accessibility from your code.
One component in code with bound tokens, every state, and docs attached.
Real resources. Open a file to take a look.
Built around your practice
Your tools.
The same design know-how.
Clear context, better prompts, and design judgment. Learn the principles here, then put them to work in the AI tools you already use.
Learn AI. All in one place.
Search in plain English
Describe what you need and the library surfaces it: guides, tools, prompts.
Your tools.md, generated
Answer a few questions, download the file your coding agent reads first.
MCP configs included
Connect Figma, tokens, and your repo to Claude, Cursor, or Codex.
Compare before you commit
Side-by-side tool comparisons with honest verdicts from daily use.
What you end the first week with
Three files that did not exist on Monday.
tools.md
A context file your agent reads first
Your stack, your conventions, your constraints, in the file Claude Code or Codex loads before the first prompt.
Generate it freeCLAUDE.md
Token and component rules an agent can follow
Naming convention, semantic layers, and the component rules that stop an agent inventing its own.
Open the templateaudit-findings.md
A prioritised token audit with suggested fixes
Every duplicate, every raw hex, every casing clash, ordered by what breaks first, with a rename map to review.
Read the guide
Membership keeps them current: 92 guides, 33 prompts, and 26 templates, added to every week, plus the member Discord.See what each plan includes
Weekly newsletter
Get the weekly DSG newsletter.
One practical guide each week: prompts, Codex and Claude notes, design-system automation, and tools worth trying.
Popular resources
Tools and kits that pair well with the guides.