# Design Taste Templates

Reference starter profiles for the `design-taste` standard (C26). Pick one via
`/apt:setup` or copy a file manually into `.aperant/design/taste.yaml` and edit.

`apt:design` reads `.aperant/design/taste.yaml` and injects its content as a
`TASTE_BLOCK` into Stage 1 wireframes and Stage 3 handoffs, so generated UI
reflects the declared direction instead of defaulting to generic-SaaS-Tailwind.

## Schema

```yaml
direction: brutalist | editorial | enterprise-clean | playful | <custom>

palette:
  bg: "#RRGGBB"
  fg: "#RRGGBB"
  muted: "#RRGGBB"
  accent: "#RRGGBB"
  border: "#RRGGBB"
  surface: "#RRGGBB"
  # Optional extras: accent2, accent3, success, warning, danger, mono

type:
  display: ["Font A", "Font B", "fallback"]
  body: ["Font A", "fallback"]
  # Optional: ui, mono, scale (tight|compact|cozy|loose),
  #           weights ([int,...]), measure (Xch), letter_spacing_headings

motion:
  speed: instant | fast | medium | slow
  ease: "cubic-bezier(...)" | "linear"
  hover: none | subtle | underline | lift | custom
  # Optional: enter, exit

density: compact | cozy | roomy

anti_patterns:
  - "Free-form strings listing things the direction explicitly rejects"
  - "Use anti_patterns to capture 'this is what generic SaaS would do, don't do that'"
```

Unknown fields are ignored — extend freely, but keep the six canonical fields
(`direction`, `palette`, `type`, `motion`, `density`, `anti_patterns`) so
downstream consumers always have a floor.

## When to pick which

| Direction          | Signal                                                   |
|--------------------|----------------------------------------------------------|
| `brutalist`        | Tool-over-showroom, dense info, intentionally unpolished |
| `editorial`        | Reading-first, long-form, warm neutrals, generous rhythm |
| `enterprise-clean` | B2B dashboards, admin, compliance — quiet confidence     |
| `playful`          | Consumer, creative, onboarding-heavy, delight > density  |

If none fit, copy the closest and edit — `direction` accepts any string.

## How to use

```bash
# Via setup (recommended)
/apt:setup    # pick "Design Taste" → choose a direction

# Or copy by hand
mkdir -p .aperant/design
cp packages/framework/templates/design-taste/editorial.yaml .aperant/design/taste.yaml
```

After copying, run `/apt:design <feature>` — the skill will detect
`.aperant/design/taste.yaml` and inject it into its prompts.

## Related

- `packages/framework/docs/design-taste.md` — concept doc + per-direction notes
- `packages/framework/skills/apt-design/SKILL.md` — consumer
- C27 (future) — runtime CSS tokens generated from this file
