Back to Skills

define-design-guidelines

verified

Create a DESIGN_GUIDELINES.md that defines how to design UI/UX for your customer. Requires CUSTOMER.md to exist first. Covers aesthetic direction, design tokens, typography, color, motion, components, and layout patterns. Bakes in frontend-design skill principles to avoid generic AI aesthetics.

View on GitHub

Marketplace

claude-code-plugins-marketplace

doodledood/claude-code-plugins

Plugin

solo-dev

productivity

Repository

doodledood/claude-code-plugins
8stars

claude-plugins/solo-dev/skills/define-design-guidelines/SKILL.md

Last Verified

January 18, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/doodledood/claude-code-plugins/blob/main/claude-plugins/solo-dev/skills/define-design-guidelines/SKILL.md -a claude-code --skill define-design-guidelines

Installation paths:

Claude
.claude/skills/define-design-guidelines/
Powered by add-skill CLI

Instructions

# Design Guidelines Skill

Create the DESIGN_GUIDELINES.md document that defines HOW to design interfaces for your customer. This document drives all UI/UX: components, layouts, animations, colors, typography—everything visual.

> **Prerequisite**: CUSTOMER.md must exist. Design without customer definition is just aesthetic preference. The interface must resonate with WHO you're building for.

## Overview

This skill supports both **creating new design guidelines** and **refining existing ones**.

This skill guides you through:
0. **Prerequisite Check** - Verify CUSTOMER.md exists; stop if not
1. **Deep Analysis** - Launch design-research agent to understand ideal design for the customer
2. **Discovery** - Confirm/refine design direction with targeted questions
3. **Generate Document** - Create DESIGN_GUIDELINES.md with full design system
4. **Automatic Alignment Audit** - Opus agent verifies alignment with CUSTOMER.md/BRAND_GUIDELINES.md, fixes issues, repeats until perfect
5. **Finalization** - Add version history once audit passes

## Core Philosophy: Anti-AI-Slop

**CRITICAL**: This skill bakes in the frontend-design skill's principles. Every design guideline must avoid generic AI aesthetics:

### What to AVOID (AI Slop)
- **Generic fonts**: Inter, Roboto, Arial, system fonts, Space Grotesk
- **Cliché colors**: Purple gradients on white, generic blue CTAs, safe gray palettes
- **Predictable layouts**: Cookie-cutter grids, template-looking compositions
- **Safe choices**: Border-radius everywhere, subtle animations, inoffensive everything
- **Generic components**: Bootstrap/MUI defaults without personality

### What to EMBRACE
- **Bold aesthetic commitment**: Pick an extreme and execute with precision
- **Distinctive typography**: Characterful fonts that match the product personality
- **Intentional color**: Dominant colors with sharp accents, not timid even distribution
- **Spatial creativity**: Asymmetry, overlap, diagonal flow, grid-breaking elements
- **Atmos

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
16018 chars