# Design: {feature}

**Task:** {task_id}
**Accepted at:** {timestamp}

## Feature Description

{feature}

## Design Tokens (existing)

<!--
  C27: populated by apt:design from .aperant/design/tokens.json when that
  file is present. Contains a compact summary of the existing palette,
  spacing scale, typography, radii, and shadows so the planner honors the
  project's aesthetic. If tokens.json was missing at accept time, delete
  this whole section header — it is optional.
-->

## Wireframe (locked)

<!--
  Paste the locked text wireframe here. One ### Screen block per screen,
  listing purpose, key states (default / loading / empty / error), and a
  text-only layout description (no HTML, no Tailwind — that is C25).
-->

## Screen Inventory

- {screen-name}: {purpose, key states}

## Component List

- {ComponentName}: {props}, {responsibilities}

## Data Bindings

- {ComponentName} ← {store / query / prop source}

## Critique Log

<!--
  Paste the full critique log here — one `### Critique — Iteration {N}`
  sub-heading per iteration, each followed by a numbered list of
  `finding → resolution` entries produced by Stage 2 of apt:design.
-->

### Critique — Iteration 1

1. {finding → resolution}

## Handoff

Next: `/apt:plan` — the planner will read this file and generate subtasks honoring the Screen Inventory and Component List above. When design.md is present, `spec.md` includes a `## Design Reference` section that cites this file and enumerates which screens/components the subtasks cover.
