Custom Claude Skills for an End-to-End Design Workflow.

Recurring design work loses value when every chat starts at zero. I needed reusable tools with their own modes, knowledge, and clear triggers.

Recurring design work loses value when every chat starts at zero. I needed reusable tools with their own modes, knowledge, and clear triggers.

Scope

Scope

AI Tooling · Workflow Architecture · DesignOps

AI Tooling · Workflow Architecture · DesignOps

/

Structure

Fourteen skills aligned to a design process.

A Skill is a custom tool for Claude that activates automatically when its topic appears. I built fourteen and aligned them to four phases of design work: Discover, Define, Develop, Deliver. Two practices run across all four: continuous review and capturing decisions. The phases keep the system organized, the constants keep skills connected.

/

Architecture

How I build every skill.

Three architectural choices repeat across every skill. Multi-Mode keeps one tool flexible across stances without becoming a generic helper. Interview First asks before generating, so the output fits the actual question. Lazy Knowledge loads references only when needed, keeping the skill light. These emerged from practice, not from a plan.

/

Workflow

Skills that hand off to each other.

Projects usually move through the same sequence: validate the idea, plan the stack, frame the brand, decide the design, verify, then build. Each skill knows what it is not and points to the next one. Self-routing keeps friction low. The path emerged from real use, not from configuration. Sometimes I follow it, sometimes not.