99 lines
2.0 KiB
Markdown
99 lines
2.0 KiB
Markdown
|
# CLAUDE.md
|
||
|
|
|
||
|
|
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
||
|
|
|
||
|
|
## Project Overview
|
||
|
|
|
||
|
|
This is a new workspace without an existing codebase. The repository is ready for new project initialization.
|
||
|
|
|
||
|
|
## Common Commands
|
||
|
|
|
||
|
|
Since this is a new workspace, you'll need to establish project structure based on the technology stack chosen:
|
||
|
|
|
||
|
|
### Project Initialization Commands
|
||
|
|
|
||
|
|
**For Node.js projects:**
|
||
|
|
```bash
|
||
|
|
npm init -y
|
||
|
|
npm install [packages]
|
||
|
|
npm run dev
|
||
|
|
npm run build
|
||
|
|
npm test
|
||
|
|
```
|
||
|
|
|
||
|
|
**For Python projects:**
|
||
|
|
```bash
|
||
|
|
python -m venv venv
|
||
|
|
source venv/bin/activate
|
||
|
|
pip install -r requirements.txt
|
||
|
|
python -m pytest
|
||
|
|
```
|
||
|
|
|
||
|
|
**For Go projects:**
|
||
|
|
```bash
|
||
|
|
go mod init [module-name]
|
||
|
|
go mod tidy
|
||
|
|
go run .
|
||
|
|
go test ./...
|
||
|
|
```
|
||
|
|
|
||
|
|
**For Rust projects:**
|
||
|
|
```bash
|
||
|
|
cargo init
|
||
|
|
cargo build
|
||
|
|
cargo run
|
||
|
|
cargo test
|
||
|
|
```
|
||
|
|
|
||
|
|
### Directory Structure Recommendations
|
||
|
|
|
||
|
|
Consider establishing one of these structures based on project type:
|
||
|
|
|
||
|
|
**Web Application:**
|
||
|
|
```
|
||
|
|
src/
|
||
|
|
├── components/
|
||
|
|
├── pages/
|
||
|
|
├── utils/
|
||
|
|
├── styles/
|
||
|
|
└── tests/
|
||
|
|
```
|
||
|
|
|
||
|
|
**API Service:**
|
||
|
|
```
|
||
|
|
src/
|
||
|
|
├── handlers/
|
||
|
|
├── models/
|
||
|
|
├── middleware/
|
||
|
|
├── config/
|
||
|
|
└── tests/
|
||
|
|
```
|
||
|
|
|
||
|
|
**Library/Package:**
|
||
|
|
```
|
||
|
|
src/
|
||
|
|
├── core/
|
||
|
|
├── utils/
|
||
|
|
├── types/
|
||
|
|
└── tests/
|
||
|
|
```
|
||
|
|
|
||
|
|
## Technology Stack Detection
|
||
|
|
|
||
|
|
When starting work in this repository:
|
||
|
|
1. Check for existing package.json, requirements.txt, Cargo.toml, or go.mod
|
||
|
|
2. Look for .gitignore, .env files, or other configuration indicators
|
||
|
|
3. Examine any existing README.md or documentation
|
||
|
|
4. Ask the user about intended technology stack if unclear
|
||
|
|
|
||
|
|
## Development Environment
|
||
|
|
|
||
|
|
This workspace runs in WSL (Windows Subsystem for Linux). File paths from Windows should be converted to WSL format:
|
||
|
|
- Windows: `C:\temp\file.txt` → WSL: `/mnt/c/temp/file.txt`
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
1. Determine the intended technology stack with the user
|
||
|
|
2. Initialize project structure accordingly
|
||
|
|
3. Set up appropriate build tools and testing framework
|
||
|
|
4. Create initial project files based on requirements
|