Skip to main content
skill CX Codex

project-bootstrapper — Claude Code skill: what it does, how to install

project-bootstrapper — a skill for Claude Code, Cursor, Codex and other platforms that scaffolds a new project or levels up an existing one: directories, linter configs, tests, Git hooks, CI/CD and documentation.

Apache-2.0 212 installs ★ 697 updated 2026-07-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mhattingpete/claude-skills-marketplace --skill project-bootstrapper -a claude-code
Open on GitHub

What project-bootstrapper does

Asks for project type (web app, CLI, library), language and framework, then builds a plan: creates src/, tests/, docs/, .github/, drops in .gitignore, .editorconfig, wires up linters (ESLint, Pylint), formatters (Prettier, Black), type checkers (TypeScript, mypy), Git pre-commit hooks, test frameworks and coverage, GitHub Actions or GitLab CI for automated testing and deployment, Dependabot for dependency updates. Writes README.md, CONTRIBUTING.md, CHANGELOG.md, example .env.example, adds Docker configs and Makefile targets for development. Includes templates for Node.js/TypeScript, Python CLI and FastAPI, React/Next.js, Go, Rust.

Adapts the setup to team size and project maturity: a solo script gets the minimum, an enterprise service gets the full suite with branch protection and architecture docs. Asks whether you want full bootstrap or just a specific piece (for instance, add tests to existing code). Without TypeScript or Python in the project, type checkers stay out.

What it helps with

  • scaffold a new project with tests, linters and CI in one pass
  • bring legacy code to production standards: add pre-commit hooks, coverage, Dependabot
  • standardize repository structure to match team conventions
  • wire up automated deployment and release automation through GitHub Actions
  • write README.md, CONTRIBUTING.md and .env.example for developer onboarding

Example prompts for the agent

  • Scaffold a new Python CLI with tests, mypy and GitHub Actions
  • Add linters, formatters and pre-commit hooks to this project
  • Level up the structure to production: Docker, CI, docs and branch protection

How to install project-bootstrapper

1Skills CLI (Vercel)

npx skills add mhattingpete/claude-skills-marketplace --skill project-bootstrapper -a claude-code

2Manually: put the files in place

~/.claude/skills/project-bootstrapper/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/project-bootstrapper/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about project-bootstrapper

How do I install project-bootstrapper in Claude Code?

Run npx skills add mhattingpete/claude-skills-marketplace --skill project-bootstrapper -a claude-code in the terminal. The skill will land in ~/.claude/skills/project-bootstrapper/SKILL.md.

What does project-bootstrapper do?

Scaffolds project structure: creates src/, tests/, docs/ directories, configures linters, formatters, type checkers, Git hooks, test frameworks, CI/CD, Dependabot and writes documentation. Works for new projects and for leveling up existing ones to production standards.

Can I add just tests without a full bootstrap?

Yes. The skill asks whether you want full setup or a specific area — for example, only test framework and coverage. Say "add tests" and it will wire up the framework, create tests/ structure and write examples.

Source text

SKILL.md · Apache-2.0
---
name: project-bootstrapper
description: Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation. Use when user wants to start a new project, improve project structure, add development tooling, or establish professional workflows.
---

# Project Bootstrapper

Sets up new projects or improves existing projects with development best practices, tooling, documentation, and workflow automation.

## When to Use

- "set up a new project"
- "bootstrap this project"
- "add best practices"
- "improve project structure"
- "set up development tooling"
- "initialize project properly"

## What It Sets Up

### 1. Project Structure
- Standard directories (src/, tests/, docs/, scripts/, .github/)
- Logical file organization
- Structure improvements

### 2. Git Configuration
- Comprehensive `.gitignore`
- `.gitattributes` for line endings/diffs
- Git hooks (pre-commit, commit-msg)
- Branch protection patterns
- Git LFS if needed

### 3. Documentation
- Comprehensive `README.md`
- `CONTRIBUTING.md`
- Code documentation (JSDoc, docstrings)
- `CHANGELOG.md` structure
- Architecture docs if complex

### 4. Testing Setup
- Identify/suggest testing framework
- Test structure and conventions
- Example/template tests
- Configure test runners
- Coverage reporting
- Testing scripts/commands

### 5. Code Quality Tools
- Linters (ESLint, Pylint, etc.)
- Formatters (Prettier, Black, etc.)
- Type checking (TypeScript, mypy, etc.)
- Pre-commit hooks for quality
- Editor configs (.editorconfig)
- Code quality badges

### 6. Dependencies Management
- Package manager configuration
- Organize dependencies
- Check security vulnerabilities
- Set up dependency updates (Dependabot, Renovate)
- Create lock files
- Document dependency choices

### 7. Development Workflow
- Useful npm scripts / Makefile targets
- Environment variable templates (.env.example)
- Docker configuration if appropriate
- Development startup scripts
- Hot-reload / watch modes
- Document development workflow

### 8. CI/CD Setup
- GitHub Actions / GitLab CI config
- Automated testing
- Automated deployment (if applicable)
- Status badges
- Release automation
- Branch protection

## Approach

### Discovery Phase

Ask clarifying questions:
1. **Project type**: New or existing?
2. **Primary purpose**: Web app, library, CLI tool?
3. **Language/framework**: JS/TS, Python, Go, etc.?
4. **Collaboration**: Personal or team?
5. **Deployment target**: Server, cloud, mobile, desktop?
6. **Preferences**: Specific tools/frameworks?
7. **Scope**: Full setup or specific areas?

### Implementation Phase

1. **Analyze existing** structure (if existing project)
2. **Create plan** based on answers
3. **Show plan** and get approval
4. **Implement systematically** (one area at a time)
5. **Verify completeness**
6. **Provide handoff** documentation

## Customization

Adapts to:
- **Language ecosystem**: Node.js vs Python vs Go vs Rust
- **Project size**: Small script vs large app
- **Team size**: Solo vs collaborative
- **Maturity**: Startup speed vs enterprise standards

## Tools Used

- **AskUserQuestion**: Gather requirements
- **Write**: Create configuration files, documentation
- **Edit**: Update existing files
- **Bash**: Initialize tools (git init, npm init)
- **Read**: Analyze existing structure
- **Glob**: Find files to update

## Success Criteria

- All standard files present and configured
- Clear and complete documentation
- Documented development workflow
- Automated quality tooling (pre-commit hooks)
- Easy test execution
- Follows language/framework conventions
- Quick developer onboarding
- No obvious best practices missing

## Templates

- Node.js/TypeScript web app
- Python CLI tool
- Python web API (FastAPI/Flask)
- React/Next.js app
- Go service
- Rust CLI/library

## Integration

- **feature-planning**: For planning custom features
- **code-auditor**: For validating setup quality
- **codebase-documenter**: For generating detailed docs

## Scope Control

- **Full bootstrap**: Everything from scratch
- **Partial setup**: Specific areas only (e.g., "just add testing")
- **Improvement pass**: Enhance existing project
- **Audit + fix**: Check what's missing and add it

© mhattingpete · Apache-2.0 · mhattingpete/claude-skills-marketplace

Similar skills

All skills for DevOps and infrastructure →

From the same set15

The whole set →
timeline-creator timeline-creator turns a project's tasks and dates into an interactive HTML timeline with Gantt bars, phases and milestones. Handy when a plan has to live in one file. CX Codex +1 337installs code-refactor code-refactor is a Claude Code skill for bulk code changes across files: renaming variables and functions, replacing deprecated patterns, and updating API calls. It automatically selects a mode that saves up to 90% of tokens for 10+ files. CX Codex +1 304installs feature-planning The feature-planning skill turns feature requests and complex changes into ordered implementation plans with concrete tasks. Use it before coding when the scope needs structure. CX Codex +1 297installs code-execution The code-execution skill runs Python locally for bulk file work, code analysis, transformations, and Git tasks. It fits large or multi-step workflows. CX Codex +1 294installs conversation-analyzer conversation-analyzer analyzes your local Claude Code session logs to detect recurring errors, repetitive prompts, and workflow bottlenecks. CX Codex +1 249installs technical-doc-creator technical-doc-creator builds HTML documentation for APIs and systems with code samples, architecture diagrams, syntax highlighting, and workflow steps. CX Codex +1 221installs ensemble-solving ensemble-solving spawns three parallel subagents to explore diverse solutions, scores each approach against weighted criteria, and returns the best outcome with trade-offs. CX Codex +1 218installs code-transfer A skill for precise code transfer between files using line-based positioning. Useful when you need to move a function to another file, extract a class into a separate module, or insert code at a specific line number. CX Codex +1 173installs

Project sponsors

Companies that keep this analytics open