Anatomy of a great feature prompt

A feature prompt that works on the first try has four parts: context (what the app is and who uses it), the job (what this feature must accomplish), constraints (what must not change), and acceptance criteria (how you will know it works). Most failed prompts are missing the constraints. "Add dark mode" without "keep the current layout and colors in light mode untouched" invites the agent to redesign things you liked. Steal this template: "In [app], users need to [job]. Build [feature] so that [acceptance criteria]. Do not change [constraints]." Boring, reliable, effective.