Claude Code Starter


Intelligent CLI that bootstraps Claude Code configurations tailored to your project's tech stack.

Quick Start

``bash
cd your-project
npx claude-code-starter
claude
`

What It Does

1. Analyzes your repository - Detects languages, frameworks, tools, and patterns
2. Generates tailored configurations - Creates skills, agents, and rules for your stack
3. Sets up development workflow - Task tracking, commands, and methodology guides

Tech Stack Detection

Automatically detects and configures for:

| Category | Detected |
| -------------- | ------------------------------------------------------------------- |
| Languages | TypeScript, JavaScript, Python, Go, Rust, Java, Ruby, and more |
| Frameworks | Next.js, React, Vue, Svelte, FastAPI, Django, NestJS, Express, etc. |
| Tools | npm, yarn, pnpm, bun, pip, cargo, go modules |
| Testing | Jest, Vitest, Pytest, Go test, Rust test |
| Linting | ESLint, Biome, Ruff, Pylint |

Generated Configurations

Based on your stack, creates:

- 📚 Skills - Framework-specific patterns (e.g., Next.js App Router, FastAPI endpoints)
- 🤖 Agents - Specialized assistants (code reviewer, test writer)
- 📏 Rules - Language conventions (TypeScript strict mode, Python PEP 8)
- ⚡ Commands - Workflow shortcuts (/task, /status, /done, /analyze)

Commands

| Command | Description |
| ----------------- | ---------------------------------------- |
| /task | Start a new task |
| /status | Show current task |
| /done | Mark task complete |
| /analyze | Deep dive into code |
| /code-review | Review changes for quality and security |

CLI Options

`bash
npx claude-code-starter # Interactive mode
npx claude-code-starter -y # Non-interactive (use defaults)
npx claude-code-starter -f # Force overwrite existing files
npx claude-code-starter -V # Verbose output
npx claude-code-starter --help # Show help
`

Example Output

`
╔═══════════════════════════════════╗
║ Claude Code Starter ║
║ AI-Assisted Development Setup ║
╚═══════════════════════════════════╝

🔍 Analyzing repository...

📊 Tech Stack Analysis
Language: TypeScript
Framework: Next.js
Package Manager: bun
Testing: vitest

✅ Configuration complete! (14 files)

Generated for your stack:
📚 9 skills (pattern-discovery, iterative-development, security, nextjs-patterns, ...)
🤖 2 agents (code-reviewer, test-writer)
📏 2 rules
`

Project Structure

After running, your project will have:

`
.claude/
├── CLAUDE.md # Project-specific instructions
├── settings.json # Permissions configuration
├── agents/ # Specialized AI agents
│ ├── code-reviewer.md
│ └── test-writer.md
├── commands/ # Slash commands
│ ├── task.md
│ ├── status.md
│ ├── done.md
│ ├── analyze.md
│ └── code-review.md
├── rules/ # Code style rules
│ ├── typescript.md # (or python.md, etc.)
│ └── code-style.md
├── skills/ # Methodology guides + patterns
│ ├── pattern-discovery.md
│ ├── systematic-debugging.md
│ ├── testing-methodology.md
│ ├── iterative-development.md
│ ├── commit-hygiene.md
│ ├── code-deduplication.md
│ ├── simplicity-rules.md
│ ├── security.md
│ └── nextjs-patterns.md # (framework-specific)
└── state/
└── task.md # Current task tracking
`

How It Works

$3

`mermaid
flowchart LR
A[CLI] --> B[Analyzer]
B --> C[Generator]
C --> D[.claude/]

B -->|reads| E[package.json]
B -->|reads| F[config files]
B -->|reads| G[lock files]

C -->|creates| H[skills/]
C -->|creates| I[agents/]
C -->|creates| J[rules/]
C -->|creates| K[commands/]
`

$3

All artifacts are generated dynamically based on your detected tech stack. There are no static templates - content is created specifically for your project.

| Artifact Type | Generation Logic |
|---------------|------------------|
| CLAUDE.md | Generated with project name, description, and detected stack |
| settings.json | Generated with safe default permissions |
| Skills | Core skills + framework-specific patterns (if detected) |
| Agents | Code reviewer and test writer agents |
| Rules | Language-specific conventions + general code style |
| Commands | Task workflow commands (/task, /status, /done, /analyze) |

$3

When running on an existing project with .claude/ configuration:

| Scenario | Behavior |
|----------|----------|
| New file | Created |
| Existing file | Skipped (preserved) |
| With -f flag | Overwritten |
| state/task.md | Always preserved |

$3

The CLI examines these files to detect your stack:

| Source | Detects |
|--------|---------|
| package.json | JS/TS frameworks, testing, linting |
| pyproject.toml / requirements.txt | Python frameworks, tools |
| go.mod | Go and its web frameworks |
| Cargo.toml | Rust and its frameworks |
| *.lockfile | Package manager (bun.lockb, yarn.lock, etc.) |
| .github/workflows/ | CI/CD platform |
| Config files | Linters, formatters, bundlers |

$3

When a framework is detected, additional skills are generated:

| Framework | Generated Skill |
|-----------|-----------------|
| Next.js | nextjs-patterns.md - App Router, Server Components |
| React | react-components.md - Hooks, component patterns |
| FastAPI | fastapi-patterns.md - Async endpoints, Pydantic |
| NestJS | nestjs-patterns.md - Modules, decorators, DI |

$3

📚 Skill Example (pattern-discovery.md)

`markdown
---
description: "Systematic approach to discovering patterns in unfamiliar codebases"
---

Pattern Discovery

When to Use

- Starting work on unfamiliar code
- Investigating "how does X work here?"
- Before making changes to existing systems

Approach

1. Find entry points (main, index, app)
2. Trace data flow through the system
3. Identify naming conventions
4. Map directory structure to responsibilities
`


🤖 Agent Example (code-reviewer.md)

`markdown
---
name: "Code Reviewer"
description: "Reviews code for quality, patterns, and potential issues"
model: "sonnet"
tools: ["Read", "Glob", "Grep"]
---

Code Reviewer Agent

You are a code reviewer focused on:
- Code quality and readability
- Potential bugs and edge cases
- Performance considerations
- Security vulnerabilities
`


📏 Rule Example (typescript.md)

`markdown
---
paths: ["/.ts", "/.tsx"]
---

TypeScript Conventions

- Use strict mode ("strict": true)
- Prefer interface over type for object shapes
- Use explicit return types on exported functions
- Avoid any, prefer unknown for truly unknown types
`


⚡ Command Example (task.md)

`markdown
---
description: "Start or switch to a new task"
---

/task

Update .claude/state/task.md with:
- Task description from user input
- Status: In Progress
- Empty decisions/notes sections
- Clear next steps
`


Tip

Add .claude/ to your global gitignore:

`bash
echo ".claude/" >> ~/.gitignore
git config --global core.excludesfile ~/.gitignore
`

CI/CD

This project uses GitHub Actions for continuous integration and automated releases.

$3

Every pull request targeting main runs:

| Check | Description |
|-------|-------------|
| Lint | Biome lint and format validation |
| Type Check | TypeScript compilation check |
| Unit Tests | Full test suite with Bun |
| Code Quality | Checks for console.log, any types, skipped tests |
| Build | Verifies package builds successfully |
| Package Size | Reports bundle size (warns if > 500KB) |

$3

When code is merged to main, semantic-release automatically:

1. Analyzes commit messages (conventional commits)
2. Determines version bump (major/minor/patch)
3. Updates package.json version
4. Generates CHANGELOG.md
5. Creates GitHub release with notes
6. Publishes to npm registry

$3

Use these prefixes for automatic versioning:

| Prefix | Version Bump | Example |
|--------|--------------|---------|
| feat: | Minor | feat: add dark mode support |
| fix: | Patch | fix: resolve memory leak |
| perf: | Patch | perf: optimize image loading |
| BREAKING CHANGE: | Major | feat!: redesign API |
| docs:, chore:, ci: | No release | docs: update README |

$3

Configure these in your GitHub repository settings:

| Secret | Description | Required For |
|--------|-------------|--------------|
| NPM_TOKEN | npm authentication token | Publishing to npm |
| GITHUB_TOKEN | Auto-provided by GitHub | Creating releases |

To create an npm token:
1. Go to npmjs.com → Access Tokens
2. Generate a new "Automation" token
3. Add it as NPM_TOKEN in GitHub repo → Settings → Secrets

$3

Configure these settings for the main branch:

- ✅ Require a pull request before merging
- ✅ Require status checks to pass before merging
- Required checks: lint, typecheck, test, build, pr-check-complete
- ✅ Require branches to be up to date before merging
- ✅ Do not allow bypassing the above settings

Development

`bash


Install dependencies

bun install

Run in development mode

bun run dev

Run tests

bun test

Build

bun run build

Lint

bun run lint

Type check

bun run typecheck
``

License

MIT