| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 0 | 0% |
What each file covers
Sections
0 shared · 6 only in A · 1 only in B- − Cline Rules for Megarepo
- − Rules Structure
- − How Cline Uses These Rules
- − Customization
- − Rules Bank Approach
- − Consistency with Other AI Assistants
- + Advanced AI Optimization
Commands
neither file has anySection tags
0 shared · 2 only in A · 0 only in B- − architecture
- − do-not
Line diff
HerringtonDarkholme/megarepo · .clinerules/README.md
@@ −1 @@
1# Cline Rules for Megarepo
2
3This directory contains Cline Rules that provide system-level guidance for the Cline AI assistant when working on this AI setup repository.
4
5## Rules Structure
6
7The rules are organized into focused files that build upon each other:
8
91. **`01-core-principles.md`** - Fundamental principles including minimal change philosophy and AI-first development
102. **`02-development.md`** - Development guidelines for Node.js/Next.js AI projects
113. **`03-documentation.md`** - Documentation requirements and standards
124. **`04-security.md`** - Security guidelines for AI projects and API key management
13
14## How Cline Uses These Rules
15
16Cline automatically processes all Markdown files in this directory, combining them into a unified set of rules. The numeric prefixes help organize the files in a logical sequence, ensuring core principles are established before specific guidelines.
17
18## Customization
19
20These rules are tailored specifically for the Megarepo AI setup repository and should be updated as the project evolves. The rules emphasize:
21
22- **Minimal Changes**: Surgical, precise modifications that respect the repository's intentional simplicity
23- **AI-First Development**: Patterns and practices optimized for AI service integrations
24- **Security Best Practices**: Safe handling of API keys and sensitive data
25- **Node.js/Next.js Patterns**: Guidelines specific to the target technology stack
26
27## Rules Bank Approach
28
29This repository follows the "active rules" pattern where the `.clinerules/` directory contains only the rules that should be active. For projects with multiple contexts, consider creating a `clinerules-bank/` directory with additional rule sets that can be activated as needed.
30
31## Consistency with Other AI Assistants
32
33These rules are designed to work alongside other AI assistant configurations in this repository:
34- GitHub Copilot (`.github/copilot-instructions.md`)
35- Claude AI (`CLAUDE.md`)
36- Cursor AI (`.cursorrules`)
37- Gemini CLI (`GEMINI.md`)
38- Universal AI guidelines (`AGENT.md`, `AGENTS.md`)
39
40All configurations share common principles while being optimized for each assistant's specific capabilities.
HerringtonDarkholme/megarepo · .windsurf/rules/ai-optimization.md
@@ +1 @@
1# Advanced AI Optimization
2
3**Activation Mode**: Manual
4**Usage**: `@ai-optimization` - Use when optimizing AI performance, costs, or implementing advanced AI patterns
5
6<performance_optimization>
7- Cache AI responses when appropriate using Redis or in-memory solutions
8- Implement request debouncing and batching for AI API calls
9- Use edge functions for AI API proxying to reduce latency
10- Consider streaming responses for long-running AI operations
11- Monitor token usage and implement cost optimization strategies
12</performance_optimization>
13
14<advanced_patterns>
15- Implement prompt versioning and A/B testing for AI interactions
16- Use vector databases for AI-powered search and recommendation features
17- Implement AI model switching based on task complexity and cost
18- Create AI agent patterns with tool calling and function execution
19- Implement multi-modal AI integrations (text, image, audio)
20</advanced_patterns>
21
22<monitoring_and_analytics>
23- Log AI API usage, costs, and performance metrics
24- Monitor response times and error rates for AI services
25- Track user interactions and satisfaction with AI features
26- Implement health checks and alerting for AI service availability
27- Use OpenTelemetry or similar for AI service observability
28</monitoring_and_analytics>
29
30<scalability_considerations>
31- Design AI workflows for horizontal scaling and load balancing
32- Implement queue systems for background AI processing
33- Consider serverless architectures for variable AI workloads
34- Use database optimization for AI-generated content storage
35- Implement proper AI service failover and redundancy strategies
36</scalability_considerations>
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# Advanced AI Optimization
22
3−This directory contains Cline Rules that provide system-level guidance for the Cline AI assistant when working on this AI setup repository.
3+**Activation Mode**: Manual
4+**Usage**: `@ai-optimization` - Use when optimizing AI performance, costs, or implementing advanced AI patterns
45
5−## Rules Structure
6+<performance_optimization>
7+- Cache AI responses when appropriate using Redis or in-memory solutions
8+- Implement request debouncing and batching for AI API calls
9+- Use edge functions for AI API proxying to reduce latency
10+- Consider streaming responses for long-running AI operations
11+- Monitor token usage and implement cost optimization strategies
12+</performance_optimization>
613
7−The rules are organized into focused files that build upon each other:
14+<advanced_patterns>
15+- Implement prompt versioning and A/B testing for AI interactions
16+- Use vector databases for AI-powered search and recommendation features
17+- Implement AI model switching based on task complexity and cost
18+- Create AI agent patterns with tool calling and function execution
19+- Implement multi-modal AI integrations (text, image, audio)
20+</advanced_patterns>
821
9−1. **`01-core-principles.md`** - Fundamental principles including minimal change philosophy and AI-first development
10−2. **`02-development.md`** - Development guidelines for Node.js/Next.js AI projects
11−3. **`03-documentation.md`** - Documentation requirements and standards
12−4. **`04-security.md`** - Security guidelines for AI projects and API key management
22+<monitoring_and_analytics>
23+- Log AI API usage, costs, and performance metrics
24+- Monitor response times and error rates for AI services
25+- Track user interactions and satisfaction with AI features
26+- Implement health checks and alerting for AI service availability
27+- Use OpenTelemetry or similar for AI service observability
28+</monitoring_and_analytics>
1329
14−## How Cline Uses These Rules
15−
16−Cline automatically processes all Markdown files in this directory, combining them into a unified set of rules. The numeric prefixes help organize the files in a logical sequence, ensuring core principles are established before specific guidelines.
17−
18−## Customization
19−
20−These rules are tailored specifically for the Megarepo AI setup repository and should be updated as the project evolves. The rules emphasize:
21−
22−- **Minimal Changes**: Surgical, precise modifications that respect the repository's intentional simplicity
23−- **AI-First Development**: Patterns and practices optimized for AI service integrations
24−- **Security Best Practices**: Safe handling of API keys and sensitive data
25−- **Node.js/Next.js Patterns**: Guidelines specific to the target technology stack
26−
27−## Rules Bank Approach
28−
29−This repository follows the "active rules" pattern where the `.clinerules/` directory contains only the rules that should be active. For projects with multiple contexts, consider creating a `clinerules-bank/` directory with additional rule sets that can be activated as needed.
30−
31−## Consistency with Other AI Assistants
32−
33−These rules are designed to work alongside other AI assistant configurations in this repository:
34−- GitHub Copilot (`.github/copilot-instructions.md`)
35−- Claude AI (`CLAUDE.md`)
36−- Cursor AI (`.cursorrules`)
37−- Gemini CLI (`GEMINI.md`)
38−- Universal AI guidelines (`AGENT.md`, `AGENTS.md`)
39−
40−All configurations share common principles while being optimized for each assistant's specific capabilities.
30+<scalability_considerations>
31+- Design AI workflows for horizontal scaling and load balancing
32+- Implement queue systems for background AI processing
33+- Consider serverless architectures for variable AI workloads
34+- Use database optimization for AI-generated content storage
35+- Implement proper AI service failover and redundancy strategies
36+</scalability_considerations>
