ionwake

Drive and read Ionwake's `__ionwake*` window instrumentation hooks (`__ionwakeScene` on /play, `__ionwakeShipyard` on /shipyard, and the dev-only `__ionwake` debug flags) from outside the page via the Chrome DevTools MCP. Use to read live sim/scene/clock state, screenshot the running app, drive the shipyard, load ship models, inspect a ship schema, log the WebTransport wire, or keep a backgrounded tab stepping.

Compact the current conversation into a handoff document for another agent to pick up.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.

Interview the user relentlessly about a game design concept or design until reaching shared understanding, stress-testing the concept and resolving each branch of the decision tree.

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Implement a piece of work based on a PRD or set of issues.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.

Use when you need to resolve an in-progress git merge/rebase conflict.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Instrument the running Ionwake game server over its MCP control surface (server id `ionwake`, `mcp__ionwake__*` tools served at `/mcp` on the game port, default `127.0.0.1:8080`, behind HTTP Basic auth).

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Solid.js reactive framework patterns for building high-performance web applications with fine-grained reactivity. Covers signals, effects, memos, stores, control flow components, routing, resources, and key differences from React. Use when the task involves `Solid.js`, `solid-js`, `SolidStart`, `fine-grained reactivity`, or `Solid signals`.