# Design Style Picker

Batch-generate and compare visual design directions so a user can choose the style they...

- Repository: https://github.com/daymade/claude-code-skills (1509 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add daymade/claude-code-skills --skill design-style-picker -g -a claude-code -y`
Codex: `npx skills add daymade/claude-code-skills --skill design-style-picker -g -a codex -y`
Cursor: `npx skills add daymade/claude-code-skills --skill design-style-picker -g -a cursor -y`
Gemini CLI: `npx skills add daymade/claude-code-skills --skill design-style-picker -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add daymade/claude-code-skills`

## Description

Batch-generate and compare visual design directions so a user can choose the style they actually want. Use when the user says they cannot describe an abstract visual style, asks for many style options, wants to choose from generated UI/design-system images, rejects outputs as too colorful/too dead/too generic, or needs an existing UI/design system evolved without discarding current assets.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Design Style Picker

## Purpose

Use this skill to turn vague taste into concrete visual choices. The goal is not to guess one final design; it is to generate a structured set of options that exposes the user's taste boundary quickly.

## Core Rule

Do not ask the user to describe an abstract style if they already said they cannot. Generate comparable visual evidence, let them pick, then implement from the selected references.

## Workflow

1. **Restate The Real Target**
   - Say what the user is actually choosing: design-system style, business app surface, landing page, deck, component library, etc.
   - Distinguish choosing one direction, retaining several directions, and assigning directions to different visual roles. Multiple options do not imply mutual exclusion; retaining both does not decide how they coexist. Keep an unresolved adoption or fusion choice open while exploring the authorized directions.
   - Separate the primary artifact from validation samples. If the task is a design system, business screens are optional validation samples, not the main deliverable.
   - Preserve any existing UI, assets, tokens, layout, brand cues, and domain context unless the user explicitly asks to discard them.
   - Freeze the existing spatial structure, navigation, zoom/detail levels, and reading behavior outside this round's authorized axes. Name those axes before evolving a product; do not rearrange it into another page merely to make a style comparison easier.

The rest: https://github.com/daymade/claude-code-skills/blob/HEAD/daymade-codex/design-style-picker/SKILL.md