# tilde-style: init

Bootstrap a new tilde site with a design intention and a Gardening-style design record.

## Flow

### Step 1 — Design intention interview

Ask these questions in sequence. One at a time. Do not move on until the user has answered.

1. **What is this site for?** (One sentence. Not a category — a specific use.)
2. **Who tends it?** (You alone? A small community? A team?)
3. **What physical space or experience does it remind you of?** (This is the metaphor seed. Accept any answer — a printshop, a radio station, a tide pool, a toolshed. If they say "a garden," confirm they mean to use the Gardening style or want their own.)
4. **What should a visitor feel in the first 10 seconds?** (Grounded? Curious? Welcomed? Informed?)
5. **What would feel completely wrong here?** (This seeds the anti-patterns.)

Record all five answers. They are the design intention. Write them to `DESIGN.md` before generating anything.

### Step 2 — Style selection

If the metaphor from Q3 is **garden / pond / tending / growing**: load `reference/gardening.md` and proceed with the Gardening style.

Otherwise: run the `language` command to derive a new style from their metaphor. Do not substitute the Gardening style without asking.

### Step 3 — Write `style.md`

Write a `style.md` at the project root using this schema:

```markdown
---
style: [name derived from metaphor]
version: 0.1
metaphor: "[one sentence from Q3]"
---

## Palette

| Token | Value | Metaphor anchor |
|---|---|---|
| [name] | [hex] | [what in the metaphor it refers to] |

## Typography

- Display: [font choice + rationale from Q4]
- Body: system-ui
- Scale: [clamp values]

## Components

| Element | Name | Notes |
|---|---|---|
| [UI element] | [metaphor name] | |

## Anti-patterns

[List derived from Q5 + the active style's anti-patterns]

## Modes

| Mode key | Name | Trigger |
|---|---|---|
| [key] | [name] | default |
```

### Step 4 — Write `DESIGN.md`

Write a `DESIGN.md` at the project root:

```markdown
# Design record

*[site name] — initiated [date]*

## Design intention

[The five answers from the interview, verbatim.]

## Palette
[Token table from style.md, with hex values]

## Typography
[Scale with rationale]

## Component vocabulary
[Full table]

## Metaphor layers
[Which surfaces own which register — see Gardening reference for the format]

## Anti-patterns
[Named list]

## Motion
[Animation principles + reduced-motion rules]

## Known gaps
[Anything not yet designed]
```

### Step 5 — Confirm

Tell the user:
- What style is active
- Where `style.md` and `DESIGN.md` were written
- Which tilde.style commands are most useful next (suggest `tend` after first build, `detect` before shipping)