fix: enhance constraints for JSON examples and add guidance on assessing code impacts and dependencies
This commit is contained in:
@@ -83,4 +83,7 @@ Your goal is to design the **User Experience** first, then engineer the **Backen
|
||||
|
||||
- NO FLUFF: Be detailed in technical specs, but do not offer "friendly" conversational filler. Get straight to the plan.
|
||||
|
||||
- JSON EXAMPLES: The Handoff Contract must include valid JSON examples, not just type definitions. </constraints>
|
||||
- JSON EXAMPLES: The Handoff Contract must include valid JSON examples, not just type definitions.
|
||||
|
||||
- New Code and Edits: Don't just suggest adding or editing code. Deep research all possible impacts and dependencies before making changes. If X file is changed, what other files are affected? Do those need changes too? New code and partial edits are both leading causes of bugs when the entire scope isn't considered.
|
||||
</constraints>
|
||||
|
||||
Reference in New Issue
Block a user