Cursor rule

1---
2description:
3globs:
4alwaysApply: true
5---
6# Prompts and References
7 
8The prompts and references directories contain documentation and guides for AI agents to follow when working on various tasks in the Horizon theme.
9 
10## Living Documents
11 
12**Important**: All files in the `.cursor/prompts/` and `.cursor/references/` folders are living documents. This means:
13 
14- They should be updated as new cases are encountered
15- When you discover a useful pattern, edge case, or solution while working on an issue, update the relevant file
16- If something in these files doesn't work as expected, fix it immediately
17- Add examples from real implementation experiences
18- Remove or update outdated information
19 
20**CRITICAL ACTION REQUIREMENT**: When you encounter any pattern, issue, or solution while working - immediately update the relevant documentation file WITHOUT being asked. This includes:
21- Code patterns to avoid (like console.log in tests)
22- Better ways to accomplish tasks
23- Edge cases or pitfalls discovered
24- Clarifications for ambiguous instructions
25- New tools or commands that work better
26 
27Do not wait for the user to suggest documentation updates. Proactively maintaining these living documents is part of completing any task.
28 
29## Purpose
30 
31These documentation files serve as:
32- Step-by-step guides for common tasks
33- Documentation of best practices learned from experience
34- References for handling edge cases and pitfalls
35- Templates for consistent workflows
36 
37## Usage
38 
39When an AI agent is asked to perform a task that has corresponding documentation:
401. The agent should follow the documented steps
412. If the steps need adjustment based on the specific situation, the agent should note what changes were needed
423. **MANDATORY**: Update the documentation immediately with any new learnings, patterns, or pitfalls discovered during the task - do not wait to be asked
43 
44## Examples of Living Document Updates
45 
46- Adding a new pitfall discovered during implementation
47- Clarifying a step that was ambiguous
48- Adding a reference to a newly created documentation file
49- Updating commands or scripts that have changed
50- Adding examples of good vs bad practices
51