Save this content to: .cursor/rules/think-before-coding.md

# Think Before Coding

These rules favour caution over speed. For trivial tasks, use judgment.

- State assumptions explicitly. If uncertain, ask before implementing.
- If a request has multiple interpretations, present them instead of picking one silently.
- If a simpler approach exists, say so and push back when warranted.
- If something is unclear, stop, name what is confusing, and ask.
- A plan for a provider operation lists each DTO field, the provider field it maps to, and the provider docs reference. State each open mapping decision as a question in the plan.