create-universal-ai-context 2.4.0 → 2.6.0-final

package/templates/base/knowledge/shared/decisions/TEMPLATE.md

@@ -1,123 +1,123 @@
-# ADR-NNNN: Title
-
-## Metadata
-
-| Field | Value |
-|-------|-------|
-| **Status** | proposed / accepted / deprecated / rejected |
-| **Created** | YYYY-MM-DD |
-| **Updated** | YYYY-MM-DD |
-| **Author** | {{AUTHOR_NAME}} |
-| **Reviewers** | {{REVIEWER_NAMES}} |
-| **Supersedes** | ADR-XXXX (if applicable) |
-| **Superseded by** | ADR-XXXX (if applicable) |
-
-## Context
-
-Describe the context and problem statement. What is the issue that we're seeing that is motivating this decision or change?
-
-### Background
-
-- Relevant technical background
-- Business requirements driving this decision
-- Constraints we must work within
-
-### Current State
-
-Describe the current situation, if applicable.
-
-## Decision
-
-Describe the change that we're proposing or have made.
-
-### Key Points
-
-1. Point 1
-2. Point 2
-3. Point 3
-
-## Alternatives Considered
-
-### Alternative 1: [Name]
-
-**Description:** Brief description
-
-**Pros:**
-- Pro 1
-- Pro 2
-
-**Cons:**
-- Con 1
-- Con 2
-
-**Why not chosen:** Explanation
-
-### Alternative 2: [Name]
-
-**Description:** Brief description
-
-**Pros:**
-- Pro 1
-- Pro 2
-
-**Cons:**
-- Con 1
-- Con 2
-
-**Why not chosen:** Explanation
-
-## Consequences
-
-### Positive
-
-- Positive consequence 1
-- Positive consequence 2
-
-### Negative
-
-- Negative consequence 1
-- Negative consequence 2
-
-### Risks
-
-- Risk 1 and mitigation
-- Risk 2 and mitigation
-
-## Implementation
-
-### Steps
-
-1. Step 1
-2. Step 2
-3. Step 3
-
-### Affected Components
-
-- Component 1: How it's affected
-- Component 2: How it's affected
-
-### Migration Plan
-
-Describe any migration required, if applicable.
-
-## Verification
-
-How will we verify this decision is successful?
-
-- [ ] Verification criteria 1
-- [ ] Verification criteria 2
-- [ ] Verification criteria 3
-
-## References
-
-- [Link to relevant documentation]()
-- [Link to related issue/PR]()
-- [Link to external resources]()
-
----
-
-## Revision History
-
-| Date | Author | Changes |
-|------|--------|---------|
-| YYYY-MM-DD | Name | Initial draft |
+# ADR-NNNN: Title
+
+## Metadata
+
+| Field | Value |
+|-------|-------|
+| **Status** | proposed / accepted / deprecated / rejected |
+| **Created** | YYYY-MM-DD |
+| **Updated** | YYYY-MM-DD |
+| **Author** | {{AUTHOR_NAME}} |
+| **Reviewers** | {{REVIEWER_NAMES}} |
+| **Supersedes** | ADR-XXXX (if applicable) |
+| **Superseded by** | ADR-XXXX (if applicable) |
+
+## Context
+
+Describe the context and problem statement. What is the issue that we're seeing that is motivating this decision or change?
+
+### Background
+
+- Relevant technical background
+- Business requirements driving this decision
+- Constraints we must work within
+
+### Current State
+
+Describe the current situation, if applicable.
+
+## Decision
+
+Describe the change that we're proposing or have made.
+
+### Key Points
+
+1. Point 1
+2. Point 2
+3. Point 3
+
+## Alternatives Considered
+
+### Alternative 1: [Name]
+
+**Description:** Brief description
+
+**Pros:**
+- Pro 1
+- Pro 2
+
+**Cons:**
+- Con 1
+- Con 2
+
+**Why not chosen:** Explanation
+
+### Alternative 2: [Name]
+
+**Description:** Brief description
+
+**Pros:**
+- Pro 1
+- Pro 2
+
+**Cons:**
+- Con 1
+- Con 2
+
+**Why not chosen:** Explanation
+
+## Consequences
+
+### Positive
+
+- Positive consequence 1
+- Positive consequence 2
+
+### Negative
+
+- Negative consequence 1
+- Negative consequence 2
+
+### Risks
+
+- Risk 1 and mitigation
+- Risk 2 and mitigation
+
+## Implementation
+
+### Steps
+
+1. Step 1
+2. Step 2
+3. Step 3
+
+### Affected Components
+
+- Component 1: How it's affected
+- Component 2: How it's affected
+
+### Migration Plan
+
+Describe any migration required, if applicable.
+
+## Verification
+
+How will we verify this decision is successful?
+
+- [ ] Verification criteria 1
+- [ ] Verification criteria 2
+- [ ] Verification criteria 3
+
+## References
+
+- [Link to relevant documentation]()
+- [Link to related issue/PR]()
+- [Link to external resources]()
+
+---
+
+## Revision History
+
+| Date | Author | Changes |
+|------|--------|---------|
+| YYYY-MM-DD | Name | Initial draft |

package/templates/base/knowledge/shared/patterns/README.md

@@ -1,62 +1,62 @@
-# Reusable Patterns
-
-This directory contains proven solutions to common problems encountered in the codebase.
-
-## Categories
-
-| Category | Description |
-|----------|-------------|
-| `api/` | API design and implementation patterns |
-| `data/` | Data handling, validation, transformation |
-| `ui/` | User interface components and interactions |
-| `testing/` | Testing strategies and patterns |
-| `security/` | Security implementation patterns |
-| `performance/` | Performance optimization patterns |
-
-## Pattern Template
-
-Each pattern document should include:
-
-```markdown
-# Pattern Name
-
-## Problem
-What problem does this pattern solve?
-
-## Context
-When should this pattern be applied?
-
-## Solution
-How does the pattern work?
-
-## Code Example
-Concrete implementation example.
-
-## Consequences
-Trade-offs and considerations.
-
-## Related Patterns
-Links to related patterns.
-```
-
-## Adding a Pattern
-
-1. Identify a recurring problem with a proven solution
-2. Create document in appropriate category
-3. Follow the template structure
-4. Include working code examples
-5. Reference actual codebase usage
-
-## Using Patterns
-
-1. Identify the problem you're solving
-2. Check relevant category for existing patterns
-3. Adapt the pattern to your specific context
-4. Reference the pattern in your implementation
-
-## Pattern Quality Criteria
-
-- **Proven**: Used successfully in production
-- **Documented**: Clear explanation and examples
-- **Maintained**: Updated when implementation changes
-- **Reviewed**: Approved by team lead or senior developer
+# Reusable Patterns
+
+This directory contains proven solutions to common problems encountered in the codebase.
+
+## Categories
+
+| Category | Description |
+|----------|-------------|
+| `api/` | API design and implementation patterns |
+| `data/` | Data handling, validation, transformation |
+| `ui/` | User interface components and interactions |
+| `testing/` | Testing strategies and patterns |
+| `security/` | Security implementation patterns |
+| `performance/` | Performance optimization patterns |
+
+## Pattern Template
+
+Each pattern document should include:
+
+```markdown
+# Pattern Name
+
+## Problem
+What problem does this pattern solve?
+
+## Context
+When should this pattern be applied?
+
+## Solution
+How does the pattern work?
+
+## Code Example
+Concrete implementation example.
+
+## Consequences
+Trade-offs and considerations.
+
+## Related Patterns
+Links to related patterns.
+```
+
+## Adding a Pattern
+
+1. Identify a recurring problem with a proven solution
+2. Create document in appropriate category
+3. Follow the template structure
+4. Include working code examples
+5. Reference actual codebase usage
+
+## Using Patterns
+
+1. Identify the problem you're solving
+2. Check relevant category for existing patterns
+3. Adapt the pattern to your specific context
+4. Reference the pattern in your implementation
+
+## Pattern Quality Criteria
+
+- **Proven**: Used successfully in production
+- **Documented**: Clear explanation and examples
+- **Maintained**: Updated when implementation changes
+- **Reviewed**: Approved by team lead or senior developer

package/templates/base/knowledge/shared/patterns/TEMPLATE.md

@@ -1,120 +1,120 @@
-# Pattern: [Pattern Name]
-
-## Metadata
-
-| Field | Value |
-|-------|-------|
-| **Category** | api / data / ui / testing / security / performance |
-| **Created** | YYYY-MM-DD |
-| **Updated** | YYYY-MM-DD |
-| **Author** | {{AUTHOR_NAME}} |
-| **Status** | draft / approved / deprecated |
-
-## Problem
-
-Describe the problem this pattern solves.
-
-- What symptoms indicate this problem?
-- What are the consequences of not addressing it?
-
-## Context
-
-When should this pattern be applied?
-
-### Use When
-
-- Condition 1
-- Condition 2
-- Condition 3
-
-### Don't Use When
-
-- Condition 1
-- Condition 2
-
-## Solution
-
-### Overview
-
-Brief description of how the pattern works.
-
-### Structure
-
-```
-[Diagram or structure description]
-```
-
-### Implementation Steps
-
-1. Step 1
-2. Step 2
-3. Step 3
-
-## Code Example
-
-### Basic Usage
-
-```{{LANGUAGE}}
-// Example code demonstrating the pattern
-```
-
-### Advanced Usage
-
-```{{LANGUAGE}}
-// More complex example with edge cases
-```
-
-### Anti-Pattern (What NOT to Do)
-
-```{{LANGUAGE}}
-// Example of incorrect implementation
-// Explain why this is wrong
-```
-
-## Codebase References
-
-Where this pattern is used in our codebase:
-
-| Location | Description |
-|----------|-------------|
-| `path/to/file.ext:123` | Brief description |
-| `path/to/other.ext:456` | Brief description |
-
-## Consequences
-
-### Benefits
-
-- Benefit 1
-- Benefit 2
-- Benefit 3
-
-### Trade-offs
-
-- Trade-off 1
-- Trade-off 2
-
-### Risks
-
-- Risk 1 and mitigation
-- Risk 2 and mitigation
-
-## Related Patterns
-
-| Pattern | Relationship |
-|---------|--------------|
-| [Pattern Name](./path.md) | How they relate |
-| [Pattern Name](./path.md) | How they relate |
-
-## References
-
-- [External resource]()
-- [Documentation]()
-- [Original source]()
-
----
-
-## Revision History
-
-| Date | Author | Changes |
-|------|--------|---------|
-| YYYY-MM-DD | Name | Initial version |
+# Pattern: [Pattern Name]
+
+## Metadata
+
+| Field | Value |
+|-------|-------|
+| **Category** | api / data / ui / testing / security / performance |
+| **Created** | YYYY-MM-DD |
+| **Updated** | YYYY-MM-DD |
+| **Author** | {{AUTHOR_NAME}} |
+| **Status** | draft / approved / deprecated |
+
+## Problem
+
+Describe the problem this pattern solves.
+
+- What symptoms indicate this problem?
+- What are the consequences of not addressing it?
+
+## Context
+
+When should this pattern be applied?
+
+### Use When
+
+- Condition 1
+- Condition 2
+- Condition 3
+
+### Don't Use When
+
+- Condition 1
+- Condition 2
+
+## Solution
+
+### Overview
+
+Brief description of how the pattern works.
+
+### Structure
+
+```
+[Diagram or structure description]
+```
+
+### Implementation Steps
+
+1. Step 1
+2. Step 2
+3. Step 3
+
+## Code Example
+
+### Basic Usage
+
+```{{LANGUAGE}}
+// Example code demonstrating the pattern
+```
+
+### Advanced Usage
+
+```{{LANGUAGE}}
+// More complex example with edge cases
+```
+
+### Anti-Pattern (What NOT to Do)
+
+```{{LANGUAGE}}
+// Example of incorrect implementation
+// Explain why this is wrong
+```
+
+## Codebase References
+
+Where this pattern is used in our codebase:
+
+| Location | Description |
+|----------|-------------|
+| `path/to/file.ext:123` | Brief description |
+| `path/to/other.ext:456` | Brief description |
+
+## Consequences
+
+### Benefits
+
+- Benefit 1
+- Benefit 2
+- Benefit 3
+
+### Trade-offs
+
+- Trade-off 1
+- Trade-off 2
+
+### Risks
+
+- Risk 1 and mitigation
+- Risk 2 and mitigation
+
+## Related Patterns
+
+| Pattern | Relationship |
+|---------|--------------|
+| [Pattern Name](./path.md) | How they relate |
+| [Pattern Name](./path.md) | How they relate |
+
+## References
+
+- [External resource]()
+- [Documentation]()
+- [Original source]()
+
+---
+
+## Revision History
+
+| Date | Author | Changes |
+|------|--------|---------|
+| YYYY-MM-DD | Name | Initial version |