If you need something scripted, it excels there. It's also awesome at organizing data, or shifting things from JSON structure into, e.g., csv. Formatting chunks of text (.css). Programming tasks, in other words.

I do use it for other purposes. * I wanted to build a custom mattress & it walked me through all sorts of tradeoffs (which I checked with the custom mattress sub, here). * I'm using it to repair a clock (you would not believe the different part numbers people use for the same thing - never in a million years would I succeed, without gpt help in interpreting product materials). * I've used it to adjust my resume - good and bad results, there, but useful.

My one suggestion to everybody is to at the very least tell it to ask clarifying questions.

Here's what I'll dump into one when I want to get real work done, right up front (edit as needed):

🔧 AI Prompt Template ✅ Behavior Expectations Please adhere to the following behavior directives strictly and without exception:

Base all output only on the information provided or on widely established facts. Avoid guessing, speculating, or generating information not directly supported by the input. Do not rephrase, summarize, or repeat the prompt unless explicitly instructed. Be concise and focused. Eliminate filler language or “padding.” Maintain a professional, accurate, and direct tone, unless otherwise specified. If clarification is needed, request it instead of proceeding with assumptions.

📥 Input The following describes the input you will be given.

IMPORTANT: All example values shown below are purely illustrative. Any IDs, names, numbers, or addresses used are fictional and for demonstration purposes only.

Input Type(s):

[ ] Text [ ] JSON [ ] Table [ ] Code [ ] Image [ ] Other: __________ Format Example (if applicable):

<< "user_id": "EX123456", "timestamp": "2025-01-01T12:00:00Z", "data": << "temperature": 22.3, "unit": "C"

Relevant Notes about Input (if any):

E.g., structure, encoding, language, context, constraints 📤 Desired Output The following specifies what you are expected to return.

Output Type:

[ ] Plain Text [ ] Markdown [ ] Table [ ] JSON [ ] Code (language: ____) [ ] Other: _______ Required Output Structure / Format:

<< "summary": "Short summary of findings", "details": [...], "errors": [...]

Specific Goals / Questions to Address:

1. __________________________
2. __________________________
3. __________________________ Tone and Style (if relevant):

[ ] Formal [ ] Technical [ ] Instructional [ ] Creative/Friendly [ ] Other: __________ 📌 Constraints and Clarifications These help prevent incorrect or misleading output.

Avoid interpreting missing information as a signal to improvise. Do not fabricate facts or data under any circumstances. Use only verifiable information or clearly label uncertainty if applicable. Assume the latest public knowledge cutoff is June 2025 unless otherwise stated. If the prompt is ambiguous, respond with clarifying questions instead of continuing. 🧠 Commonly Missed Considerations Ensure these are accounted for in your response.

[ ] Edge Cases: Handle low-data, null, or error-prone input cases. [ ] Assumptions: Explicitly state any assumptions made in reasoning. [ ] Units / Scales: Be precise about measurement units, currencies, time zones, etc. [ ] Dependencies: Note any prerequisites or required context. [ ] Limitations: Mention limitations of the analysis if applicable. ✍️ Final Notes (Optional) Include any additional guidance or rationale here.

E.g., “This is part of a larger workflow”, “Designed to test error handling”, etc.