| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 41 | 28 | 1% |
| Commands | 1 | 10 | 3 | 7% |
| Section tags | 7 | 4 | 3 | 50% |
What each file covers
Sections
1 shared · 41 only in A · 28 only in B- − Megarepo - AI Setup Repository
- − Repository Overview
- − Current Repository State
- − Working Effectively
- − Initial Repository Exploration
- − Always start by understanding the current repository state
- − When Source Code is Added
- − Check for package.json first
- − If package.json exists, install dependencies
- − NEVER CANCEL: npm install typically takes 2-5 minutes. Set timeout to 10+ minutes.
- − Common build commands (verify these exist in package.json first)
- − NEVER CANCEL: Build may take 5-45 minutes depending on project size. Set timeout to 60+ minutes.
- − Common test commands
- − NEVER CANCEL: Tests may take 5-15 minutes. Set timeout to 30+ minutes.
- − Common development server
- − Check for linting configuration
- − Run formatting if configured
- − Run type checking if TypeScript
- − Repository Structure Expectations
- − Validation Requirements
- − Before Making Changes
- − After Making Changes
- − Common Commands Reference
- − Repository Information
- − View current files
- − Check git status
- − View repository structure
- − When Package.json Exists
- − View available scripts
- − Install dependencies
- − TIMEOUT: 10+ minutes
- − Common development commands (check package.json first)
- − File Locations and Navigation
- − Current Key Files
- − Expected Important Locations (when populated)
- − AI Development Guidelines
- − Troubleshooting
- − Repository Appears Empty
- − Build Failures
- − Development Server Issues
- − Critical Reminders
- + Project: Megarepo - AI Setup Repository
- + Overview
- + 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 tests if configured
- + Check for secrets in staged files
- + Notes
- Run linting if configured
Commands
1 shared · 10 only in A · 3 only in B- − git status
- − npm run build
- − npm test
- − npm run dev
- − npm run lint
- − npm run format
- − npm run type-check
- − npm run start
- − npm run test
- − git branch -a
- + 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"
- npm install
Section tags
7 shared · 4 only in A · 3 only in B- − build
- − lint-format
- − types
- − git-pr
- + code-style
- + testing-strategy
- + docs
- setup
- test
- architecture
- security
- dependencies
- do-not
- agent-behaviour
Line diff
HerringtonDarkholme/megarepo · .github/copilot-instructions.md
@@ −1 @@
1# Megarepo - AI Setup Repository
2
3**ALWAYS follow these instructions first and only fallback to additional search and context gathering if the information here is incomplete or found to be in error.**
4
5## Repository Overview
6
7Megarepo is currently a minimal repository template designed for AI-related projects. The repository contains basic setup files and is configured for Node.js/Next.js development based on the .gitignore patterns.
8
9## Current Repository State
10
11**IMPORTANT**: This repository is currently in a minimal state with only basic setup files:
12- README.md (basic project description)
13- LICENSE (MIT license)
14- .gitignore (configured for Node.js/Next.js projects)
15
16**DO NOT attempt to build, test, or run code** - there is no source code or build system present yet.
17
18## Working Effectively
19
20### Initial Repository Exploration
21```bash
22# Always start by understanding the current repository state
23ls -la
24git status
25find . -type f -name "*.json" -o -name "*.js" -o -name "*.ts" -o -name "*.md"
26```
27
28### When Source Code is Added
29
30The repository is pre-configured for Node.js/Next.js development. When source code is added, follow these patterns:
31
32#### Node.js/Next.js Project Setup
33```bash
34# Check for package.json first
35ls package.json
36
37# If package.json exists, install dependencies
38npm install
39# NEVER CANCEL: npm install typically takes 2-5 minutes. Set timeout to 10+ minutes.
40
41# Common build commands (verify these exist in package.json first)
42npm run build
43# NEVER CANCEL: Build may take 5-45 minutes depending on project size. Set timeout to 60+ minutes.
44
45# Common test commands
46npm test
47# NEVER CANCEL: Tests may take 5-15 minutes. Set timeout to 30+ minutes.
48
49# Common development server
50npm run dev
51```
52
53#### Pre-commit Validation
54When source code exists, always run these before committing:
55```bash
56# Check for linting configuration
57ls .eslintrc* eslint.config.* .prettierrc*
58
59# Run linting if configured
60npm run lint
61
62# Run formatting if configured
63npm run format
64
65# Run type checking if TypeScript
66npm run type-check
67```
68
69## Repository Structure Expectations
70
71Based on the .gitignore configuration, expect the following when the repository is populated:
72
73```
74.
75├── README.md # Project documentation
76├── LICENSE # MIT license
77├── .gitignore # Node.js/Next.js ignore patterns
78├── package.json # Node.js dependencies and scripts
79├── package-lock.json # Dependency lockfile
80├── next.config.js # Next.js configuration (if Next.js)
81├── tsconfig.json # TypeScript configuration (if TypeScript)
82├── .eslintrc.* # ESLint configuration
83├── .prettierrc # Prettier configuration
84├── src/ # Source code directory
85│ ├── pages/ # Next.js pages (if Next.js)
86│ ├── components/ # React components
87│ └── utils/ # Utility functions
88├── public/ # Static assets
89├── .next/ # Next.js build output (ignored)
90├── build/ # Build output (ignored)
91└── node_modules/ # Dependencies (ignored)
92```
93
94## Validation Requirements
95
96### Before Making Changes
971. **Always check current repository state first**:
98 ```bash
99 git status
100 ls -la
101 cat package.json # Only if it exists
102 ```
103
1042. **Verify build system exists before attempting builds**:
105 ```bash
106 # Check for package.json before running npm commands
107 test -f package.json && echo "Node.js project detected" || echo "No package.json found"
108 ```
109
110### After Making Changes
1111. **When source code is present, always validate**:
112 ```bash
113 # Install dependencies if package.json exists
114 test -f package.json && npm install
115
116 # Build if build script exists
117 test -f package.json && npm run build
118
119 # Test if test script exists
120 test -f package.json && npm test
121
122 # Lint if lint script exists
123 test -f package.json && npm run lint
124 ```
125
1262. **Manual validation scenarios when application exists**:
127 - Start the development server and verify it loads
128 - Test basic functionality by navigating through the application
129 - Verify any API endpoints respond correctly
130 - Check console for errors
131
132## Common Commands Reference
133
134### Repository Information
135```bash
136# View current files
137ls -la
138
139# Check git status
140git status
141
142# View repository structure
143tree . -a -I 'node_modules|.git' # If tree is available (use -a to show hidden files)
144find . -type f -not -path "./.git/*" -not -path "./node_modules/*" | sort
145```
146
147### When Package.json Exists
148```bash
149# View available scripts
150cat package.json | grep -A 20 '"scripts"'
151
152# Install dependencies
153npm install
154# TIMEOUT: 10+ minutes
155
156# Common development commands (check package.json first)
157npm run dev # Development server
158npm run build # Production build
159npm run start # Start production server
160npm run test # Run tests
161npm run lint # Run linter
162npm run format # Format code
163```
164
165## File Locations and Navigation
166
167### Current Key Files
168- `/README.md` - Project overview and setup instructions
169- `/LICENSE` - MIT license terms
170- `/.gitignore` - Git ignore patterns (Node.js/Next.js focused)
171
172### Expected Important Locations (when populated)
173- `/src/` - Main source code directory
174- `/src/pages/` - Next.js pages (if Next.js project)
175- `/src/components/` - React components
176- `/public/` - Static assets and files
177- `/package.json` - Project configuration and dependencies
178- `/next.config.js` - Next.js configuration
179- `/tsconfig.json` - TypeScript configuration
180
181## AI Development Guidelines
182
183Since this is an AI setup repository:
184
1851. **Always verify AI-related dependencies** when they are added:
186 ```bash
187 # Common AI packages to look for
188 grep -E "(openai|langchain|tensorflow|pytorch|huggingface)" package.json
189 ```
190
1912. **Environment variables for AI services**:
192 ```bash
193 # Check for environment configuration
194 ls .env* || echo "No environment files found"
195 ```
196
1973. **API key management**:
198 - Never commit API keys
199 - Always use environment variables
200 - Check .env.example for required variables
201
202## Troubleshooting
203
204### Repository Appears Empty
205- This is expected in the current state
206- Check git branch: `git branch -a`
207- Look for other branches that might contain code
208
209### Build Failures
210- First verify package.json exists: `ls package.json`
211- Clear dependencies and reinstall: `rm -rf node_modules package-lock.json && npm install`
212- Check Node.js version compatibility in package.json
213
214### Development Server Issues
215- Verify port availability (typically 3000 for Next.js)
216- Check for environment variable requirements
217- Review console output for specific error messages
218
219## Critical Reminders
220
221- **NEVER CANCEL builds or long-running commands** - they may take 45+ minutes
222- **ALWAYS validate commands work** before assuming functionality exists
223- **CHECK for package.json** before running npm commands
224- **SET APPROPRIATE TIMEOUTS** - builds: 60+ minutes, tests: 30+ minutes
225- **VERIFY repository state** before attempting any operations
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−# Megarepo - AI Setup Repository
1+# Project: Megarepo - AI Setup Repository
22
3−**ALWAYS follow these instructions first and only fallback to additional search and context gathering if the information here is incomplete or found to be in error.**
3+## 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−## Repository Overview
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−Megarepo is currently a minimal repository template designed for AI-related projects. The repository contains basic setup files and is configured for Node.js/Next.js development based on the .gitignore patterns.
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−## Current Repository State
27+## Coding Preferences
1028
11−**IMPORTANT**: This repository is currently in a minimal state with only basic setup files:
12−- README.md (basic project description)
13−- LICENSE (MIT license)
14−- .gitignore (configured for Node.js/Next.js projects)
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)
1534
16−**DO NOT attempt to build, test, or run code** - there is no source code or build system present yet.
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
1741
18−## Working Effectively
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
1947
20−### Initial Repository Exploration
21−```bash
22−# Always start by understanding the current repository state
23−ls -la
24−git status
25−find . -type f -name "*.json" -o -name "*.js" -o -name "*.ts" -o -name "*.md"
26−```
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
2753
28−### When Source Code is Added
54+## Instructions for Claude
2955
30−The repository is pre-configured for Node.js/Next.js development. When source code is added, follow these patterns:
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
3161
32−#### Node.js/Next.js Project Setup
33−```bash
34−# Check for package.json first
35−ls package.json
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**
3667
37−# If package.json exists, install dependencies
38−npm install
39−# NEVER CANCEL: npm install typically takes 2-5 minutes. Set timeout to 10+ minutes.
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
4073
41−# Common build commands (verify these exist in package.json first)
42−npm run build
43−# NEVER CANCEL: Build may take 5-45 minutes depending on project size. Set timeout to 60+ minutes.
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
4479
45−# Common test commands
46−npm test
47−# NEVER CANCEL: Tests may take 5-15 minutes. Set timeout to 30+ minutes.
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
4885
49−# Common development server
50−npm run dev
51−```
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
5292
53−#### Pre-commit Validation
54−When source code exists, always run these before committing:
93+## Development Workflow
94+
95+### Initial Setup (when code is added)
5596 ```bash
56−# Check for linting configuration
57−ls .eslintrc* eslint.config.* .prettierrc*
97+# Verify package.json exists before running commands
98+test -f package.json && echo "Node.js project detected" || echo "No package.json found"
5899
59−# Run linting if configured
60−npm run lint
100+# Install dependencies if package.json exists
101+npm install
61102
62−# Run formatting if configured
63−npm run format
64−
65−# Run type checking if TypeScript
66−npm run type-check
103+# Check for environment variables
104+ls .env* || echo "No environment files found"
67105 ```
68106
69−## Repository Structure Expectations
70−
71−Based on the .gitignore configuration, expect the following when the repository is populated:
72−
73−```
74−.
75−├── README.md # Project documentation
76−├── LICENSE # MIT license
77−├── .gitignore # Node.js/Next.js ignore patterns
78−├── package.json # Node.js dependencies and scripts
79−├── package-lock.json # Dependency lockfile
80−├── next.config.js # Next.js configuration (if Next.js)
81−├── tsconfig.json # TypeScript configuration (if TypeScript)
82−├── .eslintrc.* # ESLint configuration
83−├── .prettierrc # Prettier configuration
84−├── src/ # Source code directory
85−│ ├── pages/ # Next.js pages (if Next.js)
86−│ ├── components/ # React components
87−│ └── utils/ # Utility functions
88−├── public/ # Static assets
89−├── .next/ # Next.js build output (ignored)
90−├── build/ # Build output (ignored)
91−└── node_modules/ # Dependencies (ignored)
92−```
93−
94−## Validation Requirements
95−
96−### Before Making Changes
97−1. **Always check current repository state first**:
98− ```bash
99− git status
100− ls -la
101− cat package.json # Only if it exists
102− ```
103−
104−2. **Verify build system exists before attempting builds**:
105− ```bash
106− # Check for package.json before running npm commands
107− test -f package.json && echo "Node.js project detected" || echo "No package.json found"
108− ```
109−
110−### After Making Changes
111−1. **When source code is present, always validate**:
112− ```bash
113− # Install dependencies if package.json exists
114− test -f package.json && npm install
115−
116− # Build if build script exists
117− test -f package.json && npm run build
118−
119− # Test if test script exists
120− test -f package.json && npm test
121−
122− # Lint if lint script exists
123− test -f package.json && npm run lint
124− ```
125−
126−2. **Manual validation scenarios when application exists**:
127− - Start the development server and verify it loads
128− - Test basic functionality by navigating through the application
129− - Verify any API endpoints respond correctly
130− - Check console for errors
131−
132−## Common Commands Reference
133−
134−### Repository Information
107+### AI Service Integration
135108 ```bash
136−# View current files
137−ls -la
109+# Check for AI-related packages
110+grep -E "(openai|langchain|tensorflow|pytorch|huggingface)" package.json
138111
139−# Check git status
140−git status
141−
142−# View repository structure
143−tree . -a -I 'node_modules|.git' # If tree is available (use -a to show hidden files)
144−find . -type f -not -path "./.git/*" -not -path "./node_modules/*" | sort
112+# Validate environment configuration
113+test -f .env.example && echo "Environment template found" || echo "Create .env.example for required variables"
145114 ```
146115
147−### When Package.json Exists
116+### Before Committing
148117 ```bash
149−# View available scripts
150−cat package.json | grep -A 20 '"scripts"'
118+# Run linting if configured
119+npm run lint 2>/dev/null || echo "No lint script found"
151120
152−# Install dependencies
153−npm install
154−# TIMEOUT: 10+ minutes
121+# Run tests if configured
122+npm run test 2>/dev/null || echo "No test script found"
155123
156−# Common development commands (check package.json first)
157−npm run dev # Development server
158−npm run build # Production build
159−npm run start # Start production server
160−npm run test # Run tests
161−npm run lint # Run linter
162−npm run format # Format code
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"
163126 ```
164127
165−## File Locations and Navigation
166−
167−### Current Key Files
168−- `/README.md` - Project overview and setup instructions
169−- `/LICENSE` - MIT license terms
170−- `/.gitignore` - Git ignore patterns (Node.js/Next.js focused)
171−
172−### Expected Important Locations (when populated)
173−- `/src/` - Main source code directory
174−- `/src/pages/` - Next.js pages (if Next.js project)
175−- `/src/components/` - React components
176−- `/public/` - Static assets and files
177−- `/package.json` - Project configuration and dependencies
178−- `/next.config.js` - Next.js configuration
179−- `/tsconfig.json` - TypeScript configuration
180−
181−## AI Development Guidelines
182−
183−Since this is an AI setup repository:
184−
185−1. **Always verify AI-related dependencies** when they are added:
186− ```bash
187− # Common AI packages to look for
188− grep -E "(openai|langchain|tensorflow|pytorch|huggingface)" package.json
189− ```
190−
191−2. **Environment variables for AI services**:
192− ```bash
193− # Check for environment configuration
194− ls .env* || echo "No environment files found"
195− ```
196−
197−3. **API key management**:
198− - Never commit API keys
199− - Always use environment variables
200− - Check .env.example for required variables
201−
202−## Troubleshooting
203−
204−### Repository Appears Empty
205−- This is expected in the current state
206−- Check git branch: `git branch -a`
207−- Look for other branches that might contain code
208−
209−### Build Failures
210−- First verify package.json exists: `ls package.json`
211−- Clear dependencies and reinstall: `rm -rf node_modules package-lock.json && npm install`
212−- Check Node.js version compatibility in package.json
213−
214−### Development Server Issues
215−- Verify port availability (typically 3000 for Next.js)
216−- Check for environment variable requirements
217−- Review console output for specific error messages
218−
219−## Critical Reminders
220−
221−- **NEVER CANCEL builds or long-running commands** - they may take 45+ minutes
222−- **ALWAYS validate commands work** before assuming functionality exists
223−- **CHECK for package.json** before running npm commands
224−- **SET APPROPRIATE TIMEOUTS** - builds: 60+ minutes, tests: 30+ minutes
225−- **VERIFY repository state** before attempting any operations
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
