# refactor: restructure .cursor directory for improved organization and
clarity
## Description
This PR refactors the `.cursor` directory to enhance organization,
clarity, and maintainability.
### Problem
The existing `.cursor` directory lacked clear organization, making it
difficult to find specific files, understand their purpose, and add new
components consistently.
### Solution
A comprehensive restructuring:
#### New Directory Structure
```
.cursor/
├── settings.json # Main configuration file
├── docs/ # Documentation
│ ├── guides/ # In-depth guides
│ ├── references/ # Quick references
│ └── practices/ # Best practices
├── rules/ # Rule definitions
│ ├── commit/ # Commit-related rules
│ ├── quality/ # Code quality rules
│ ├── testing/ # Testing rules
│ └── verification/ # Verification rules
└── hooks/ # Git hooks and scripts
```
#### Key Changes
1. **Logical Categorization**: Organized files into clear categories
based on purpose
2. **Improved Documentation**: Added comprehensive README files for each
directory
3. **Standardized Naming**: Implemented consistent kebab-case naming
convention
4. **Reference Updates**: Updated all internal references to point to
new file locations
### Benefits
- **Easier Navigation**: Clear categorization makes finding files
intuitive
- **Improved Understanding**: Comprehensive documentation explains
purpose and usage
- **Simplified Maintenance**: Logical structure makes updates and
additions easier
- **Better Onboarding**: New team members can quickly understand the
system
This refactoring sets a solid foundation for all Cursor AI-related
configurations and rules, making it easier for the team to leverage
Cursor's capabilities.
## Description
Introduced a new directory for cursor-specific rules and behaviors,
including commit message guidelines and workspace rules for derived
files and Cypress tests. This enhances the consistency and clarity of
our development practices.
Fixes #`Issue Number`
_or_
Fixes `Issue URL`
> [!WARNING]
> _If no issue exists, please create an issue first, and check with the
maintainers if the issue is valid._
## Automation
/ok-to-test tags=""
### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results -->
> [!CAUTION]
> If you modify the content in this section, you are likely to disrupt
the CI result for your PR.
<!-- end of auto-generated comment: Cypress test results -->
## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [ ] No
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Expanded project guidelines to clarify best practices for team
communications, workspace organization, and testing procedures—enhancing
internal coordination and overall product quality.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
