-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathbackend-rules.mdc
More file actions
38 lines (34 loc) · 1.32 KB
/
backend-rules.mdc
File metadata and controls
38 lines (34 loc) · 1.32 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
---
description:
globs:
alwaysApply: true
---
# Backend Development Rules
## Related Rules
- @README.mdc for general coding practices
- @workflow-rules.mdc for development workflow
- @frontend-rules.mdc for frontend integration
- @api-documentation.mdc for API documentation standards
## Module References
- @backend/migrations.mdc for database migrations
- @backend/database.mdc for database management and optimization
- @backend/class-structure.mdc for class organization and structure
- @backend/code-style.mdc for code style guidelines
- @backend/background-jobs.mdc for background and delayed job processing
- @backend/api-design.mdc for API implementation and design
- @backend/data-processing.mdc for data processing and business logic
- @backend/best-practices.mdc for best practices and anti-patterns
## When to Check These Rules
- When working on models or controllers
- When writing database queries or migrations
- When implementing background jobs
- When creating or modifying API endpoints
- When documenting API endpoints
## Validation Checklist
- [ ] Code follows RuboCop conventions
- [ ] Database queries are optimized
- [ ] Background jobs use Sidekiq
- [ ] Error handling is implemented
- [ ] Business logic is properly separated
- [ ] API endpoints are properly documented
- [ ] OpenAPI/Swagger documentation is up to date