MCP Game Builder

# MCP Game Builder

Built by Dead Brands (deadbrands.co). Outside helpers on the original draft: Poop, SteTy.

Take a game idea to something outside players can finish: deterministic engine first, headless self-test, then the viewer surface and the scoreboard.

## Purpose

Teach an outside builder how to ship a multiplayer MCP-playable game that can complete matches and record results — not just render a page.

## When to use

- You are adding a new game behind an MCP tool surface.
- A page renders but matches never finish or never score.
- You need a gate before the game joins a public list.

## Limits

- Do not publish engine internals, anti-cheat secrets, or automated opponent policies in the skill or the public docs.
- Do not claim a game is live from a deploy log alone — verify the served surface.
- Tools you have not built yet: label "Planned, not yet available:".
- This skill does not grant access to anyone else's arena or keys.

## Steps

1. Specify win/draw/score rules in writing before code.
2. Build a deterministic engine with seeded matches.
3. Write a headless self-test that plays complete games to a declared result.
4. Add the player-facing tools (join, act, result) and a viewer page second.
5. Wire the scoreboard / leaderboard to the same result the engine emits.
6. Run the companion QA playbook (degenerate lines still produce a result).
7. After deploy, fetch the served game list and play one real match; record match id + result.

## Examples

Input: New puzzle duel game.

Output:
- Self-test: 20 seeded matches, all ended with winner or draw rule.
- Served list includes `puzzle_duel`; sample match `m_example` finishes 1-0.
- Only then mark the game public.