The Playbook

Before answering, research this thoroughly. Find 3 credible perspectives, summarize what you learn from each, then give me your recommendation based on the evidence. Show your reasoning.

Before you build, write, or plan anything — interview me first. Ask me 5 specific questions to understand exactly what I need, one at a time. Don't start working until you have all my answers.

Here's an example of the quality and style I want: [paste your example here] Match this tone, structure, and level of detail. Don't copy it — use it as a reference for what "good" looks like. Explain what you're borrowing from it.

Look at what we have so far. What is the single most impactful improvement you could make right now? Not a list of 10 things — one move that makes the biggest difference. Explain why this one matters most.

Act as a skeptical critic. What are the 3 weakest parts of this? Where will it break? What am I not seeing? Be honest and specific — I need the hard truth, not encouragement.

Explain why you chose this approach over the alternatives. What are the tradeoffs? What would you do differently if you had different constraints? If I asked you to start over with a completely different strategy, what would it be and why?

Write acceptance criteria for this project. What specific conditions must be true for this to be considered done? List them as checkboxes I can verify. Include edge cases that would catch a sloppy version.

Look at this project I'm proud of: [paste or describe your best work] Identify the patterns that made it good. What decisions, structures, or approaches could I reuse? Turn those patterns into a reusable prompt template I can apply to future projects.

Summarize what I just built / wrote / created in a way I could share publicly. Write it as a short, engaging update — like a devlog or LinkedIn post. Focus on what's interesting about the approach, not just what was done. Keep it under 150 words.