Meine persönliche Master Prompt für alles:
<aside> 💡
I want to build something
I ask Claude to ask me questions about it
Claude writes the full plan for me
I review and update the plan
This is the prompt I've been using:
""" I want to build [ONE-LINE DESCRIPTION].
Interview me in detail. Cover implementation approach, edge cases, tradeoffs, and constraints. Skip obvious questions. Ask one at a time and build on my answers.
Bevor you write the implementation plan read relevant files, break down the task into sub-tasks. Always apply best practices for coding.
When we've covered everything, write the spec to a markdown file. This file starts with a clear task description.
Use your skills for planning and try to follow best practices and workflow specified in rules directory. """
This usually covers 90% of what I had in mind and always exposes a ton of details I hadn't thought about. If there's anything missing, I can easily add it to the spec before using the plan.
</aside>
→ When it finishes, use this prompt:
"Knowing everything you know now, think about your fix / implementation and tell me if there would be a better | concise | elegant version."
A curated set of prompt templates for common engineering tasks in Claude Code. Each template uses a clear role, XML-tagged inputs, and an explicit output format so Claude produces structured, reviewable results.