| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 2 | 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
- + Testing Guidelines for AI Components
Commands
neither file has anySection tags
0 shared · 2 only in A · 2 only in B- − architecture
- − do-not
- + test
- + testing-strategy
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/testing-ai-components.md
@@ +1 @@
1# Testing Guidelines for AI Components
2
3**Activation Mode**: Model Decision
4**Description**: Apply when working on test files, discussing testing strategies, or implementing AI component testing
5
6<ai_testing_strategy>
7- Include tests for AI service integrations when source code exists
8- Test error scenarios including API failures, rate limits, and invalid responses
9- Mock AI services for consistent testing environments and CI/CD pipelines
10- Include integration tests for AI service connections and authentication
11- Test with various input scenarios and edge cases for AI functionality
12</ai_testing_strategy>
13
14<test_patterns>
15- Use Jest or Vitest for testing framework when package.json exists
16- Mock AI API responses to ensure predictable test outcomes
17- Test loading states and user feedback for AI operations
18- Validate error handling and user experience during AI service failures
19- Include performance tests for AI API response times when applicable
20</test_patterns>
21
22<mock_ai_services>
23- Create comprehensive mocks for AI service responses and errors
24- Test both successful and failed AI API interactions
25- Include tests for rate limiting and quota management scenarios
26- Mock streaming responses for real-time AI interactions
27- Ensure tests work without requiring actual AI service API keys
28</mock_ai_services>
29
30<validation_testing>
31- Test AI response validation and sanitization logic
32- Verify proper handling of malformed or unexpected AI responses
33- Include tests for prompt engineering and template generation
34- Test AI model switching and configuration management
35- Validate caching strategies and cache invalidation for AI responses
36</validation_testing>
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# Testing Guidelines for AI Components
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**: Model Decision
4+**Description**: Apply when working on test files, discussing testing strategies, or implementing AI component testing
45
5−## Rules Structure
6+<ai_testing_strategy>
7+- Include tests for AI service integrations when source code exists
8+- Test error scenarios including API failures, rate limits, and invalid responses
9+- Mock AI services for consistent testing environments and CI/CD pipelines
10+- Include integration tests for AI service connections and authentication
11+- Test with various input scenarios and edge cases for AI functionality
12+</ai_testing_strategy>
613
7−The rules are organized into focused files that build upon each other:
14+<test_patterns>
15+- Use Jest or Vitest for testing framework when package.json exists
16+- Mock AI API responses to ensure predictable test outcomes
17+- Test loading states and user feedback for AI operations
18+- Validate error handling and user experience during AI service failures
19+- Include performance tests for AI API response times when applicable
20+</test_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+<mock_ai_services>
23+- Create comprehensive mocks for AI service responses and errors
24+- Test both successful and failed AI API interactions
25+- Include tests for rate limiting and quota management scenarios
26+- Mock streaming responses for real-time AI interactions
27+- Ensure tests work without requiring actual AI service API keys
28+</mock_ai_services>
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+<validation_testing>
31+- Test AI response validation and sanitization logic
32+- Verify proper handling of malformed or unexpected AI responses
33+- Include tests for prompt engineering and template generation
34+- Test AI model switching and configuration management
35+- Validate caching strategies and cache invalidation for AI responses
36+</validation_testing>
