| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 11 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 1 | 1 | 2 | 25% |
What each file covers
Sections
0 shared · 6 only in A · 11 only in B- − Cline Rules for Megarepo
- − Rules Structure
- − How Cline Uses These Rules
- − Customization
- − Rules Bank Approach
- − Consistency with Other AI Assistants
- + Project Structure & Architecture
- + Expected Project Structure
- + Key Directory Guidelines
- + Source Code Organization
- + Component Organization
- + Utility Organization
- + Architectural Principles
- + 1. Node.js/Next.js Development
- + 2. File Naming Conventions
- + 3. Import Organization
- + 4. Configuration Management
Commands
neither file has anySection tags
1 shared · 1 only in A · 2 only in B- − do-not
- + code-style
- + ui
- 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 · .cursor/rules/project-structure.mdc
@@ +1 @@
1---
2description: "File organization and architectural patterns for the AI setup repository"
3globs: ["src/**/*", "app/**/*", "public/**/*", "docs/**/*"]
4alwaysApply: false
5---
6
7# Project Structure & Architecture
8
9Guidelines for organizing files and structuring the AI setup repository.
10
11## Expected Project Structure
12
13```
14.
15├── README.md # Project documentation
16├── LICENSE # MIT license
17├── .gitignore # Node.js/Next.js patterns
18├── .cursor/rules/ # Cursor project rules
19├── .env.example # Environment variable template
20├── package.json # Dependencies and scripts
21├── next.config.js # Next.js configuration
22├── tsconfig.json # TypeScript configuration
23├── src/
24│ ├── app/ # Next.js app directory
25│ ├── components/ # React components
26│ ├── lib/ # Utility functions and AI clients
27│ ├── types/ # TypeScript type definitions
28│ └── utils/ # Helper functions
29├── public/ # Static assets
30└── docs/ # Additional documentation
31```
32
33## Key Directory Guidelines
34
35### Source Code Organization
36- `src/lib/` - Place AI client configurations and utilities here
37- `src/components/` - Reusable UI components, including AI-powered components
38- `src/app/api/` - API routes for AI services and integrations
39- `src/types/` - TypeScript definitions for AI responses and data models
40
41### Component Organization
42- Group related components in feature-specific subdirectories
43- Keep component styles and tests near the component
44- Use index files for clean imports
45
46### Utility Organization
47- Group related utilities in feature-specific directories
48- Separate AI-specific utilities from general utilities
49- Implement consistent naming patterns
50
51## Architectural Principles
52
53### 1. Node.js/Next.js Development
54- Follow Next.js 13+ App Router patterns when applicable
55- Use modern ES6+ JavaScript/TypeScript features
56- Implement proper async/await patterns for AI API calls
57- Use React Server Components where appropriate
58- Optimize for both development and production environments
59
60### 2. File Naming Conventions
61- Use camelCase for JavaScript/TypeScript files
62- Use PascalCase for React component files
63- Use kebab-case for API routes and static files
64- Use descriptive names that indicate purpose
65
66### 3. Import Organization
67- Group imports by type (external, internal, relative)
68- Use absolute imports with path aliases when configured
69- Keep imports organized and clean
70
71### 4. Configuration Management
72- Keep all configuration files in the project root
73- Use TypeScript for configuration files when possible
74- Document configuration options and their purposes
@@ −1 +1 @@
1−# Cline Rules for Megarepo
1+---
2+description: "File organization and architectural patterns for the AI setup repository"
3+globs: ["src/**/*", "app/**/*", "public/**/*", "docs/**/*"]
4+alwaysApply: false
5+---
26
3−This directory contains Cline Rules that provide system-level guidance for the Cline AI assistant when working on this AI setup repository.
7+# Project Structure & Architecture
48
5−## Rules Structure
9+Guidelines for organizing files and structuring the AI setup repository.
610
7−The rules are organized into focused files that build upon each other:
11+## Expected Project Structure
812
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+.
15+├── README.md # Project documentation
16+├── LICENSE # MIT license
17+├── .gitignore # Node.js/Next.js patterns
18+├── .cursor/rules/ # Cursor project rules
19+├── .env.example # Environment variable template
20+├── package.json # Dependencies and scripts
21+├── next.config.js # Next.js configuration
22+├── tsconfig.json # TypeScript configuration
23+├── src/
24+│ ├── app/ # Next.js app directory
25+│ ├── components/ # React components
26+│ ├── lib/ # Utility functions and AI clients
27+│ ├── types/ # TypeScript type definitions
28+│ └── utils/ # Helper functions
29+├── public/ # Static assets
30+└── docs/ # Additional documentation
31+```
1332
14−## How Cline Uses These Rules
33+## Key Directory Guidelines
1534
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.
35+### Source Code Organization
36+- `src/lib/` - Place AI client configurations and utilities here
37+- `src/components/` - Reusable UI components, including AI-powered components
38+- `src/app/api/` - API routes for AI services and integrations
39+- `src/types/` - TypeScript definitions for AI responses and data models
1740
18−## Customization
41+### Component Organization
42+- Group related components in feature-specific subdirectories
43+- Keep component styles and tests near the component
44+- Use index files for clean imports
1945
20−These rules are tailored specifically for the Megarepo AI setup repository and should be updated as the project evolves. The rules emphasize:
46+### Utility Organization
47+- Group related utilities in feature-specific directories
48+- Separate AI-specific utilities from general utilities
49+- Implement consistent naming patterns
2150
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
51+## Architectural Principles
2652
27−## Rules Bank Approach
53+### 1. Node.js/Next.js Development
54+- Follow Next.js 13+ App Router patterns when applicable
55+- Use modern ES6+ JavaScript/TypeScript features
56+- Implement proper async/await patterns for AI API calls
57+- Use React Server Components where appropriate
58+- Optimize for both development and production environments
2859
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.
60+### 2. File Naming Conventions
61+- Use camelCase for JavaScript/TypeScript files
62+- Use PascalCase for React component files
63+- Use kebab-case for API routes and static files
64+- Use descriptive names that indicate purpose
3065
31−## Consistency with Other AI Assistants
66+### 3. Import Organization
67+- Group imports by type (external, internal, relative)
68+- Use absolute imports with path aliases when configured
69+- Keep imports organized and clean
3270
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.
71+### 4. Configuration Management
72+- Keep all configuration files in the project root
73+- Use TypeScript for configuration files when possible
74+- Document configuration options and their purposes
