claude-code-starterlisted

# Claude Code Starter You are setting up Claude Code configuration for a project. Follow the flow below to analyze the project and generate all `.claude/` configuration files. ## Step 1: Detect Project Type Check if this is a **new project** (empty or <3 source files) or an **existing project**. **For new projects**, ask the user these questions: 1. What are you building? (project description) 2. Primary language? (TypeScript, JavaScript, Python, Go, Rust, Swift, Kotlin, Java, Ruby, C#, PHP, C++) 3. Framework? (filtered by language — e.g. Next.js/React/Vue for TS/JS, FastAPI/Django/Flask for Python) 4. Package manager? (filtered by language) 5. Testing framework? (filtered by language, or "None") 6. Linter/Formatter? (filtered by language, or "None") 7. Project type? (Web App, API/Backend, CLI Tool, Library/Package, Mobile App, Desktop App, Monorepo, Other) **For existing projects**, analyze the codebase: - Read `package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`, `Gemfile`, or equivalent - Detect languages, frameworks, package manager, testing, linting, formatting, bundler - Identify architecture patterns, directory structure, code conventions ## Step 2: Create `.claude/settings.json` Generate `settings.json` with permissions based on detected stack. Example: ```json { "$schema": "https://json.schemastore.org/claude-code-settings.json", "permissions": { "allow": [ "Read(**)", "Edit(**)", "Write(.claude/**)", "Bash(git:*)", "Bash(npm:*)", "Bas