project-init

Files (1)

• SKILL.md

SKILL.md (first lines)

# Project Init — CLAUDE.md Template Generator

Generates a project-level CLAUDE.md tailored to the detected tech stack.
Eliminates boilerplate setup and ensures consistent project conventions.

## Detection Logic

Scan the project root for stack indicators:

```
package.json + next.config.*     → Next.js template
package.json + expo              → Expo/React Native template
package.json (generic)           → Node.js template
pubspec.yaml                     → Flutter/Dart template
requirements.txt | pyproject.toml → Python template
Cargo.toml                       → Rust template
go.mod                           → Go template
Gemfile                          → Ruby/Rails template
*.sln | *.csproj                 → .NET template
build.gradle*                    → Java/Kotlin template
Dockerfile (no app code)         → DevOps template
No indicators                    → Generic template
```

If multiple indicators exist, use the primary one (first match in order above).

## Template: Next.js

```markdown
# Project Instructions

## Stack
- Next.js (App Router), React, TypeScript
- Tailwind CSS for styling

## Conventions
- Use Server Components by default, 'use client' only when needed
- File conventions: page.tsx, layout.tsx, loading.tsx, error.tsx
- Data fetching in Server Components (no useEffect for initial data)
- Route handlers in app/api/ with proper HTTP status codes

## Testing
- Jest + React Testing Library for unit tests
- Playwright for E2E (if configured)
- Run: `npm test` (unit), `npx playwright test` (E2E)

## Commands
- Dev: `npm run dev`
- Build: `npm run build`
- Lint: `npm run lint`
- Format: `npx prettier --write .`
```

## Template: Python

```markdown
# Project Instructions

## Stack
- Python 3.11+
- Package manager: uv (preferred) or pip

## Conventions
- Type hints on all function signatures
- snake_case everywhere, UPPER_SNAKE for constants
- Async/await for I/O-bound operations
- Pydantic for data validation

## Testing
- pytest with fixtures
- Run: `pytest` or `uv run pytest`
- Coverage: `pytest --cov`

## Quality
- Formatter: ruff format
- Linter: ruff check
- Type checker: ty or mypy
```

## Template: Flutter/Dart

```markdown
# Project Instructions

## Stack
- Flutter, Dart
- State management: [detect from pubspec.yaml — riverpod/bloc/provider]

## Conventions
- Widgets: small, composable, single-purpose
- File structure: lib/features/{name}/ with models, views, controllers
- const constructors wherever possible
- Named parameters for widget constructors

## Testing
- flutter test for unit/widget tests
- integration_test/ for integration tests
- Run: `flutter test`

## Commands
- Dev: `flutter run`
- Build: `flutter build apk` / `flutter build ios`
- Format: `dart format .`
- Analyze: `dart analyze`
```

## Template: Go

```markdown
# Project Instructions

## Stack
- Go 1.22+

## Conventions
- Error handling: always check returned errors, wrap with fmt.Errorf
- Interfaces: accept interfaces, return structs
- Package names: short, lowercase, no underscores
- Context: pass as first parameter

From Leo-Atienza/atlas-claude, MIT.

More from Leo-Atienza/atlas-claude