DOOM MCP vs GSD (get-shit-done)

Chris Nager built a fully playable DOOM that runs as an MCP (Model Context Protocol) app, rendering inline inside Claude and ChatGPT without a separate browser tab. The architecture uses two MCP tools — create_doom_session for inline-capable hosts and get_doom_launch_url as a browser fallback — combined with cloudflare/doom-wasm for the game runtime and a signed token system that maintains session state across both surfaces. The result is the same session whether you're playing inline or in a tab. The key technical challenge was avoiding iframe and CSP (Content Security Policy) issues. Rather than embedding a browser page inside the MCP iframe, the DOOM canvas runs directly inside the host's iframe — a subtle but critical distinction that resolved a class of rendering and input-handling bugs. The final implementation is intentionally stripped down: no save/load, no persistence adapters, just stable playable DOOM. Beyond the novelty, this project is a concrete demonstration that MCP apps are interactive surfaces, not just tool-calling JSON endpoints. The progressive enhancement pattern — same signed-token foundation serving both inline and browser modes — is a reusable architecture for any game or interactive experience that wants to live inside an AI assistant. Nager open-sourced the implementation and the blog post is a detailed technical breakdown.

GSD (get-shit-done) is a meta-prompting and context engineering system for Claude Code that imposes software engineering discipline on AI-assisted development. It replaces ad-hoc prompting with a five-step methodology — initialize, discuss, plan, execute, verify — that keeps context fresh and quality high across long, complex projects. The system works by loading specialized documentation strategically: project vision, requirements, roadmaps, and research are injected at the right phases rather than dumped into a single bloated context window. Planning produces XML-formatted task trees with built-in verification steps, and execution happens in waves — parallel where dependencies allow, sequential where they don't. Quality gates automatically detect schema drift, security regressions, and scope creep before they compound into bigger problems. For teams that have experienced the quality degradation that hits around hour three of a long Claude Code session, GSD's architecture of fresh context windows per phase is the fix. A Quick Mode handles ad-hoc tasks without the full planning overhead, making it practical for both exploratory work and milestone-driven development. It's MIT-licensed, JavaScript-based, and designed for solo developers and small teams who want spec-driven development without enterprise process overhead.