900-component-template

TL;DR: This template provides the standard structure for BIG BRAIN component rule files, ensuring consistent formatting, comprehensive documentation, and proper integration with the memory bank system.

1.0.0

```
---
description: WHEN [activation context] APPLY/ENSURE/FOLLOW [action or requirement]
globs: ["**/*.mdc", "**/*.md"]
alwaysApply: true/false
---

> **TL;DR:** Brief 1-3 sentence summary of the component's purpose and function.

<version>1.0.0</version>

<context>
  Detailed explanation of why this component exists, what problem it solves,
  and its importance within the BIG BRAIN system. Provide sufficient background
  for understanding the component's purpose without requiring extensive
  cross-referencing.
</context>

<requirements>
  <requirement>First specific requirement this component must fulfill</requirement>
  <requirement>Second specific requirement this component must fulfill</requirement>
  <requirement>Additional requirements as needed</requirement>
  <requirement>Be specific, actionable, and verification-friendly</requirement>
  <requirement>Focus on WHAT must be achieved, not HOW</requirement>
</requirements>

<details>
  <section-name>SECTION NAME IN UPPERCASE</section-name>
  <content>
    Detailed content for this section, organized in a structured manner.
    Use consistent formatting throughout:

    1. **Primary Items**
       - Sub-item details
       - Additional details
       - More information

    2. **Secondary Items**
       - Supporting information
       - Implementation guidance
       - Best practices

    Add as many structured sections as needed to fully document the component.
    Use numbered lists for sequential processes and bulleted lists for collections.
  </content>
</details>

<details>
  <section-name>ANOTHER SECTION NAME</section-name>
  <content>
    Additional section content organized similarly.

    Include relevant:
    - Implementation details
    - Usage guidelines
    - Integration information
    - Examples
    - Edge cases

    Ensure comprehensive coverage of the component's functionality.
  </content>
</details>

<details>
  <section-name>COMPLEXITY ADAPTATION</section-name>
  <content>
    Explain how the component adapts to different complexity levels:

    **Level 1 (Simple)**
    - Simplified behavior for basic tasks
    - Minimal requirements
    - Streamlined processing

    **Level 2 (Moderate)**
    - Standard behavior for routine tasks
    - Complete but focused requirements
    - Regular processing depth

    **Level 3 (Complex)**
    - Enhanced behavior for complex tasks
    - Comprehensive requirements
    - Thorough processing

    **Level 4 (Critical)**
    - Maximum behavior for mission-critical tasks
    - Exhaustive requirements
    - Rigorous processing with additional validation

    Specific details should explain how the component's behavior changes
    based on task complexity level.
  </content>
</details>

<details>
  <section-name>INTEGRATION WITH MEMORY BANK</section-name>
  <content>
    Explain how this component integrates with the memory bank:

    1. **Documentation Updates**
       - What updates are made to activeContext.md
       - What is recorded in progress.md
       - What patterns are documented in systemPatterns.md
       - What technical details are updated in techContext.md

    2. **Knowledge Preservation**
       - How critical information is preserved
       - How decisions are documented
       - How component state is maintained
       - How reference integrity is preserved

    3. **Cross-Component Integration**
       - How this component interacts with others
       - Key integration points
       - Dependency relationships
       - Interface contracts

    This section is crucial for ensuring the component works within the
    overall memory bank system.
  </content>
</details>

<details>
  <section-name>EXAMPLES</section-name>
  <content>
    Provide concrete examples of the component in action:

    **Example 1: [Brief Description]**
    ```
    [Detailed example implementation or usage]
    ```

    **Example 2: [Brief Description]**
    ```
    [Another example showing different aspect]
    ```

    Examples should be practical, illustrative, and cover both typical
    usage and important edge cases.
  </content>
</details>

## 📝 Version History

| Version | Date       | Author    | Changes                           |
| ------- | ---------- | --------- | --------------------------------- |
| 1.0.0   | YYYY-MM-DD | BIG BRAIN | Initial component implementation  |
```