claude-design-skill

这段内容是审核时保存的快照。外部来源才是完整且最新的版本。

---
name: claude-design-skill
description: >-
  Produce high-fidelity HTML design artifacts with output format matrix
  (canvas/prototype/deck/timeline). Includes tweaks protocol for iterative
  refinement and Design Direction Advisor with 10 philosophies. Use when
  creating polished design deliverables, exploring visual directions, or
  refining HTML designs iteratively. Source: jiji262/claude-design-skill.
---

# Claude Design Skill

Produce high-fidelity HTML design artifacts with intentional visual direction. Supports multiple output formats, iterative tweaks, and philosophy-guided design exploration.

---

## Output Format Matrix

Select format based on deliverable intent:

| Format | ID | Use Case | Viewport | Structure |
|--------|-----|----------|----------|-----------|
| **Canvas** | `canvas` | Static high-fidelity mockup | Fluid / responsive | Single-page design, no chrome |
| **Prototype** | `prototype` | Clickable multi-screen flow | Fluid | Shell + screens + JS state |
| **Deck** | `deck` | Presentation slides | 1920×1080 fixed | Delegate to `frontend-slides` |
| **Timeline** | `timeline` | Chronological visual narrative | Fluid vertical | Sections as timeline nodes |

### Canvas

- Full visual design of one screen or scrollable page
- Production-quality CSS — tokens, hover states, responsive breakpoints
- No lorem — real or labeled placeholder content

### Prototype

- 2–6 connected screens with click navigation
- State indicators (active nav, form validation demo)
- Inline JS only — single HTML file

### Deck

- Route to `frontend-slides` skill for 16:9 zero-dependency slides

### Timeline

- Vertical narrative: product evolution, project milestones, process documentation
- Alternating left/right nodes or progressive scroll reveal
- Date markers, connector lines, media embeds

---

## Workflow

```
1. Classify output format (canvas / prototype / deck / timeline)
2. Run Design Direction Advisor if direction unclear
3. Detect existing design system — respect if present
4. Build high-fidelity HTML artifact
5. Present to user
6. Enter tweaks protocol if refinement requested
```

---

## Design Direction Advisor

When visual direction is unspecified, select or present one of **10 design philosophies**:

| # | Philosophy | Character | Palette mood | Typography |
|---|------------|-----------|--------------|------------|
| 1 | **Brutalist Web** | Raw, exposed structure, monospace | Black/white, red accent | Mono + system |
| 2 | **Editorial Elegance** | Magazine layout, serif headlines | Cream/black, gold accent | Serif display + sans body |
| 3 | **Swiss Modernism** | Grid-precise, rational | Primary colors on white | Helvetica-like geometric sans |
| 4 | **Soft Minimalism** | Generous whitespace, subtle shadows | Off-white, soft gray, one pastel | Light sans throughout |
| 5 | **Neon Cyberpunk** | Dark base, glowing accents | Black, cyan, magenta | Condensed display + mono |
| 6 | **Organic Natural** | Rounded forms, earthy textures | Greens, browns, terracotta | Humanist sans + soft serif |
| 7 | **Retro-Futurism** | 70s–80s optimism, gradients | Orange, avocado, mustard | Rounded display fonts |
| 8 | **Luxury Refinement** | High contrast, restrained motion | Black, champagne, deep navy | High-contrast serif + thin sans |
| 9 | **Playful Pop** | Bold color blocks, illustration-ready | Saturated primaries | Rounded, friendly sans |
| 10 | **Industrial Utilitarian** | Data-dense, functional beauty | Steel gray, safety orange | Mono data + compact sans |

### Advisor workflow

```
1. Ask user goal and audience (if not known)
2. Present 2–3 philosophy options with rationale
3. User selects (or agent picks best fit with explanation)
4. Apply philosophy consistently across all design decisions
```

Do not blend philosophies unless user explicitly requests hybrid.

---

## Tweaks Protocol

Iterative refinement without full rebuilds. User tweak requests map to scoped edits:

| Tweak type | Scope | Action |
|------------|-