Team Scale
Align User Rules Across Team
Creating consistency by aligning personal AI rules across the entire team
While User Rules are personal, aligning them across the team creates consistency.
Team Practice
1. Define Core Standards Everyone Should Have
Create docs/cursor-user-rules.md in your repo:
# Recommended Cursor User Rules for Team
Copy these to your Cursor Settings → Rules for AI:
1. If a request is ambiguous, ask clarifying questions before generating code.
2. When asked to 'fix' something, first explain what's wrong and why your solution addresses it.
3. Always type function parameters and return values explicitly.
4. Extract magic numbers and strings into named constants.
5. Use early returns to reduce nesting. Avoid deeply nested if-else chains.
6. Before suggesting a solution, verify it matches the existing tech stack and patterns.
7. Prefer unknown over any. Use type guards to narrow types.
8. When modifying files, preserve existing code structure and patterns.
## Optional (personal preference):
- Add your own rules for code style preferences
- Add language-specific rules (e.g., "Use record for DTOs in C#")2. Review in Onboarding
- New developer sets up User Rules on day 1
- Include in onboarding checklist
- Discuss why each rule matters
3. Evolve Based on PR Feedback
Team retrospective insight:
"AI keeps generating 'any' types, causing runtime errors"
Action: Add to recommended User Rules:
"Never use 'any' type. Use 'unknown' and type guards instead."Why This Matters
- AI output is consistent across team members
- Code reviews focus on logic, not style
- Onboarding is faster (AI behaves predictably)
- Fewer "why did AI do this?" questions