| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 8 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 1 | 33% |
What each file covers
Sections
0 shared · 6 only in A · 8 only in B- − Cline Rules for Megarepo
- − Rules Structure
- − How Cline Uses These Rules
- − Customization
- − Rules Bank Approach
- − Consistency with Other AI Assistants
- + Windsurf Rules for Megarepo
- + Rule Files
- + Always On Rules (Applied Continuously)
- + Glob Pattern Rules (File-Type Specific)
- + Model Decision Rules (Context-Aware)
- + Manual Rules (On-Demand)
- + Usage
- + Rule Design Principles
Commands
neither file has anySection tags
1 shared · 1 only in A · 1 only in B- − architecture
- + types
- 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/README.md
@@ +1 @@
1# Windsurf Rules for Megarepo
2
3This directory contains workspace-level rules for Windsurf AI to follow when working on the megarepo AI setup repository.
4
5## Rule Files
6
7### Always On Rules (Applied Continuously)
8- **ai-development-core.md** - Core AI development guidelines and repository context
9- **security-api-keys.md** - Security guidelines and API key management practices
10
11### Glob Pattern Rules (File-Type Specific)
12- **typescript-javascript.md** - Applied to `**/*.{ts,tsx,js,jsx}` files
13- **documentation-standards.md** - Applied to `**/*.md` files
14
15### Model Decision Rules (Context-Aware)
16- **testing-ai-components.md** - Applied when working on testing strategies or test files
17
18### Manual Rules (On-Demand)
19- **ai-optimization.md** - Use `@ai-optimization` for advanced performance optimization
20
21## Usage
22
23Windsurf automatically discovers and applies these rules based on their activation modes. The rules complement the existing AI agent configurations in the repository:
24
25- `.cursorrules` - Cursor AI development rules
26- `CLAUDE.md` - Claude-specific instructions
27- `AGENT.md` - Universal AI agent instructions
28- `.github/copilot-instructions.md` - GitHub Copilot guidelines
29
30## Rule Design Principles
31
32- Keep rules simple, concise, and specific to AI development
33- Use XML tags to group related guidelines
34- Format with bullet points and markdown for clarity
35- Focus on AI-specific patterns rather than generic coding advice
36- Maintain consistency with existing repository patterns
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# Windsurf Rules for Megarepo
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+This directory contains workspace-level rules for Windsurf AI to follow when working on the megarepo AI setup repository.
44
5−## Rules Structure
5+## Rule Files
66
7−The rules are organized into focused files that build upon each other:
7+### Always On Rules (Applied Continuously)
8+- **ai-development-core.md** - Core AI development guidelines and repository context
9+- **security-api-keys.md** - Security guidelines and API key management practices
810
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
11+### Glob Pattern Rules (File-Type Specific)
12+- **typescript-javascript.md** - Applied to `**/*.{ts,tsx,js,jsx}` files
13+- **documentation-standards.md** - Applied to `**/*.md` files
1314
14−## How Cline Uses These Rules
15+### Model Decision Rules (Context-Aware)
16+- **testing-ai-components.md** - Applied when working on testing strategies or test files
1517
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.
18+### Manual Rules (On-Demand)
19+- **ai-optimization.md** - Use `@ai-optimization` for advanced performance optimization
1720
18−## Customization
21+## Usage
1922
20−These rules are tailored specifically for the Megarepo AI setup repository and should be updated as the project evolves. The rules emphasize:
23+Windsurf automatically discovers and applies these rules based on their activation modes. The rules complement the existing AI agent configurations in the repository:
2124
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
25+- `.cursorrules` - Cursor AI development rules
26+- `CLAUDE.md` - Claude-specific instructions
27+- `AGENT.md` - Universal AI agent instructions
28+- `.github/copilot-instructions.md` - GitHub Copilot guidelines
2629
27−## Rules Bank Approach
30+## Rule Design Principles
2831
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.
32+- Keep rules simple, concise, and specific to AI development
33+- Use XML tags to group related guidelines
34+- Format with bullet points and markdown for clarity
35+- Focus on AI-specific patterns rather than generic coding advice
36+- Maintain consistency with existing repository patterns
