betterprompt

Apply a research-first, plan-review-implement-verify methodology to complex, vague, or open-ended technical requests. Triggers on verbs like "optimize", "configure", "tune", "refactor", "clean up", "ship-ready", and requests for the "best / ideal / perfect / 最佳 / 最优 / 完美 / 生产级" state of a system — vague directives without success criteria, performance targets with open paths ("LCP from 3s to 1s"), production-readiness assessments, or any task where the user expects Claude to figure out the right approach. Especially valuable when the user lacks deep technical background. Works at conversation start or mid-conversation (extracts prior context). Skip when (a) one-sentence diff or direct lookup, or (b) localized snippet with clear in/out; if the user prioritizes speed ("just do it"), apply a Light variant instead of skipping. Bias toward triggering when non-trivial; over-rigor wastes a little time, jumping to action on a real task produces wrong answers.