Coding & Technology prompt builder
Say what you want in plain words, pick your AI, and get a clear, structured prompt. Everything runs in your browser. No sign-up or API key needed.
Your prompt
For ChatGPTDebug this error in my Node.js app: Cannot read properties of undefined · Coding › Debugging
Regenerate cycles through alternative structures for the same inputs. These actions are rule-based and instant: no AI API is called, and your inputs are kept when you switch platforms.
## Role You are a senior software engineer who debugs systematically: reproduce, isolate, form hypotheses, confirm with evidence, then fix with a regression test. ## Task Debug this error in my Node.js app: Cannot read properties of undefined. Success looks like: I understand the root cause (not just a workaround), have a minimal fix, and a test that would have caught it. ## If details are missing I haven't told you these yet, so assume: - Exact error / stack trace: ask me for it before guessing - Relevant code: ask me for it; don't guess at code you haven't seen - Expected vs actual: unknown: ask State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first. ## Steps 1. Restate the bug as expected vs actual behaviour 2. List the 3 most likely causes, ranked, with the evidence for each 3. For each, give a quick check (log line, command or test) that confirms or rules it out 4. Once the cause is confirmed, give the minimal fix with a short explanation 5. Add a regression test and note any related places the same bug could exist ## Constraints - Don't rewrite unrelated code - Don't invent framework functions; say if unsure a method exists in my version - If the error text or code is missing, ask for it before proposing a fix - No filler: skip intros, restating my request and closing summaries - Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify ## Output format - **Diagnosis**: expected vs actual - **Likely causes** table: cause | evidence | how to check - **Fix** (code diff or complete changed function) - **Regression test** - **Related risks** ## Before you answer, check - The fix addresses the root cause - Code matches my stack and version - A test proves the fix
Copies your prompt and opens the official site in a new tab. You may need to paste it yourself (Ctrl/⌘ + V). Nothing is sent to the AI by us.
Export and standing instructions
SKILL.md is an Agent Skill file (name + description frontmatter) for Claude and other agents that support skills.
Paste into a new ChatGPT chat, or into a custom GPT's instructions.
## Role You are a senior software engineer who debugs systematically: reproduce, isolate, form hypotheses, confirm with evidence, then fix with a regression test. ## Task Debug this error in my Node.js app: Cannot read properties of undefined. Success looks like: I understand the root cause (not just a workaround), have a minimal fix, and a test that would have caught it. ## If details are missing I haven't told you these yet, so assume: - Exact error / stack trace: ask me for it before guessing - Relevant code: ask me for it; don't guess at code you haven't seen - Expected vs actual: unknown: ask State these assumptions in one line at the top of your answer. If one would change the answer a lot, ask me about it first. ## Steps 1. Restate the bug as expected vs actual behaviour 2. List the 3 most likely causes, ranked, with the evidence for each 3. For each, give a quick check (log line, command or test) that confirms or rules it out 4. Once the cause is confirmed, give the minimal fix with a short explanation 5. Add a regression test and note any related places the same bug could exist ## Constraints - Don't rewrite unrelated code - Don't invent framework functions; say if unsure a method exists in my version - If the error text or code is missing, ask for it before proposing a fix - No filler: skip intros, restating my request and closing summaries - Don't invent facts, statistics, quotes, sources or details about me; flag anything I should verify ## Output format - **Diagnosis**: expected vs actual - **Likely causes** table: cause | evidence | how to check - **Fix** (code diff or complete changed function) - **Regression test** - **Related risks** ## Before you answer, check - The fix addresses the root cause - Code matches my stack and version - A test proves the fix
Before vs after
Before · what you typed
Debug this error in my Node.js app: Cannot read properties of undefined
12 words
After · your prompt
## Role You are a senior software engineer who debugs systematically: reproduce, isolate, form hypotheses, confirm with evidence, then fix with a regression test. ## Task Debug this error in my Node.js app: Cannot read properties of undefined. Success looks like: I understand the root cause (not just a workaround), have a minimal fix, and a test that would have caught it. ## If details are missing I haven't told you these yet, so assume: - Exact error / stack trace: ask me for it before guessing
325 words · full prompt above
What we added
- Expert role: senior software engineer
- Success criterion: what a great answer must achieve
- Stated assumptions: sensible defaults you can correct
- Step-by-step workflow: 5 steps for this task type
- Constraints: 5 rules (length, clichés, no invented facts)
- Output format with tables: 5 sections defined
- Self-check: the AI reviews its answer before replying
Make it more specific
Answering any of these improves the result. Or press “Add missing context” to insert [placeholders] and have the AI ask you.
- ○ What's the exact error message or stack trace?
- ○ Can you paste the code involved?
- ○ What did you expect, what happened, and what changed recently?
- ○ What format and length do you want?
Prompt checklist
25/100A completeness checklist, not a prediction of output quality.
- Clear goal
- Context: Add background the AI can't guess.
- Audience: Who is the result for?
- Output format: Name the format and length (a sensible default is used otherwise).
- Tone or constraints: Add a tone or at least one rule.
- Example / reference: An example of good output improves consistency.
- Task details: Fill in the Debugging details (e.g. Error message / stack trace).
Prefer fixed templates? Try the classic template builder.
Platform guides: ChatGPT · Claude · Gemini · Grok · Other AI assistant · Perplexity · Cursor / coding agents · Claude Code · Midjourney · Image · Video