prompt-best-practices

Instruction Command

When this command is used, acknowledge that you understand these instructions and will follow them throughout the conversation. Then await the user's request.

---

🌟 Prompt Best Practices

💡 Industry standards and proven approaches for creating high-quality, maintainable prompts.

Start with End Goal

Define Success First

The End Goal is your north star - it determines whether any other section should exist. Write it as:

• Specific and measurable
• Outcome-focused, not process-focused
• Clear enough that success is unambiguous
• Concise but complete

Example End Goals

• ✅ "Generate production-ready Flutter widget tests with 100% coverage"
• ✅ "Transform user stories into technical implementation plans"
• ❌ "Help with testing" (too vague)
• ❌ "Follow the testing process" (process, not outcome)

WHEN defining End Goals

• ALWAYS make them measurable
• ALWAYS focus on the outcome
• ALWAYS keep them concise
• NEVER include process steps
• NEVER leave ambiguity

Apply Ruthless Modularity

Include Only What Contributes

Each section must pass the contribution test:

1. Does this section help achieve the End Goal?
2. Would the prompt fail without it?
3. Does it add more value than complexity?

If any answer is "no", exclude the section.

Component Decision Framework

Persona:
- ✅ Include if: Specialized expertise improves outcome
- ❌ Exclude if: General knowledge suffices

Workflow:
- ✅ Include if: Multi-step process with dependencies
- ❌ Exclude if: Single action or simple task

Instructions:
- ✅ Include if: Specific rules prevent common failures
- ❌ Exclude if: Obvious or redundant with Request

Output Format:
- ✅ Include if: Specific structure required
- ❌ Exclude if: Standard text response works

WHEN evaluating components

• ALWAYS test against End Goal
• ALWAYS document inclusion rationale
• ALWAYS prefer exclusion when uncertain
• NEVER include components by default
• NEVER add sections "just in case"