I presented my custom AI design workflow to our design team two weeks ago.
I presented my custom AI design workflow to our design team two weeks ago. #ClaudeDesign launched ๐ฉ๐ฌ๐ค ๐๐๐ฎ๐จ ๐ก๐๐ฉ๐๐ง and had a lot of overlap with what I built. I sat on this post for a while. ๐งโโ๏ธ
Decided to share because building it taught me something about where custom workflows are still optimal (for now).
๐ข๐ญ๐ช๐ฆ๐ฏ๐ฆ ๐พ๐ญ๐ข๐ถ๐ฅ๐ฆ ๐ฟ๐ฆ๐ด๐ช๐จ๐ฏ ๐ธ๐ช๐ฏ๐ด
Seed of an idea โ something โgood enoughโ to move a conversation forward, fast. Built-in sketch tool (hey, thatโs the โdigital napkinโ concept), consistent format, easy to share and comment on. For early ideation, itโs genuinely convenient.
๐ข๐ญ๐ช๐ฆ๐ฏ๐ฆ ๐๐ถ๐ด๐ต๐ฐ๐ฎ ๐ด๐ฌ๐ช๐ญ๐ญ๐ด ๐ธ๐ช๐ฏ
๐๐ฉ๐ฆ๐ฏ ๐ช๐ต ๐ด๐ต๐ข๐ณ๐ต๐ด ๐ฃ๐ฆ๐ง๐ฐ๐ณ๐ฆ ๐จ๐ฆ๐ฏ๐ฆ๐ณ๐ข๐ต๐ช๐ฐ๐ฏ. My workflow begins with /๐ฃ๐ณ๐ช๐ฆ๐ง-๐ค๐ณ๐ฆ๐ข๐ต๐ช๐ฐ๐ฏ, a live or async brainstorm between me and AI that builds a comprehensive project context before anything gets made. In async mode, AI generates a questionnaire based on the problem area, the team discusses and answers it in a working session, then we bring the answers back to Claude Code and AI picks up from there. That context carries forward into every skill downstream.
๐พ๐ฐ๐ฎ๐ฑ๐ฐ๐ฏ๐ฆ๐ฏ๐ต ๐ง๐ช๐ฅ๐ฆ๐ญ๐ช๐ต๐บ. Claude Design rebuilds components as HTML files rather than pulling from the actual codebase I uploaded, which sometimes isn't 1-to-1 with the actual design system โ missing states, missing components, approximate spacing. Custom skills can go deeper, connecting to your real design system components and anti-patterns, so what comes out actually matches your product styles and adheres to your design system better.
๐๐ฉ๐ฆ ๐ด๐บ๐ด๐ต๐ฆ๐ฎ ๐ญ๐ฆ๐ข๐ณ๐ฏ๐ด โ or at least, starts to. Every time I run /๐ฅ๐ช๐ณ๐ฆ๐ค๐ต-๐ฉ๐ช๐ง๐ช and flag what's off, the anti-patterns file updates. The goal is for team decisions and feedback to feed back in the same way, still figuring out that part. But even the early version compounds.
Thatโs the thinking behind this experiment: how my custom skills actually chain together across the double-diamond design process.
/๐ฃ๐ณ๐ช๐ฆ๐ง-๐ค๐ณ๐ฆ๐ข๐ต๐ช๐ฐ๐ฏ โ /๐ค๐ณ๐ฆ๐ข๐ต๐ฆ-๐ฅ๐ฆ๐ค๐ฌ โ /๐ฎ๐ช๐ฅ-๐ต๐ฐ-๐ฉ๐ช๐ง๐ช ๐ฐ๐ณ /๐ฅ๐ช๐ณ๐ฆ๐ค๐ต-๐ฉ๐ช๐ง๐ช โ /๐ช๐ต๐ฆ๐ณ๐ข๐ต๐ฆ โ /๐ค๐ฐ๐ฅ๐ฆ-๐ต๐ฐ-๐ง๐ช๐จ๐ฎ๐ข โ /๐ข๐ฅ๐ฅ-๐ต๐ฐ-๐ด๐บ๐ด๐ต๐ฆ๐ฎ
Each skill's output is the next skill's input. Human checkpoint and decision making at every stage. Also, you don't have to use all the skills. Already have a brief? Start at exploration. Already have hi-fi? Jump to /๐ช๐ต๐ฆ๐ณ๐ข๐ต๐ฆ.
Check the 3min video below for the highlights of my walkthrough. ๐
Claude Design is genuinely great, but a custom workflow can be tuned to your methodology, your design system, your rhythm in ways a general tool can't, at least not yet. Until it fully closes the gaps (and I believe it will), there's room for each of us to systematize how we work with AI, not just adopt it.
Still a lot to explore for future experiments: one-click wireframe โ hi-fi switching, converting prototyping code โ production, tighter design system compliance, and more.
Curious what gaps you're working around with Claude Design or anything else. Leave your comments!