| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 14 | 10 | 0% |
| Commands | 0 | 3 | 0 | 0% |
| Section tags | 2 | 5 | 5 | 17% |
What each file covers
Sections
0 shared · 14 only in A · 10 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
- + Code Quality Standards
- + Core Development Principles
- + 1. TypeScript Guidelines
- + 2. TypeScript Patterns
- + 3. React Best Practices
- + 4. Testing Patterns
- + 5. Error Handling Standards
- + 6. Documentation Requirements
- + 7. Code Style Guidelines
- + 8. API Development Standards
Commands
0 shared · 3 only in A · 0 only in B- − npm install
- − npm run build
- − npm test
Section tags
2 shared · 5 only in A · 5 only in B- − setup
- − build
- − architecture
- − dependencies
- − agent-behaviour
- + types
- + testing-strategy
- + git-pr
- + api
- + docs
- test
- code-style
Line diff
HerringtonDarkholme/megarepo · .clinerules/02-development.md
@@ −1 @@
1# Development Guidelines
2
3## Technology Stack
4This repository is pre-configured for **Node.js/Next.js development** with AI integrations.
5
6### When Source Code is Added
7Follow these patterns based on existing repository guidelines:
8
9```bash
10# Always verify package.json exists first
11test -f package.json && echo "Node.js project detected" || echo "No package.json found"
12
13# Install dependencies with appropriate timeout
14npm install # Allow 10+ minutes for completion
15
16# Build with extended timeout for AI projects
17npm run build # Allow 60+ minutes - AI projects can have complex builds
18
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
24
25# Run tests with adequate time
26npm test # Allow 30+ minutes for comprehensive test suites
27## AI Integration Best Practices
28
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
36
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/`
42
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```
62
63## File Structure Standards
64Follow 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
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 · .cursor/rules/code-quality.mdc
@@ +1 @@
1---
2description: "Code quality standards including TypeScript, testing, and formatting guidelines"
3globs: ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "**/*.test.*", "**/*.spec.*"]
4alwaysApply: true
5---
6
7# Code Quality Standards
8
9Comprehensive code quality guidelines for the AI setup repository.
10
11## Core Development Principles
12
13### 1. TypeScript Guidelines
14- Use strict type checking
15- Define interfaces for all AI API responses
16- Use union types for AI model selections
17- Implement proper error type definitions
18
19### 2. TypeScript Patterns
20```typescript
21// Define interfaces for AI responses
22interface AIResponse {
23 content: string;
24 model: string;
25 usage: {
26 prompt_tokens: number;
27 completion_tokens: number;
28 };
29}
30
31// Use union types for model selection
32type AIModel = 'gpt-4' | 'gpt-3.5-turbo' | 'claude-3' | 'claude-2';
33```
34
35### 3. React Best Practices
36- Use functional components with hooks
37- Implement proper cleanup for AI subscriptions
38- Use React.memo for expensive AI-powered components
39- Handle loading and error states consistently
40
41### 4. Testing Patterns
42```javascript
43// Example AI component test pattern
44describe('AI Chat Component', () => {
45 it('handles API errors gracefully', async () => {
46 // Mock AI service failure
47 mockAIService.mockRejectedValue(new Error('API Error'));
48
49 render(<ChatComponent />);
50
51 // Test error handling and user feedback
52 expect(screen.getByText(/error/i)).toBeInTheDocument();
53 });
54});
55```
56
57### 5. Error Handling Standards
58- Write comprehensive error handling and logging
59- Implement proper error boundaries for React components
60- Use custom error types for different failure scenarios
61- Provide meaningful error messages to users
62
63### 6. Documentation Requirements
64- Document all AI-related functions and components
65- Include usage examples for AI integrations
66- Explain prompt engineering decisions
67- Document environment setup requirements
68
69### 7. Code Style Guidelines
70- Write clean, readable, and well-documented code
71- Follow established linting and formatting rules
72- Write meaningful commit messages and documentation
73- Use descriptive variable and function names
74
75### 8. API Development Standards
76- Follow RESTful principles for AI service endpoints
77- Implement proper rate limiting and authentication
78- Use middleware for common AI service operations
79- Document API endpoints with clear examples
@@ −1 +1 @@
1−# Development Guidelines
1+---
2+description: "Code quality standards including TypeScript, testing, and formatting guidelines"
3+globs: ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "**/*.test.*", "**/*.spec.*"]
4+alwaysApply: true
5+---
26
3−## Technology Stack
4−This repository is pre-configured for **Node.js/Next.js development** with AI integrations.
7+# Code Quality Standards
58
6−### When Source Code is Added
7−Follow these patterns based on existing repository guidelines:
9+Comprehensive code quality guidelines for the AI setup repository.
810
9−```bash
10−# Always verify package.json exists first
11−test -f package.json && echo "Node.js project detected" || echo "No package.json found"
11+## Core Development Principles
1212
13−# Install dependencies with appropriate timeout
14−npm install # Allow 10+ minutes for completion
13+### 1. TypeScript Guidelines
14+- Use strict type checking
15+- Define interfaces for all AI API responses
16+- Use union types for AI model selections
17+- Implement proper error type definitions
1518
16−# Build with extended timeout for AI projects
17−npm run build # Allow 60+ minutes - AI projects can have complex builds
19+### 2. TypeScript Patterns
20+```typescript
21+// Define interfaces for AI responses
22+interface AIResponse {
23+ content: string;
24+ model: string;
25+ usage: {
26+ prompt_tokens: number;
27+ completion_tokens: number;
28+ };
29+}
1830
19−# Run tests with adequate time
20−npm test # Allow 30+ minutes for comprehensive test suites
31+// Use union types for model selection
32+type AIModel = 'gpt-4' | 'gpt-3.5-turbo' | 'claude-3' | 'claude-2';
2133 ```
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
2434
25−# Run tests with adequate time
26−npm test # Allow 30+ minutes for comprehensive test suites
27−## AI Integration Best Practices
35+### 3. React Best Practices
36+- Use functional components with hooks
37+- Implement proper cleanup for AI subscriptions
38+- Use React.memo for expensive AI-powered components
39+- Handle loading and error states consistently
2840
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
36−
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/`
42−
43−### Error Handling Pattern
41+### 4. Testing Patterns
4442 ```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 }]
43+// Example AI component test pattern
44+describe('AI Chat Component', () => {
45+ it('handles API errors gracefully', async () => {
46+ // Mock AI service failure
47+ mockAIService.mockRejectedValue(new Error('API Error'));
48+
49+ render(<ChatComponent />);
50+
51+ // Test error handling and user feedback
52+ expect(screen.getByText(/error/i)).toBeInTheDocument();
5053 });
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−}
54+});
6155 ```
6256
63−## File Structure Standards
64−Follow the established minimal structure and expand thoughtfully:
57+### 5. Error Handling Standards
58+- Write comprehensive error handling and logging
59+- Implement proper error boundaries for React components
60+- Use custom error types for different failure scenarios
61+- Provide meaningful error messages to users
6562
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−```
63+### 6. Documentation Requirements
64+- Document all AI-related functions and components
65+- Include usage examples for AI integrations
66+- Explain prompt engineering decisions
67+- Document environment setup requirements
8368
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
69+### 7. Code Style Guidelines
70+- Write clean, readable, and well-documented code
71+- Follow established linting and formatting rules
72+- Write meaningful commit messages and documentation
73+- Use descriptive variable and function names
74+
75+### 8. API Development Standards
76+- Follow RESTful principles for AI service endpoints
77+- Implement proper rate limiting and authentication
78+- Use middleware for common AI service operations
79+- Document API endpoints with clear examples
