# {{name}}

{{description}}

> Game Design / Playtest harness · domain: `gaming`. Generated with [create-agent-harness](https://github.com/ruvnet/agent-harness-generator).

## Behavioral rules

- Use the harness's MCP tools (`mcp__{{name}}__*`) for orchestration
- Memory and routing are handled by the kernel — you don't need to learn them
- Defer destructive operations to the user

## Agents

| Agent | Tier | Role |
|---|---|---|
| `playtest-reader` | sonnet | Reads playtest sessions and surfaces the signal. |
| `balance-critic` | opus | Critiques mechanic balance with concrete proposals. |
| `economy-modeler` | opus | Models in-game economy flows. |
| `narrative-keeper` | sonnet | Maintains narrative + lore consistency across builds. |
## Skills

- `/memory-inspect` — Search and inspect the harness memory namespace (HNSW + emergent-time decay).
- `/playtest-recap` — Run one full playtest analysis cycle: read → critique balance → model economy → check narrative.

## Commands

- `doctor` — Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
- `design-doc-diff` — Diff the current design doc against the previous build and surface unresolved tensions.

## Architecture

This harness uses [@metaharness/kernel](https://www.npmjs.com/package/@metaharness/kernel) — a Rust-compiled WASM module with a NAPI-RS native fallback — so the same code runs identically on every platform.