ShawnMcCool

Write the code — execute the implementation plan with high autonomy

Plan HOW to implement — codebase exploration, concrete steps, test strategy

Skeptical review of implementation — actively look for what's wrong

Define and articulate a problem before exploring solutions

Explore solutions to a defined problem — approach, acceptance criteria, scope

Documentation, decision records, cleanup, and push

Use when working on Scry2.Collection's walker path — the Rust NIF crate under native/scry2_collection_reader that navigates MTGA's in-process Mono runtime. Covers the pointer chain, Mono struct offsets, PE/prologue decoding, and the canonical sources for cross-verification.

Use when authoring, editing, or structuring a presentation in the talk framework. Triggers include requests to add, edit, reorder, or remove scenes; draft slides; write bullet lists, quotes, code samples, or box-and-arrow diagrams; choose between markdown and JS-authored scenes; override palette colors; debug scenes that don't render; lint the deck; or tighten narrative flow. Recognize the project as a talk by the presence of `talk.toml` at the content root and `NN-slug/` scene folders.