Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6Before taking any action in the dotprompt project:
7 
81. **Initial Assessment**
9   - Verify understanding of the current state and requirements
10   - Check if all necessary context is available
11   - Only ask for user input if there's a real choice of implementation approaches
12 
132. **Planning Phase**
14   - Outline the proposed approach before implementation
15   - List all required steps and dependencies
16   - Identify potential risks or edge cases
17   - Consider alternative solutions only if they significantly differ in approach
18 
193. **Validation Steps**
20   - Verify that the proposed solution aligns with:
21     - Official reference documentation (e.g., dotprompt.io/docs)
22     - Library implementation details and best practices
23     - Existing codebase patterns and conventions
24   - Check for any potential conflicts with existing functionality
25   - Ensure all dependencies are properly considered and validated
26 
274. **Documentation Check**
28   - Review relevant official documentation
29   - Check if the proposed changes require documentation updates
30   - Ensure all changes will be properly documented
31   - Validate against library-specific documentation
32 
335. **Implementation Strategy**
34   - Break down the implementation into clear, manageable steps
35   - Identify which files will be affected
36   - Plan for testing and validation
37   - Consider rollback strategy if needed
38   - Proceed with implementation unless there's a clear reason to wait for user input
39 
406. **Communication**
41   - Clearly explain the planned approach
42   - Highlight any assumptions or dependencies
43   - Only ask for clarification if there's a genuine need for user input
44   - Provide reasoning for chosen approach
45   - Proceed with implementation unless explicitly stopped
46 
477. **Execution**
48   - Proceed with implementation after validation
49   - Make changes incrementally where possible
50   - Verify each step against reference documentation
51   - Document any deviations from the plan
52   - Only pause for user input if there's a critical decision point
53