project-bootstrapper

Q: How do I install project-bootstrapper?

Run npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill project-bootstrapper in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/project-bootstrapper/ (personal) or .claude/skills/project-bootstrapper/ (project).

by mhattingpeteProductivity & Automation

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.

Installs: 209
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill project-bootstrapper

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads project-bootstrapper automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

Project type: New or existing?
Primary purpose: Web app, library, CLI tool?
Language/framework: JS/TS, Python, Go, etc.?
Collaboration: Personal or team?
Deployment target: Server, cloud, mobile, desktop?
Preferences: Specific tools/frameworks?
Scope: Full setup or specific areas?

Implementation Phase

Analyze existing structure (if existing project)
Create plan based on answers
Show plan and get approval
Implement systematically (one area at a time)
Verify completeness
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

FAQ

What does the project-bootstrapper skill do?

How do I install project-bootstrapper?

Run npx skills add https://github.com/mhattingpete/claude-skills-marketplace --skill project-bootstrapper in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/project-bootstrapper/ (personal) or .claude/skills/project-bootstrapper/ (project).

Which AI agents can use project-bootstrapper?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is project-bootstrapper safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains project-bootstrapper?

It is published by mhattingpete in mhattingpete/claude-skills-marketplace. It has 209 recorded installs.