The below describes how you should be structuring new rule sections in this document.

• Required Rule Structure:

  ---
  description: Clear, one-line description of what the rule enforces
  globs: path/to/files/*.ext, other/path/**/*
  alwaysApply: boolean
  ---
  
  - **Main Points in Bold**
    - Sub-points with details
    - Examples and explanations
  

• Section References:

  • Use ALL_CAPS_SECTION to reference files
  • Example: COPILOT_RULES

• Code Examples:

  • Use language-specific code blocks

  // ✅ DO: Show good examples
  const goodExample = true;
  
  // ❌ DON'T: Show anti-patterns
  const badExample = false;
  

• Rule Content Guidelines:

  • Start with high-level overview
  • Include specific, actionable requirements
  • Show examples of correct implementation
  • Reference existing code when possible
  • Keep rules DRY by referencing other rules

• Rule Maintenance:

  • Update rules when new patterns emerge
  • Add examples from actual codebase
  • Remove outdated patterns
  • Cross-reference related rules

• Best Practices:

  • Use bullet points for clarity
  • Keep descriptions concise
  • Include both DO and DON'T examples
  • Reference actual code over theoretical examples
  • Use consistent formatting across rules