Skip to main content

FOR DESIGNERS

Designers

Whether design is your whole job or one hat you wear, claude-kit gives visual and UX work a real owner instead of letting it get squeezed in between code changes.

The designer role​

The designer appears in the software, content, and (when you add it) other profiles. It owns every visual decision: the design system, brand, screens, motion, UX writing, accessibility for the UI. When a request touches how something looks or feels, the coordinator routes it here.

It comes wired with design-minded skills:

  • Design systems — token architecture, type scales, component libraries, light/dark theming.
  • Brand — discovering a mark, voice, and a full brand kit from a brief.
  • UI/UX — production-grade interfaces with real craft.
  • Animation — GSAP for timelines, scroll-driven motion, and smooth, performant interactions.

You don't have to name the skill — describe the work and the designer reaches for the right one.

Point instead of describe — annotate​

The standout for designers: /kit-annotate. If you're reviewing a running React app, you can click any element, leave a note right on it ("tighten this spacing," "wrong shade of blue here"), and Claude reads a structured record — the component, its place in the tree, the source file, and your comment — then fixes the code.

It's the difference between writing a paragraph describing which button and just pointing at it.

A typical session​

"Design a settings page — match our design system, dark mode included, and animate the section transitions."

The designer pulls the design-system skill for tokens and components, the GSAP skill for the transitions, and produces a coherent screen. Reviewing it live? Switch on annotate and point at what needs another pass.

Make it yours​

  • Bring your brand. Point the designer at your brand kit; with memory on it holds those decisions across sessions.
  • Adjust the team. Add or trim roles with /kit-customize.

Where to go next​