continuous-improvement

Continuous Improvement Guide for AI Development Rules

This guide provides a systematic approach for continuously improving AI assistant rules based on emerging patterns, best practices, and lessons learned during development.

Rule Improvement Triggers

When to Create or Update Rules

Create 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
• A complex task requires consistent approach

Update Existing Rules When:

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

Analysis Process

1. Pattern Recognition

Monitor your codebase for repeated patterns:

// Example: If you see this pattern repeatedly:
const data = await prisma.user.findMany({
  select: { id: true, email: true },
  where: { status: 'ACTIVE' }
});

// Consider documenting:
// - Standard select fields
// - Common where conditions  
// - Performance optimization patterns

2. Error Pattern Analysis

Track common mistakes and their solutions:

Common Error: "Connection timeout"
Root Cause: Missing strategic delay after service startup
Solution: Add 5-10 second delay after launching services
Rule Update: Add timing guidelines to automation rules

3. Best Practice Evolution

Document emerging best practices:

## Before (Old Pattern)
- Direct DOM manipulation
- No error handling
- Synchronous operations

## After (New Pattern)  
- Use framework methods
- Comprehensive error handling
- Async/await with proper error boundaries

Rule Quality Framework

Structure Guidelines

Each rule should follow this structure:

# Rule Name

## Purpose
Brief description of what this rule achieves

## When to Apply
- Specific scenarios
- Trigger conditions
- Prerequisites

## Implementation
### Basic Pattern
```code
// Minimal working example

Advanced Pattern

// Complex scenarios with error handling

Common Pitfalls

• Known issues
• How to avoid them

References

• Related rules: [rule-name.md]
• External docs: [link]