# WP-44 — `gen:context` generator

Status: todo
Phase: 8 — platform/DX/showcase
Priority: P3
Depends on: WP-38, WP-43

## Why

Adding a bounded context is currently a manual multi-file edit (folders + tsconfig alias + copied
ESLint boundary block + lazy route) — the `new-context` skill's most error-prone steps. Mechanise it.

## Decisions

- `gen:context` (same tool as WP-43) emits `{domain,application,infrastructure,ui,contracts}`
  folders + the `@ctx/*` tsconfig path alias + a lazy route + the boundary entry.
- **Simpler because of WP-38:** boundaries are declarative by then, so the generator adds one config
  entry instead of hand-copying ESLint blocks.
- Replaces the manual portion of the `new-context` skill.

## Files

- Extend the WP-43 generator setup with a `context` generator + templates.
- Wire tsconfig alias + boundary config + route insertion (idempotent edits).
- Update `.claude/skills/new-context/SKILL.md`.

## Acceptance criteria

- [ ] `npm run gen:context <name>` produces a context that lints clean (boundaries recognised) and
      routes lazily.
- [ ] Boundary tool (WP-38) validates the new context's allowed edges.
- [ ] `npm run ci` green.