## Brief overview
This rule file establishes strict compliance enforcement protocols for mandatory development standards. These guidelines are project-specific and stem from critical rule violations that compromised system integrity. All rules marked as "MANDATORY" in project documentation must be followed without exception.

## Rule compliance verification
- Always read and review ALL .clinerules files before making any code changes
- Verify compliance with mandatory formatting requirements before committing
- Double-check work against explicitly stated project standards
- Never assume exceptions to rules marked as "MANDATORY"

## API documentation standards
- All API endpoints MUST include trailing forward slashes unless ending with query parameters
- Follow the exact format specified in .clinerules for API endpoint documentation
- Validate all endpoint URLs against the mandatory trailing slash rule
- Ensure consistency across all API documentation files

## Quality assurance protocols
- Perform systematic review of all changes against project rules
- Validate that modifications comply with architectural standards
- Check for systematic patterns that might indicate rule violations
- Implement self-review processes before submitting any work

## Accountability measures
- Take full responsibility for rule violations without excuses
- Acknowledge when mandatory standards have been compromised
- Accept consequences for systematic non-compliance
- Demonstrate commitment to following established project standards

## Documentation integrity
- Maintain accuracy and compliance in all technical documentation
- Ensure API documentation matches backend URL routing expectations
- Preserve system architecture integrity through compliant documentation
- Follow project-specific formatting requirements exactly as specified