Weekly updated guides, prompts, and tools for designers to build, audit, and scale products.
How it works
Each path connects your existing design system to AI tools you already have access to.
Connect Claude to your Figma file, run a token audit, and get a prioritized fix list.
audit-tokens prompt Generate specs, props, states, accessibility notes, and usage guidelines from existing code.
Props & variants documented
Accessibility notes added
Usage guidelines written
Edge cases & do/don't examples
AI generates these from your Storybook stories and existing usage patterns.
Compare 40 tools side-by-side. Find the component library, token tool, and testing setup that fits.
Style Dictionary
Tokens Studio
Radix + Tailwind
shadcn/ui
Practical guides, prompts, tool reviews, comparisons, and design-system resources. Built from real projects, not theory.
Token pipelines, Figma MCP, Claude Code, component audits. Written from real projects, not demos.
Copy, paste, ship. Audits, docs, reviews, design critique. Tested across Claude, ChatGPT, and Gemini.
Every AI design tool, tried hands-on. Skip the ones that look great in demos and fail at work.
Real features, real pricing, real trade-offs. No affiliate links, no hedging.
What Netflix, Meta, Porsche, and Volvo actually ship. Searchable, with tokens, components, and docs.
Quick answers on MCP, CLIs, prompting, tokens, and team structure. Curated links and next steps.
What's inside
Everything I use daily as a senior product designer and consultant. Organized by task, not by buzzword.
Create a tools.md file that gives Claude, Codex, Cursor, and coding agents your tools and dependencies.
Try it free →Token audits, MCP setup, Figma-to-code, component docs, Claude Skills, Playwright, and more.
Copy-paste prompts for token audits, component docs, accessibility reviews, and design critique.
Side-by-side breakdowns with real features, real pricing, and honest verdicts for every major tool.
Screenshots, tech stacks, GitHub repos, Figma kits, and Storybook links for major design systems.
Quick answers to common questions about tokens, MCP, CLI tools, and AI for designers.
How it works
Move from lesson to action without guessing what to do next. Each path helps you make one visible improvement, then save what worked for the next project.
[01]
Start with a sequence that tells you what to learn next, from setup to real design-system work.
[02]
Use each guide to compare the before and after: cleaner docs, stronger prompts, better review output.
[03]
Grab the exact instruction, run it in your AI tool, then adjust only the project-specific details.
[04]
Save what worked as a rule, skill, checklist, or team playbook so the next pass gets easier.
Weekly newsletter
One practical guide each week: prompts, Codex and Claude notes, design-system automation, and tools worth trying.