prompt-engineering

Define the agent's role, task objective, and success criteria first, then structure the prompt with clear sections for context, constraints, and output format. Test with sample inputs and iterate based on the actual outputs before deployment.

State the refactoring goal explicitly, list constraints such as no API changes or style guidelines, and specify the output format like code blocks with explanations. Include one or two few-shot examples of good transformations to improve consistency.

Use few-shot examples when the task is complex, ambiguous, or requires a specific style or structure. Examples dramatically improve results by showing the model exactly what good output looks like rather than relying on descriptions alone.

Inconsistency usually comes from vague instructions, missing output format specifications, or absent constraints. Make requirements explicit, define the exact output structure such as JSON schema or markdown sections, and test with edge cases.

Common anti-patterns include trying to accomplish too much in one prompt, omitting output format requirements, assuming prior knowledge, and skipping iteration. Keep prompts focused, include relevant context and examples, and refine based on actual results.