| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 1 | 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
- + Documentation Standards
Commands
neither file has anySection tags
0 shared · 2 only in A · 1 only in B- − architecture
- − do-not
- + docs
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/documentation-standards.md
@@ +1 @@
1# Documentation Standards
2
3**Activation Mode**: Glob
4**Pattern**: `**/*.md`
5
6<documentation_requirements>
7- Update README.md when adding significant AI functionality or features
8- Document AI service setup and configuration steps clearly
9- Include examples of AI integrations and usage patterns
10- Maintain consistency with existing documentation style and structure
11- Document environment variable requirements for AI services
12</documentation_requirements>
13
14<ai_documentation_specifics>
15- Document all AI model dependencies and version requirements
16- Include prompt engineering decisions and template explanations
17- Explain AI service rate limiting and quota management approaches
18- Provide troubleshooting guides for common AI integration issues
19- Document performance considerations and optimization strategies
20</ai_documentation_specifics>
21
22<code_documentation>
23- Include JSDoc comments for AI-related functions and complex algorithms
24- Document API endpoints with clear request/response examples
25- Explain AI service authentication and configuration patterns
26- Include usage examples for AI utility functions and client libraries
27- Document data flow and processing pipelines for AI features
28</code_documentation>
29
30<maintenance_guidelines>
31- Keep documentation up to date with AI service API changes
32- Document breaking changes and migration guides for AI integrations
33- Include version compatibility information for AI service SDKs
34- Maintain examples that work with current AI service APIs
35- Document known limitations and workarounds for AI services
36</maintenance_guidelines>
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# Documentation Standards
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**: Glob
4+**Pattern**: `**/*.md`
45
5−## Rules Structure
6+<documentation_requirements>
7+- Update README.md when adding significant AI functionality or features
8+- Document AI service setup and configuration steps clearly
9+- Include examples of AI integrations and usage patterns
10+- Maintain consistency with existing documentation style and structure
11+- Document environment variable requirements for AI services
12+</documentation_requirements>
613
7−The rules are organized into focused files that build upon each other:
14+<ai_documentation_specifics>
15+- Document all AI model dependencies and version requirements
16+- Include prompt engineering decisions and template explanations
17+- Explain AI service rate limiting and quota management approaches
18+- Provide troubleshooting guides for common AI integration issues
19+- Document performance considerations and optimization strategies
20+</ai_documentation_specifics>
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+<code_documentation>
23+- Include JSDoc comments for AI-related functions and complex algorithms
24+- Document API endpoints with clear request/response examples
25+- Explain AI service authentication and configuration patterns
26+- Include usage examples for AI utility functions and client libraries
27+- Document data flow and processing pipelines for AI features
28+</code_documentation>
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+<maintenance_guidelines>
31+- Keep documentation up to date with AI service API changes
32+- Document breaking changes and migration guides for AI integrations
33+- Include version compatibility information for AI service SDKs
34+- Maintain examples that work with current AI service APIs
35+- Document known limitations and workarounds for AI services
36+</maintenance_guidelines>
