Comparison

A · Cline rules · HerringtonDarkholme/megarepo B · Windsurf rules · HerringtonDarkholme/megarepo

What each file covers, counted
Dimension	Only in A	Only in B	Overlap
Sections	14	8	0%
Commands	3	0	0%
Section tags	7	2	0%

What each file covers

Sections

0 shared · 14 only in A · 8 only in B

− Development Guidelines
− Technology Stack
− When Source Code is Added
− Always verify package.json exists first
− Install dependencies with appropriate timeout
− Build with extended timeout for AI projects
− Run tests with adequate time
− Build with reasonable timeout for most projects
− AI Integration Best Practices
− Preferred AI Dependencies
− Code Organization
− Error Handling Pattern
− File Structure Standards
− Development Workflow
+ Windsurf Rules for Megarepo
+ Rule Files
+ Always On Rules (Applied Continuously)
+ Glob Pattern Rules (File-Type Specific)
+ Model Decision Rules (Context-Aware)
+ Manual Rules (On-Demand)
+ Usage
+ Rule Design Principles

Commands

0 shared · 3 only in A · 0 only in B

− npm install
− npm run build
− npm test

Section tags

0 shared · 7 only in A · 2 only in B

− setup
− build
− test
− code-style
− architecture
− dependencies
− agent-behaviour
+ types
+ do-not

Line diff

+25 added−77 removed11 unchanged12.5% identical

HerringtonDarkholme/megarepo · .clinerules/02-development.md

@@ −1 @@

1# Development Guidelines

3## Technology Stack

4This repository is pre-configured for **Node.js/Next.js development** with AI integrations.

6### When Source Code is Added

7Follow these patterns based on existing repository guidelines:

9```bash

10# Always verify package.json exists first

11test -f package.json && echo "Node.js project detected" || echo "No package.json found"

13# Install dependencies with appropriate timeout

14npm install # Allow 10+ minutes for completion

16# Build with extended timeout for AI projects

17npm run build # Allow 60+ minutes - AI projects can have complex builds

19# Run tests with adequate time

20npm test # Allow 30+ minutes for comprehensive test suites

21```

22# Build with reasonable timeout for most projects

23npm run build # Allow 15-30 minutes for most Node.js/Next.js builds with AI integrations

25# Run tests with adequate time

26npm test # Allow 30+ minutes for comprehensive test suites

27## AI Integration Best Practices

29### Preferred AI Dependencies

30When adding AI functionality, use these established packages:

31- `openai` - Official OpenAI API client

32- `@langchain/core` - LangChain framework for AI workflows

33- `@vercel/ai` - Vercel AI SDK for streaming and UI integration

34- `@huggingface/inference` - Hugging Face API client

35- `@anthropic-ai/sdk` - Anthropic Claude API client

37### Code Organization

38- Place AI client configurations in `src/lib/` directory

39- Create reusable AI components in `src/components/ai/`

40- Implement API routes for AI services in `src/app/api/` (Next.js App Router)

41- Define TypeScript types for AI responses in `src/types/`

43### Error Handling Pattern

44```javascript

45// Implement comprehensive error handling for AI services

46try {

47 const response = await aiClient.chat.completions.create({

48 model: "gpt-4",

49 messages: [{ role: "user", content: prompt }]

50 });

51 return response.choices[0].message.content;

52} catch (error) {

53 if (error.code === 'rate_limit_exceeded') {

54 throw new AIRateLimitError('Rate limit exceeded, please try again later');

55 }

56 if (error.code === 'insufficient_quota') {

57 throw new AIQuotaError('API quota exceeded');

58 }

59 throw new AIServiceError(`AI service failed: ${error.message}`);

60}

61```

63## File Structure Standards

64Follow the established minimal structure and expand thoughtfully:

66```

67.

68├── .clinerules/ # Cline AI rules (this directory)

69├── .github/ # GitHub workflows and Copilot instructions

70├── .kiro/steering/ # Kiro AI steering files

71├── .cursorrules # Cursor AI development rules

72├── CLAUDE.md # Claude AI specific configuration

73├── GEMINI.md # Gemini CLI configuration

74├── AGENT.md # Universal AI agent instructions

75├── package.json # Dependencies and scripts (when added)

76├── src/ # Source code (when added)

77│ ├── lib/ # AI clients and utilities

78│ ├── components/ # React components including AI components

79│ ├── app/ # Next.js App Router (pages and API routes)

80│ └── types/ # TypeScript definitions

81└── public/ # Static assets

82```

84## Development Workflow

851. **Before Changes**: Check repository state and existing patterns

862. **During Development**: Follow TypeScript best practices and AI patterns

873. **Testing**: Include AI service mocks and error scenario testing

884. **Documentation**: Update relevant AI configuration files as needed

HerringtonDarkholme/megarepo · .windsurf/rules/README.md

@@ +1 @@

1# Windsurf Rules for Megarepo

3This directory contains workspace-level rules for Windsurf AI to follow when working on the megarepo AI setup repository.

5## Rule Files

7### Always On Rules (Applied Continuously)

8- **ai-development-core.md** - Core AI development guidelines and repository context

9- **security-api-keys.md** - Security guidelines and API key management practices

11### Glob Pattern Rules (File-Type Specific)

12- **typescript-javascript.md** - Applied to `**/*.{ts,tsx,js,jsx}` files

13- **documentation-standards.md** - Applied to `**/*.md` files

15### Model Decision Rules (Context-Aware)

16- **testing-ai-components.md** - Applied when working on testing strategies or test files

18### Manual Rules (On-Demand)

19- **ai-optimization.md** - Use `@ai-optimization` for advanced performance optimization

21## Usage

23Windsurf automatically discovers and applies these rules based on their activation modes. The rules complement the existing AI agent configurations in the repository:

25- `.cursorrules` - Cursor AI development rules

26- `CLAUDE.md` - Claude-specific instructions

27- `AGENT.md` - Universal AI agent instructions

28- `.github/copilot-instructions.md` - GitHub Copilot guidelines

30## Rule Design Principles

32- Keep rules simple, concise, and specific to AI development

33- Use XML tags to group related guidelines

34- Format with bullet points and markdown for clarity

35- Focus on AI-specific patterns rather than generic coding advice

36- Maintain consistency with existing repository patterns

@@ −1 +1 @@

1−# Development Guidelines

1+# Windsurf Rules for Megarepo

3−## Technology Stack

4−This repository is pre-configured for **Node.js/Next.js development** with AI integrations.

3+This directory contains workspace-level rules for Windsurf AI to follow when working on the megarepo AI setup repository.

6−### When Source Code is Added

7−Follow these patterns based on existing repository guidelines:

5+## Rule Files

9−```bash

10−# Always verify package.json exists first

11−test -f package.json && echo "Node.js project detected" || echo "No package.json found"

7+### Always On Rules (Applied Continuously)

8+- **ai-development-core.md** - Core AI development guidelines and repository context

9+- **security-api-keys.md** - Security guidelines and API key management practices

1210

13−# Install dependencies with appropriate timeout

14−npm install # Allow 10+ minutes for completion

11+### Glob Pattern Rules (File-Type Specific)

12+- **typescript-javascript.md** - Applied to `**/*.{ts,tsx,js,jsx}` files

13+- **documentation-standards.md** - Applied to `**/*.md` files

1514

16−# Build with extended timeout for AI projects

17−npm run build # Allow 60+ minutes - AI projects can have complex builds

15+### Model Decision Rules (Context-Aware)

16+- **testing-ai-components.md** - Applied when working on testing strategies or test files

1817

19−# Run tests with adequate time

20−npm test # Allow 30+ minutes for comprehensive test suites

21−```

22−# Build with reasonable timeout for most projects

23−npm run build # Allow 15-30 minutes for most Node.js/Next.js builds with AI integrations

18+### Manual Rules (On-Demand)

19+- **ai-optimization.md** - Use `@ai-optimization` for advanced performance optimization

2420

25−# Run tests with adequate time

26−npm test # Allow 30+ minutes for comprehensive test suites

27−## AI Integration Best Practices

21+## Usage

2822

29−### Preferred AI Dependencies

30−When adding AI functionality, use these established packages:

31−- `openai` - Official OpenAI API client

32−- `@langchain/core` - LangChain framework for AI workflows

33−- `@vercel/ai` - Vercel AI SDK for streaming and UI integration

34−- `@huggingface/inference` - Hugging Face API client

35−- `@anthropic-ai/sdk` - Anthropic Claude API client

23+Windsurf automatically discovers and applies these rules based on their activation modes. The rules complement the existing AI agent configurations in the repository:

3624

37−### Code Organization

38−- Place AI client configurations in `src/lib/` directory

39−- Create reusable AI components in `src/components/ai/`

40−- Implement API routes for AI services in `src/app/api/` (Next.js App Router)

41−- Define TypeScript types for AI responses in `src/types/`

25+- `.cursorrules` - Cursor AI development rules

26+- `CLAUDE.md` - Claude-specific instructions

27+- `AGENT.md` - Universal AI agent instructions

28+- `.github/copilot-instructions.md` - GitHub Copilot guidelines

4229

43−### Error Handling Pattern

44−```javascript

45−// Implement comprehensive error handling for AI services

46−try {

47− const response = await aiClient.chat.completions.create({

48− model: "gpt-4",

49− messages: [{ role: "user", content: prompt }]

50− });

51− return response.choices[0].message.content;

52−} catch (error) {

53− if (error.code === 'rate_limit_exceeded') {

54− throw new AIRateLimitError('Rate limit exceeded, please try again later');

55− }

56− if (error.code === 'insufficient_quota') {

57− throw new AIQuotaError('API quota exceeded');

58− }

59− throw new AIServiceError(`AI service failed: ${error.message}`);

60−}

61−```

30+## Rule Design Principles

6231

63−## File Structure Standards

64−Follow the established minimal structure and expand thoughtfully:

65−

66−```

67−.

68−├── .clinerules/ # Cline AI rules (this directory)

69−├── .github/ # GitHub workflows and Copilot instructions

70−├── .kiro/steering/ # Kiro AI steering files

71−├── .cursorrules # Cursor AI development rules

72−├── CLAUDE.md # Claude AI specific configuration

73−├── GEMINI.md # Gemini CLI configuration

74−├── AGENT.md # Universal AI agent instructions

75−├── package.json # Dependencies and scripts (when added)

76−├── src/ # Source code (when added)

77−│ ├── lib/ # AI clients and utilities

78−│ ├── components/ # React components including AI components

79−│ ├── app/ # Next.js App Router (pages and API routes)

80−│ └── types/ # TypeScript definitions

81−└── public/ # Static assets

82−```

83−

84−## Development Workflow

85−1. **Before Changes**: Check repository state and existing patterns

86−2. **During Development**: Follow TypeScript best practices and AI patterns

87−3. **Testing**: Include AI service mocks and error scenario testing

88−4. **Documentation**: Update relevant AI configuration files as needed

32+- Keep rules simple, concise, and specific to AI development

33+- Use XML tags to group related guidelines

34+- Format with bullet points and markdown for clarity

35+- Focus on AI-specific patterns rather than generic coding advice

36+- Maintain consistency with existing repository patterns