Two files, one repository
HerringtonDarkholme/megarepo ships 8 formats across 23 indexed files. The question worth asking is whether the second one says anything the first does not.
CompareAGENTS.md ↔ CLAUDE.mdAGENTS.md ↔ .cursorrulesAGENTS.md ↔ GEMINI.mdAGENTS.md ↔ Cline rulesAGENTS.md ↔ Copilot instructionsAGENTS.md ↔ Cursor rulesAGENTS.md ↔ Windsurf rulesCLAUDE.md ↔ .cursorrulesCLAUDE.md ↔ GEMINI.mdCLAUDE.md ↔ Cline rulesCLAUDE.md ↔ Copilot instructionsCLAUDE.md ↔ Cursor rulesCLAUDE.md ↔ Windsurf rules.cursorrules ↔ GEMINI.md.cursorrules ↔ Cline rules.cursorrules ↔ Copilot instructions.cursorrules ↔ Cursor rules.cursorrules ↔ Windsurf rulesGEMINI.md ↔ Cline rulesGEMINI.md ↔ Copilot instructionsGEMINI.md ↔ Cursor rulesGEMINI.md ↔ Windsurf rulesCline rules ↔ Copilot instructionsCline rules ↔ Cursor rulesCline rules ↔ Windsurf rulesCopilot instructions ↔ Cursor rulesCopilot instructions ↔ Windsurf rulesCursor rules ↔ Windsurf rules
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 2 | 15 | 27 | 5% |
| Commands | 0 | 0 | 4 | 0% |
| Section tags | 2 | 0 | 8 | 20% |
What each file covers
Sections
2 shared · 15 only in A · 27 only in B- − AI Agents Configuration
- − Configured AI Agents
- − Claude AI
- − GitHub Copilot
- − Windsurf AI
- − Gemini CLI
- − OpenCode
- − Google Antigravity
- − Agent Coordination
- − Shared Principles
- − Repository Structure Awareness
- − Usage Guidelines
- − For Developers
- − For AI Agents
- − Adding New Agents
- + Project: Megarepo - AI Setup Repository
- + Architecture
- + Technology Stack
- + Coding Preferences
- + General Guidelines
- + AI Development Specific
- + Code Style
- + File Organization
- + Instructions for Claude
- + Project Understanding
- + When Adding New Code
- + AI-Specific Considerations
- + Testing Strategy
- + Documentation Requirements
- + Constraints and Limitations
- + Development Workflow
- + Initial Setup (when code is added)
- + Verify package.json exists before running commands
- + Install dependencies if package.json exists
- + Check for environment variables
- + AI Service Integration
- + Check for AI-related packages
- + Validate environment configuration
- + Before Committing
- + Run linting if configured
- + Run tests if configured
- + Check for secrets in staged files
- Overview
- Notes
Commands
0 shared · 0 only in A · 4 only in B- + npm install
- + npm run lint 2>/dev/null || echo "No lint script found"
- + npm run test 2>/dev/null || echo "No test script found"
- + git diff --cached --name-only | xargs grep -l "api.*key\|secret\|token" || echo "No potential secrets found"
Section tags
2 shared · 0 only in A · 8 only in B- + setup
- + test
- + code-style
- + testing-strategy
- + security
- + dependencies
- + do-not
- + docs
- architecture
- agent-behaviour
Line diff
HerringtonDarkholme/megarepo · AGENTS.md
@@ −1 @@
1# AI Agents Configuration
2
3## Overview
4
5This repository includes configuration and instruction files for various AI agents to ensure consistent and effective collaboration in AI development projects. Each agent has specific instructions tailored to their capabilities and use cases within the megarepo ecosystem.
6
7## Configured AI Agents
8
9### Claude AI
10- **Configuration File**: `CLAUDE.md`
11- **Purpose**: Comprehensive AI development assistance, code generation, and project guidance
12- **Capabilities**:
13 - Code review and development
14 - AI-specific architectural guidance
15 - Documentation and testing strategies
16 - Environment setup and configuration
17
18### GitHub Copilot
19- **Configuration File**: `.github/copilot-instructions.md`
20- **Purpose**: IDE-integrated code completion and development assistance
21- **Capabilities**:
22 - Real-time code suggestions
23 - Repository navigation guidance
24 - Build and test workflow instructions
25 - Node.js/Next.js development patterns
26
27### Windsurf AI
28- **Configuration Files**: `.windsurf/rules/` directory with multiple rule files
29- **Purpose**: Intelligent code assistance with contextual rule activation
30- **Capabilities**:
31 - Context-aware rule activation (Always On, Manual, Model Decision, Glob patterns)
32 - AI development best practices and security guidelines
33 - TypeScript/JavaScript specific patterns and optimizations
34 - Testing strategies for AI components and integrations
35 - Documentation standards for AI projects
36
37### Gemini CLI
38- **Configuration File**: `GEMINI.md`
39- **Purpose**: Google's AI-powered command-line interface for interactive development
40- **Capabilities**:
41 - Interactive AI-assisted development sessions
42 - Context-aware code generation and editing
43 - File-based project memory and configuration
44 - Extensible tool system with MCP server support
45 - Project-specific settings and sandboxing options
46
47### OpenCode
48- **Configuration Files**: `opencode.json`, `AGENTS.md` (also supports `CLAUDE.md` as fallback)
49- **Purpose**: Modern AI coding assistant with TUI and web interfaces
50- **Capabilities**:
51 - Terminal-based UI (TUI) and web-based interfaces
52 - Multi-provider model support (Anthropic, OpenAI, etc.)
53 - Custom instructions via AGENTS.md files
54 - Extensible configuration with JSON schema support
55 - Project-specific and global configuration merging
56 - Remote organizational config support
57 - Compatible with Claude Code file conventions
58
59### Google Antigravity
60- **Configuration Files**: `.agent/rules/` and `.agent/skills/` directories
61- **Purpose**: Google's AI-powered development assistant with advanced rule-based activation and reusable skills
62- **Reference**: https://antigravity.google/docs/skills
63- **Capabilities**:
64 - Context-aware rule activation (Always On, Manual, Model Decision, Glob patterns)
65 - Reusable skills for AI development tasks (integration, prompt engineering, evaluation, code review, security)
66 - Workspace-level rules for consistent AI assistance
67 - AI development best practices and security guidelines
68 - File-type specific guidance via glob patterns
69 - Manual activation rules for specialized features
70 - Model-driven context-aware assistance
71
72## Agent Coordination
73
74### Shared Principles
75- **Minimal Changes**: All agents follow surgical, minimal modification approaches
76- **AI-First Design**: Configurations prioritize AI development workflows
77- **Environment Safety**: No API keys or secrets committed to repository
78- **Consistency**: Maintain uniform coding standards and documentation patterns
79
80### Repository Structure Awareness
81All agents are configured to understand:
82- Current minimal state of the repository
83- Node.js/Next.js target architecture
84- MIT license requirements
85- Pre-configured .gitignore patterns
86
87## Usage Guidelines
88
89### For Developers
901. **Review agent-specific files** before engaging with each AI assistant
912. **Follow established patterns** when working with any configured agent
923. **Maintain consistency** across different AI interactions
934. **Update configurations** as the repository evolves
94
95### For AI Agents
96- Always reference the appropriate configuration file for context
97- Coordinate with other agent configurations to maintain consistency
98- Respect the minimal, focused approach established in this repository
99- Update this overview when new agents are added
100
101## Adding New Agents
102
103When adding new AI agents to this repository:
104
1051. **Create agent-specific configuration file** following the established pattern
1062. **Update this AGENTS.md file** to include the new agent
1073. **Ensure compatibility** with existing agent configurations
1084. **Test coordination** between multiple agents if applicable
1095. **Document any special requirements** or limitations
110
111## Notes
112
113- This file serves as a central index for all AI agent configurations
114- Individual agent files contain detailed, agent-specific instructions
115- The repository is designed to evolve from its current minimal state
116- Always refer to `.github/copilot-instructions.md` for workflow details
117- Maintain the minimal, focused approach that characterizes this repository template
HerringtonDarkholme/megarepo · CLAUDE.md
@@ +1 @@
1# Project: Megarepo - AI Setup Repository
2
3## Overview
4Megarepo is a minimal repository template designed for AI-related projects and development. It serves as a foundational setup repository that provides basic configuration files and structure for Node.js/Next.js AI applications. The repository is currently in a minimal state and is intended to be expanded with AI-specific tooling, configurations, and project scaffolding.
5
6## Architecture
7- **Current Structure**: Minimal setup with basic configuration files
8- **Target Architecture**: Node.js/Next.js based AI applications
9- **Key Directories** (when populated):
10 - `src/` - Main source code directory
11 - `src/pages/` - Next.js pages (if Next.js project)
12 - `src/components/` - React components for AI interfaces
13 - `src/utils/` - Utility functions and AI helpers
14 - `public/` - Static assets and files
15- **Configuration Files**:
16 - `.gitignore` - Pre-configured for Node.js/Next.js projects
17 - `LICENSE` - MIT license
18 - `.github/copilot-instructions.md` - Detailed AI agent instructions
19
20## Technology Stack
21- **Frontend**: Next.js, React (intended)
22- **Runtime**: Node.js
23- **Package Manager**: npm
24- **License**: MIT
25- **AI Integrations**: To be determined based on project needs (OpenAI, LangChain, Hugging Face, etc.)
26
27## Coding Preferences
28
29### General Guidelines
30- Follow existing patterns established in the repository
31- Prioritize minimal, surgical changes over large refactors
32- Maintain consistency with the existing file structure
33- Use TypeScript when adding JavaScript code (based on .gitignore patterns)
34
35### AI Development Specific
36- Use environment variables for API keys and sensitive configuration
37- Never commit API keys or secrets to the repository
38- Structure AI-related code in logical, modular components
39- Document AI model dependencies and version requirements
40- Include error handling for AI service failures
41
42### Code Style
43- Follow standard Node.js/Next.js conventions
44- Use meaningful variable and function names, especially for AI-related functionality
45- Include JSDoc comments for complex AI algorithms or integrations
46- Organize imports: external dependencies first, then internal modules
47
48### File Organization
49- Keep configuration files in the root directory
50- Place source code in `src/` directory when added
51- Use clear, descriptive file names
52- Group related functionality together
53
54## Instructions for Claude
55
56### Project Understanding
57- This repository is currently minimal and serves as a template/setup for AI projects
58- No build system or source code exists yet - do not attempt to build, test, or run code
59- The repository is pre-configured for Node.js/Next.js development patterns
60- Focus on the intended AI setup purpose when making recommendations
61
62### When Adding New Code
631. **Always check for existing package.json before running npm commands**
642. **Follow the patterns established in `.github/copilot-instructions.md`**
653. **Set appropriate timeouts for long-running operations** (builds: 60+ minutes, installs: 10+ minutes)
664. **Validate changes don't break existing minimal structure**
67
68### AI-Specific Considerations
69- When adding AI dependencies, verify compatibility with the intended Node.js/Next.js stack
70- Create `.env.example` files to document required environment variables
71- Consider rate limiting and error handling for AI service integrations
72- Document AI model requirements, versions, and expected behavior
73
74### Testing Strategy
75- When source code is added, include tests for AI functionality
76- Test error scenarios (API failures, rate limits, invalid responses)
77- Include integration tests for AI service connections
78- Document how to run tests with mock AI services for CI/CD
79
80### Documentation Requirements
81- Update README.md when adding significant functionality
82- Document AI service setup and configuration steps
83- Include examples of AI integrations and usage
84- Maintain this claude.md file as the project evolves
85
86### Constraints and Limitations
87- Repository is currently minimal - respect this intentional simplicity
88- Do not add unnecessary complexity or dependencies prematurely
89- Maintain compatibility with the existing MIT license
90- Follow the existing .gitignore patterns for Node.js/Next.js projects
91- Respect the established minimal change philosophy outlined in copilot-instructions.md
92
93## Development Workflow
94
95### Initial Setup (when code is added)
96```bash
97# Verify package.json exists before running commands
98test -f package.json && echo "Node.js project detected" || echo "No package.json found"
99
100# Install dependencies if package.json exists
101npm install
102
103# Check for environment variables
104ls .env* || echo "No environment files found"
105```
106
107### AI Service Integration
108```bash
109# Check for AI-related packages
110grep -E "(openai|langchain|tensorflow|pytorch|huggingface)" package.json
111
112# Validate environment configuration
113test -f .env.example && echo "Environment template found" || echo "Create .env.example for required variables"
114```
115
116### Before Committing
117```bash
118# Run linting if configured
119npm run lint 2>/dev/null || echo "No lint script found"
120
121# Run tests if configured
122npm run test 2>/dev/null || echo "No test script found"
123
124# Check for secrets in staged files
125git diff --cached --name-only | xargs grep -l "api.*key\|secret\|token" || echo "No potential secrets found"
126```
127
128## Notes
129- This configuration file should be updated as the repository evolves from its current minimal state
130- The repository is designed to be a foundation for AI projects, so expect significant expansion
131- Always refer to `.github/copilot-instructions.md` for additional context and detailed workflows
132- Maintain the minimal, focused approach that characterizes this repository template
@@ −1 +1 @@
1−# AI Agents Configuration
1+# Project: Megarepo - AI Setup Repository
22
33 ## Overview
4+Megarepo is a minimal repository template designed for AI-related projects and development. It serves as a foundational setup repository that provides basic configuration files and structure for Node.js/Next.js AI applications. The repository is currently in a minimal state and is intended to be expanded with AI-specific tooling, configurations, and project scaffolding.
45
5−This repository includes configuration and instruction files for various AI agents to ensure consistent and effective collaboration in AI development projects. Each agent has specific instructions tailored to their capabilities and use cases within the megarepo ecosystem.
6+## Architecture
7+- **Current Structure**: Minimal setup with basic configuration files
8+- **Target Architecture**: Node.js/Next.js based AI applications
9+- **Key Directories** (when populated):
10+ - `src/` - Main source code directory
11+ - `src/pages/` - Next.js pages (if Next.js project)
12+ - `src/components/` - React components for AI interfaces
13+ - `src/utils/` - Utility functions and AI helpers
14+ - `public/` - Static assets and files
15+- **Configuration Files**:
16+ - `.gitignore` - Pre-configured for Node.js/Next.js projects
17+ - `LICENSE` - MIT license
18+ - `.github/copilot-instructions.md` - Detailed AI agent instructions
619
7−## Configured AI Agents
20+## Technology Stack
21+- **Frontend**: Next.js, React (intended)
22+- **Runtime**: Node.js
23+- **Package Manager**: npm
24+- **License**: MIT
25+- **AI Integrations**: To be determined based on project needs (OpenAI, LangChain, Hugging Face, etc.)
826
9−### Claude AI
10−- **Configuration File**: `CLAUDE.md`
11−- **Purpose**: Comprehensive AI development assistance, code generation, and project guidance
12−- **Capabilities**:
13− - Code review and development
14− - AI-specific architectural guidance
15− - Documentation and testing strategies
16− - Environment setup and configuration
27+## Coding Preferences
1728
18−### GitHub Copilot
19−- **Configuration File**: `.github/copilot-instructions.md`
20−- **Purpose**: IDE-integrated code completion and development assistance
21−- **Capabilities**:
22− - Real-time code suggestions
23− - Repository navigation guidance
24− - Build and test workflow instructions
25− - Node.js/Next.js development patterns
29+### General Guidelines
30+- Follow existing patterns established in the repository
31+- Prioritize minimal, surgical changes over large refactors
32+- Maintain consistency with the existing file structure
33+- Use TypeScript when adding JavaScript code (based on .gitignore patterns)
2634
27−### Windsurf AI
28−- **Configuration Files**: `.windsurf/rules/` directory with multiple rule files
29−- **Purpose**: Intelligent code assistance with contextual rule activation
30−- **Capabilities**:
31− - Context-aware rule activation (Always On, Manual, Model Decision, Glob patterns)
32− - AI development best practices and security guidelines
33− - TypeScript/JavaScript specific patterns and optimizations
34− - Testing strategies for AI components and integrations
35− - Documentation standards for AI projects
35+### AI Development Specific
36+- Use environment variables for API keys and sensitive configuration
37+- Never commit API keys or secrets to the repository
38+- Structure AI-related code in logical, modular components
39+- Document AI model dependencies and version requirements
40+- Include error handling for AI service failures
3641
37−### Gemini CLI
38−- **Configuration File**: `GEMINI.md`
39−- **Purpose**: Google's AI-powered command-line interface for interactive development
40−- **Capabilities**:
41− - Interactive AI-assisted development sessions
42− - Context-aware code generation and editing
43− - File-based project memory and configuration
44− - Extensible tool system with MCP server support
45− - Project-specific settings and sandboxing options
42+### Code Style
43+- Follow standard Node.js/Next.js conventions
44+- Use meaningful variable and function names, especially for AI-related functionality
45+- Include JSDoc comments for complex AI algorithms or integrations
46+- Organize imports: external dependencies first, then internal modules
4647
47−### OpenCode
48−- **Configuration Files**: `opencode.json`, `AGENTS.md` (also supports `CLAUDE.md` as fallback)
49−- **Purpose**: Modern AI coding assistant with TUI and web interfaces
50−- **Capabilities**:
51− - Terminal-based UI (TUI) and web-based interfaces
52− - Multi-provider model support (Anthropic, OpenAI, etc.)
53− - Custom instructions via AGENTS.md files
54− - Extensible configuration with JSON schema support
55− - Project-specific and global configuration merging
56− - Remote organizational config support
57− - Compatible with Claude Code file conventions
48+### File Organization
49+- Keep configuration files in the root directory
50+- Place source code in `src/` directory when added
51+- Use clear, descriptive file names
52+- Group related functionality together
5853
59−### Google Antigravity
60−- **Configuration Files**: `.agent/rules/` and `.agent/skills/` directories
61−- **Purpose**: Google's AI-powered development assistant with advanced rule-based activation and reusable skills
62−- **Reference**: https://antigravity.google/docs/skills
63−- **Capabilities**:
64− - Context-aware rule activation (Always On, Manual, Model Decision, Glob patterns)
65− - Reusable skills for AI development tasks (integration, prompt engineering, evaluation, code review, security)
66− - Workspace-level rules for consistent AI assistance
67− - AI development best practices and security guidelines
68− - File-type specific guidance via glob patterns
69− - Manual activation rules for specialized features
70− - Model-driven context-aware assistance
54+## Instructions for Claude
7155
72−## Agent Coordination
56+### Project Understanding
57+- This repository is currently minimal and serves as a template/setup for AI projects
58+- No build system or source code exists yet - do not attempt to build, test, or run code
59+- The repository is pre-configured for Node.js/Next.js development patterns
60+- Focus on the intended AI setup purpose when making recommendations
7361
74−### Shared Principles
75−- **Minimal Changes**: All agents follow surgical, minimal modification approaches
76−- **AI-First Design**: Configurations prioritize AI development workflows
77−- **Environment Safety**: No API keys or secrets committed to repository
78−- **Consistency**: Maintain uniform coding standards and documentation patterns
62+### When Adding New Code
63+1. **Always check for existing package.json before running npm commands**
64+2. **Follow the patterns established in `.github/copilot-instructions.md`**
65+3. **Set appropriate timeouts for long-running operations** (builds: 60+ minutes, installs: 10+ minutes)
66+4. **Validate changes don't break existing minimal structure**
7967
80−### Repository Structure Awareness
81−All agents are configured to understand:
82−- Current minimal state of the repository
83−- Node.js/Next.js target architecture
84−- MIT license requirements
85−- Pre-configured .gitignore patterns
68+### AI-Specific Considerations
69+- When adding AI dependencies, verify compatibility with the intended Node.js/Next.js stack
70+- Create `.env.example` files to document required environment variables
71+- Consider rate limiting and error handling for AI service integrations
72+- Document AI model requirements, versions, and expected behavior
8673
87−## Usage Guidelines
74+### Testing Strategy
75+- When source code is added, include tests for AI functionality
76+- Test error scenarios (API failures, rate limits, invalid responses)
77+- Include integration tests for AI service connections
78+- Document how to run tests with mock AI services for CI/CD
8879
89−### For Developers
90−1. **Review agent-specific files** before engaging with each AI assistant
91−2. **Follow established patterns** when working with any configured agent
92−3. **Maintain consistency** across different AI interactions
93−4. **Update configurations** as the repository evolves
80+### Documentation Requirements
81+- Update README.md when adding significant functionality
82+- Document AI service setup and configuration steps
83+- Include examples of AI integrations and usage
84+- Maintain this claude.md file as the project evolves
9485
95−### For AI Agents
96−- Always reference the appropriate configuration file for context
97−- Coordinate with other agent configurations to maintain consistency
98−- Respect the minimal, focused approach established in this repository
99−- Update this overview when new agents are added
86+### Constraints and Limitations
87+- Repository is currently minimal - respect this intentional simplicity
88+- Do not add unnecessary complexity or dependencies prematurely
89+- Maintain compatibility with the existing MIT license
90+- Follow the existing .gitignore patterns for Node.js/Next.js projects
91+- Respect the established minimal change philosophy outlined in copilot-instructions.md
10092
101−## Adding New Agents
93+## Development Workflow
10294
103−When adding new AI agents to this repository:
95+### Initial Setup (when code is added)
96+```bash
97+# Verify package.json exists before running commands
98+test -f package.json && echo "Node.js project detected" || echo "No package.json found"
10499
105−1. **Create agent-specific configuration file** following the established pattern
106−2. **Update this AGENTS.md file** to include the new agent
107−3. **Ensure compatibility** with existing agent configurations
108−4. **Test coordination** between multiple agents if applicable
109−5. **Document any special requirements** or limitations
100+# Install dependencies if package.json exists
101+npm install
110102
111−## Notes
103+# Check for environment variables
104+ls .env* || echo "No environment files found"
105+```
112106
113−- This file serves as a central index for all AI agent configurations
114−- Individual agent files contain detailed, agent-specific instructions
115−- The repository is designed to evolve from its current minimal state
116−- Always refer to `.github/copilot-instructions.md` for workflow details
107+### AI Service Integration
108+```bash
109+# Check for AI-related packages
110+grep -E "(openai|langchain|tensorflow|pytorch|huggingface)" package.json
111+
112+# Validate environment configuration
113+test -f .env.example && echo "Environment template found" || echo "Create .env.example for required variables"
114+```
115+
116+### Before Committing
117+```bash
118+# Run linting if configured
119+npm run lint 2>/dev/null || echo "No lint script found"
120+
121+# Run tests if configured
122+npm run test 2>/dev/null || echo "No test script found"
123+
124+# Check for secrets in staged files
125+git diff --cached --name-only | xargs grep -l "api.*key\|secret\|token" || echo "No potential secrets found"
126+```
127+
128+## Notes
129+- This configuration file should be updated as the repository evolves from its current minimal state
130+- The repository is designed to be a foundation for AI projects, so expect significant expansion
131+- Always refer to `.github/copilot-instructions.md` for additional context and detailed workflows
117132 - Maintain the minimal, focused approach that characterizes this repository template
