self-improve

Instruction file imported from IHKodifier/etg-code (.cursor/rules/self-improve.mdc). Copyright stays with the author.

• Rule Improvement Triggers:

  • New code patterns not covered by existing rules
  • Repeated similar implementations across files
  • Common error patterns that could be prevented
  • New libraries or tools being used consistently
  • Emerging best practices in the codebase

• Analysis Process:

  • Compare new code with existing rules
  • Identify patterns that should be standardized
  • Look for references to external documentation
  • Check for consistent error handling patterns
  • Monitor test patterns and coverage

• Rule Updates:

  • Add New Rules When:

    • A new technology/pattern is used in 3+ files
    • Common bugs could be prevented by a rule
    • Code reviews repeatedly mention the same feedback
    • New security or performance patterns emerge

  • Modify Existing Rules When:

    • Better examples exist in the codebase
    • Additional edge cases are discovered
    • Related rules have been updated
    • Implementation details have changed

• Example Pattern Recognition:

  // If you see repeated patterns like:
  const data = await prisma.user.findMany({
    select: { id: true, email: true },
    where: { status: 'ACTIVE' }
  });
  
  // Consider adding to [prisma.mdc](mdc:.cursor/rules/prisma.mdc):
  // - Standard select fields
  // - Common where conditions
  // - Performance optimization patterns

• API Configuration Pattern Recognition:

  // If you see repeated API path issues like:
  static const String _questionsPath = '/api/v1/questions';  // ❌ Double prefix
  // When ApiClient.baseUrl already includes '/api/v1'
  
  // Consider adding to [general-flutter-rule.mdc](mdc:.cursor/rules/general-flutter-rule.mdc):
  // - API client base URL configuration standards
  // - Service path relative vs absolute path guidelines
  // - API debugging patterns for 401/404 errors
  // - Path concatenation validation rules

• Rule Quality Checks:

  • Rules should be actionable and specific
  • Examples should come from actual code
  • References should be up to date
  • Patterns should be consistently enforced

• Continuous Improvement:

  • Monitor code review comments
  • Track common development questions
  • Update rules after major refactors
  • Add links to relevant documentation
  • Cross-reference related rules

• Rule Deprecation:

  • Mark outdated patterns as deprecated
  • Remove rules that no longer apply
  • Update references to deprecated rules
  • Document migration paths for old patterns

• Documentation Updates:

  • Keep examples synchronized with code
  • Update references to external docs
  • Maintain links between related rules
  • Document breaking changes Follow cursor_rules.mdc for proper rule formatting and structure.