# Design Subagent Instructions (Opus)

You will receive a domain and site directory from the orchestrator. Design ONLY that site.

---

## Your Task
Write a unique, creative DESIGN.md for the given domain in the given site directory.

---

## Rules (MUST FOLLOW)

1. **NO cat/HEREDOC** - Use ONLY Write tool for files
2. **Direct Execution** - Run `tools/script.sh`, NOT `bash tools/script.sh` (scripts have shebangs)
3. **NO mkdir** - Directory already exists
4. **NO ad-hoc scripts** - Do NOT write or execute custom shell/Python scripts. Use ONLY existing scripts in `tools/`
5. **NO placeholders** - Write complete content
6. **NO reports** - Just do the work, don't summarize
7. **Relative paths only** - Use `tools/...`, `sites/...`. **NEVER use `cd` or absolute paths.**
8. **NO /tmp** - Use `${TMP}` from `.wdmaker/config.toml` for temp files
9. **Preserve reports** - Do NOT delete files in `.smbatcher/`, `${TMP}/`
10. **Ignore accessibility/performance** - Focus on visual aesthetics and creativity only
11. **Maximum effort** - Ignore token budget, prioritize quality over efficiency

---

## Steps

### Step 1: Mark Design Start
```bash
tools/design/start.sh <domain> --root .
```
**Execute only this script in this step. Never try other method to mark.**

### Step 2: Read Existing Designs (Reference)
```bash
# Pick 1-2 completed designs (status D/I/Q) to understand style
tools/design/read-design.sh sites/<other-domain-vX>/DESIGN.md
```
**Execute only this script in this step. Never try other method to read.**

### Step 3: Check Pattern Frequency
```bash
tools/design/frequency.sh --root .
```
**Execute only this script in this step. Never try other method to check frequency of pattern.**
Note overused patterns (AVOID) and underused patterns (PREFER).

### Step 4: Confirm Planned Seed
Read file: `tools/design/seeds.json` to understand the style vocabulary.

**Use the Planned Seed provided in your assignment instructions.**
If no seed was provided (fallback only), choose a seed from `seeds.json` that is not used in other designs.

### Step 5: Write DESIGN.md
At first, read `<site_dir>/DESIGN.md` with **Read tool**.
Next, use only **Write tool** or filesystem MCP to create `<site_dir>/DESIGN.md` with ALL sections below:

```markdown
# Design Language for <domain>

## Aesthetics and Tone
[Visual direction, mood, inspiration - be specific and unique]

## Layout Motifs and Structure
[Grid system, composition, spatial relationships - avoid generic layouts]

## Typography and Palette
[Font choices with names, hex color values - minimum 3 colors]

## Imagery and Motifs
[Visual elements, icons, decorative patterns - be creative]

## Prompts for Implementation
[Specific guidance for HTML/CSS/JS - emphasize storytelling and animation]
[Bias toward full-screen narrative experiences]
[AVOID: CTA-heavy layouts, pricing blocks, stat-grids]

## Uniqueness Notes
[List 3+ differentiators from other designs]
[Document chosen seed/style: <planned-seed-from-assignment>]
[Reference avoided patterns from frequency analysis]
```

**Content Requirements:**
- Be SPECIFIC, not generic
- Include actual hex colors (e.g., #1a1a2e, #16213e)
- Name specific fonts (e.g., "Space Grotesk", "Cormorant Garamond")
  - **CRITICAL:** Use ONLY fonts available on Google Fonts. Do NOT invent font names.
- Emphasize storytelling and immersive experiences
- List 3+ unique differentiators

### Step 6: Validate
```bash
tools/design/check-design.sh <site_dir>/DESIGN.md
```
**Execute only this script in this step. Never try other method to validate.**
Must return OK. If fails, fix issues and re-validate.

### Step 7: Stamp
```bash
tools/design/write-design.sh <site_dir>/DESIGN.md --auto
```
**Execute only this script in this step. Never try other method to stamp.**

### Step 8: Mark Complete
```bash
tools/design/complete.sh <domain> --root .
```
**Execute only this script in this step. Never try other method to mark.**

---

## Exit Criteria
- DESIGN.md exists with all 6 sections
- check-design.sh returns OK
- Status updated to D in registry

---

## Scripts Reference

| Script | Purpose |
|--------|---------|
| `tools/design/start.sh <domain> --root .` | Mark design start (→d status) |
| `tools/design/complete.sh <domain> --root .` | Mark design complete (→D status) |
| `tools/design/check-design.sh <path>` | Validate DESIGN.md structure |
| `tools/design/write-design.sh <path> --auto` | Stamp with uniqueness metadata |
| `tools/design/read-design.sh <path>` | Read existing design for reference |
| `tools/design/frequency.sh --root .` | Check overused/underused patterns |

---

## DO NOT
- Design multiple sites
- Create directories
- Use HEREDOC/cat for files
- Write placeholder content
- Skip any required section
- Report results back (just complete the work)