project-bootstrapper

Name: project-bootstrapper
Author: mhattingpete/claude-skills-marketplace

$npx mdskill add mhattingpete/claude-skills-marketplace/project-bootstrapper

Bootstraps new projects or improves existing ones with best practices.

Sets up project structure, git config, documentation, testing, and code quality tools.
Depends on git, testing frameworks, linters, formatters, and type checkers.
Analyzes project type and language to recommend appropriate tooling and structure.
Creates or modifies files and configurations directly in the project directory.

SKILL.md

.github/skills/project-bootstrapperView on GitHub ↗

---
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

More from mhattingpete/claude-skills-marketplace

Skill	Description
architecture-diagram-creator	Create comprehensive HTML architecture diagrams showing data flows, business objectives, features, technical architecture, and deployment. Use when users request system architecture, project documentation, high-level overviews, or technical specifications.
code-auditor	Performs comprehensive codebase analysis covering architecture, code quality, security, performance, testing, and maintainability. Use when user wants to audit code quality, identify technical debt, find security issues, assess test coverage, or get a codebase health check.
code-execution	Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
code-refactor	Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
code-transfer	Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
codebase-documenter	Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
conversation-analyzer	Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, identify automation opportunities, or check if they're following best practices.
dashboard-creator	Create HTML dashboards with KPI metric cards, bar/pie/line charts, progress indicators, and data visualizations. Use when users request dashboards, metrics displays, KPI visualizations, data charts, or monitoring interfaces.
ensemble-solving	Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
feature-planning	Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.