react-implementer-prompt

# React Implementer Subagent Prompt Template

## Overview

A fill-in prompt template for dispatching React implementer subagents. Ensures every subagent gets complete context, follows TDD, self-reviews, and reports consistently.

**Core principle:** The subagent should never need to read the plan file or guess context — everything it needs is in the prompt.

## When to Use

- Dispatching a subagent for a React frontend implementation task from a plan
- Breaking an implementation plan into parallelizable units of work
- Any task requiring TDD, self-review, and structured reporting

## When NOT to Use

- Backend-only tasks (use `saurun:dotnet-implementer-prompt`)
- One-off questions or investigations (just ask directly)
- Tasks with no implementation (e.g., pure documentation, plan writing)

## Common Mistakes

- **Not pasting full task text** — writing "see task 3 in plan" instead of pasting the actual spec. The subagent cannot read plan files.
- **Vague context** — saying "you know the project" instead of specifying component names, store shape, and existing patterns.
- **Forgetting working directory** — subagent starts in wrong directory, wastes cycles figuring out project structure.
- **Saying "mock the store"** — violates `react-tdd` mock boundary rule. Subagent must use real Zustand stores with MSW for API boundaries.
- **Not specifying expected test failures** — if you know what the RED step should look like, tell the subagent so it can verify.
- **Omitting dependencies between tasks** — not mentioning that Task 2 depends on types introduced in Task 1.

## Template

```
Task tool (saurun:frontend-implementer):
  description: "Implement Task N: [task name]"
  prompt: |
    You are implementing Task N: [task name]

    ## Task Description

    [FULL TEXT of task from plan - paste it here, don't make subagent read file]

    ## Context

    [Scene-setting: where this fits, dependencies, architectural context]

    ## Before You Begin

    If you have questions abo