| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 17 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 1 | 33% |
What each file covers
Sections
0 shared · 6 only in A · 17 only in B- − Cline Rules for Megarepo
- − Rules Structure
- − How Cline Uses These Rules
- − Customization
- − Rules Bank Approach
- − Consistency with Other AI Assistants
- + AI Agents Configuration
- + Overview
- + 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
- + Notes
Commands
neither file has anySection tags
1 shared · 1 only in A · 1 only in B- − do-not
- + agent-behaviour
- architecture
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 · 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
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+# AI Agents Configuration
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+## Overview
44
5−## Rules Structure
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.
66
7−The rules are organized into focused files that build upon each other:
7+## Configured AI Agents
88
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
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
1317
14−## How Cline Uses These Rules
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
1526
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.
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
1736
18−## Customization
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
1946
20−These rules are tailored specifically for the Megarepo AI setup repository and should be updated as the project evolves. The rules emphasize:
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
2158
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
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
2671
27−## Rules Bank Approach
72+## Agent Coordination
2873
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.
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
3079
31−## Consistency with Other AI Assistants
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
3286
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`)
87+## Usage Guidelines
3988
40−All configurations share common principles while being optimized for each assistant's specific capabilities.
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
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+
103+When adding new AI agents to this repository:
104+
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
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
