| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 2 | 25% |
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
- + Security and API Key Management
Commands
neither file has anySection tags
1 shared · 1 only in A · 2 only in B- − architecture
- + security
- + api
- 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/security-api-keys.md
@@ +1 @@
1# Security and API Key Management
2
3**Activation Mode**: Always On
4
5<security_guidelines>
6- NEVER commit API keys, secrets, or credentials to version control
7- Always use environment variables for sensitive data and AI service keys
8- Create .env.example files to document required environment variables
9- Implement proper API key rotation and management patterns
10- Use secure storage solutions for production deployments
11</security_guidelines>
12
13<data_privacy>
14- Avoid sending sensitive user data to AI services without proper consent
15- Implement data anonymization where possible for AI training and processing
16- Follow GDPR and privacy regulations in AI data handling
17- Document data usage and retention policies for AI services
18- Validate all inputs before sending to AI services to prevent injection attacks
19</data_privacy>
20
21<api_security>
22- Implement proper CORS settings for AI API endpoints
23- Use HTTPS for all AI API communications and service integrations
24- Implement proper rate limiting and authentication for AI endpoints
25- Regularly audit and rotate API keys and secrets
26- Use middleware for common AI service authentication operations
27</api_security>
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# Security and API Key Management
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**: Always On
44
5−## Rules Structure
5+<security_guidelines>
6+- NEVER commit API keys, secrets, or credentials to version control
7+- Always use environment variables for sensitive data and AI service keys
8+- Create .env.example files to document required environment variables
9+- Implement proper API key rotation and management patterns
10+- Use secure storage solutions for production deployments
11+</security_guidelines>
612
7−The rules are organized into focused files that build upon each other:
13+<data_privacy>
14+- Avoid sending sensitive user data to AI services without proper consent
15+- Implement data anonymization where possible for AI training and processing
16+- Follow GDPR and privacy regulations in AI data handling
17+- Document data usage and retention policies for AI services
18+- Validate all inputs before sending to AI services to prevent injection attacks
19+</data_privacy>
820
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
13−
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.
21+<api_security>
22+- Implement proper CORS settings for AI API endpoints
23+- Use HTTPS for all AI API communications and service integrations
24+- Implement proper rate limiting and authentication for AI endpoints
25+- Regularly audit and rotate API keys and secrets
26+- Use middleware for common AI service authentication operations
27+</api_security>
