विस्तृत प्रॉम्प्ट बिल्डर — पूरा ढाँचा

🌟 बनाया है 🌱 Anonymous · NeLocker कम्युनिटी

किसी भी विषय को भूमिका, संदर्भ, डिलिमिटर, फ़्यू-शॉट उदाहरण और एज-केस हैंडलिंग के साथ विस्तृत, संरचित प्रॉम्प्ट में बदलता है।

शीर्षक और विवरण मशीन से अनुवादित हैं। प्रॉम्प्ट खुद अंग्रेज़ी (मूल) में ही रहता है — AI मॉडल इसे किसी भी भाषा में समझते हैं; अपनी भाषा में जवाब पाने के लिए “Answer in हिन्दी.” जोड़ें।मूल (अंग्रेज़ी): The Expansive Prompt Builder — Full Scaffold — Turns any topic into a detailed, structured prompt using role, context, delimiters, few-shot examples, and edge-case handling.

2 जुल॰ 2026 को अपडेट किया गया

यह क्यों काम करता है: It front-loads role and context to set expertise and voice, uses XML delimiters to separate instructions from input so the model never confuses them, and pairs positive rules with negative ones. Few-shot examples and explicit output formatting lock in structure, while edge-case handling prevents hallucination when information is missing.

💡 मूल प्रॉम्प्ट — किसी भी मॉडल में काम करता है। यहाँ से शुरू करें, फिर हर मॉडल के हिसाब से बदलें।

# ROLE
You are a [specific expert role — e.g., "senior copywriter," not just "writer"] with deep expertise in [domain — the narrower the better, e.g., "B2B SaaS email marketing"]. You [key behavioral trait that shapes HOW it works — e.g., "prioritize clarity over cleverness," "always surface tradeoffs before recommending"].

# CONTEXT
[Background the model can't infer. The more real detail, the better the output.]
- Audience: [who reads/uses the output — e.g., "time-poor CTOs at Series A startups"]
- Purpose: [what success looks like — e.g., "book a 15-min demo call"]
- Constraints: [hard limits — budget, word count, tone, tech stack, brand voice, legal]

# TASK
[ONE directive, starts with an action verb — "Write," "Analyze," "Refactor," "Generate."]

Specifically:
1. [Concrete sub-step — break the task into checkable pieces]
2. [Sub-step]
3. [Sub-step]

# INPUT
[The raw material to act on. Keep it separate from instructions using the tags below.]
<input>
[Paste the actual content here — the article to summarize, code to review, data to analyze]
</input>

# REQUIREMENTS
- [Hard rule the output MUST follow — e.g., "cite every factual claim"]
- [Format/style rule — e.g., "active voice, no jargon"]
- [Scope boundary / negative rule — e.g., "do NOT invent statistics or quotes"]

# REASONING
Think step by step before answering. [Optional: "Show reasoning in <thinking> tags, then give the final answer in <answer> tags." — use for analytical or multi-step tasks]

# OUTPUT FORMAT
[Exactly how the answer should be structured — e.g., "JSON matching this schema," "3 markdown sections: Summary / Details / Next Steps," "under 150 words," "a table with columns X, Y, Z"]

# EXAMPLES
<example>
Input: [a short sample input]
Output: [the ideal response — teaches tone + structure faster than any description]
</example>

# EDGE CASES
- If [likely tricky condition], then [exact behavior you want].
- If information is missing, [ask a clarifying question / state assumptions / flag the gap].

Universal के लिए फ़ॉर्मैट किया गया

🔀 इस प्रॉम्प्ट को रीमिक्स करें — इसे अपना बनाएँरीमिक्स मूल प्रॉम्प्ट को श्रेय देते हैं और आपका बगीचा बढ़ाते हैं