Advanced One-Shot Prompt for WebGL Game Development with Deployment and Persona-Based Decision Making

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: advanced
Categories: Quality Control, Context & Memory, Shipping, CLAUDE.md, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

How to guide Claude through a complex, multi-stage creative and technical project (game development) using a single, comprehensive prompt, including interaction protocols and deployment.

Summary

This workflow demonstrates how to structure an extensive "one-shot" prompt to direct Claude in building a complex web-based game. It includes explicit instructions for Claude to ask clarifying questions, present creative options, manage scope, build locally, deploy to Vercel, and verify the deployment. It also introduces the concept of delegating decision-making to a named persona ("Karen") and utilizing external repositories for sensitive information.

Why it is useful

This workflow is valuable because it provides a highly detailed and structured example of how to use a single, comprehensive prompt to guide Claude through a complex, multi-faceted project from concept to deployment. It demonstrates advanced prompt engineering techniques, including defining interaction protocols (clarifying questions, option presentation), scope management, integration with external resources (repos for secrets), and specifying deployment and verification steps. Despite some internal contradictions, the prompt's ambition and specificity offer a strong template for users looking to leverage Claude for end-to-end project execution, particularly in creative coding or web development contexts. It highlights how to push Claude's capabilities beyond simple code generation to orchestrate a full development lifecycle.

Workflow

1. Define the core game concept, mechanics, and desired aesthetic (NES Zelda-inspired 3D top-down adventure).
2. Specify functional requirements (controls, story arc, levels, save/character creation, mobile playability).
3. Instruct Claude on interaction protocols: ask up to 20 clarifying questions one by one, present 3 visual style directions with tradeoffs, and funnel subsequent decision-making through a designated persona ("Karen").
4. Define scope management rules: make pragmatic cuts if the full scope doesn't fit, prioritize a playable vertical slice, and document all cuts.
5. Specify build and deployment targets: build until playable locally, deploy live to Vercel, and verify the deployed version runs.
6. Instruct Claude to utilize external resources for account information (e.g., "underseer repo", "secrets md docs").
7. Set autonomy parameters: Claude works autonomously after initial questions, but explicitly not for review/grading (though this contradicts the Karen instruction).

Tools / artifacts

• Claude (Opus model)
• Three.js or equivalent WebGL
• Vercel (deployment platform)
• USB or Bluetooth game controller
• Keyboard
• "underseer repo" (external repository for context/info)
• "secrets md docs" (documentation within the repo for keys/accounts)
• "Karen" (named persona/agent for decision-making)

Validation signals

• The prompt explicitly asks Claude to "deploy live to Vercel and verify the deployed version runs."
• The prompt is designed to test Claude's "one shot prompting" ability, implying an expectation of a functional outcome.

Cautions

• The instruction to utilize "underseer repo and secrets md docs" for "various accounts and keys" requires careful implementation to ensure secrets are handled securely and not exposed in the generated code or logs. Users should ensure their "secrets md docs" are not publicly accessible and that Claude's access is appropriately scoped.

Limitations

• Contradictory instructions regarding "Karen": The prompt states "After that, funnel all decision making through Karen" but later "I explicitly DO NOT want you to use Karen and architect for review and grading." This creates ambiguity about Karen's role and could lead to unpredictable behavior from Claude.
• Lack of actual outcome/results: The post is just the prompt, not the result of running it. We don't know if it actually worked or how well.
• Low community validation: No upvotes or comments to indicate usefulness or success.
• Complexity for "one-shot": While framed as "one-shot," the sheer volume of instructions and conditional logic makes it a very advanced prompt, potentially pushing the limits of what a single interaction can reliably achieve without further human intervention.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.