80% of the value in 20% of the time
An interactive script that sets up your Claude Code environment in 3-5 minutes by asking smart questions about your project.
The Jumpstart script automatically creates:
✅ Custom CLAUDE.md - Tailored to your project type and language
✅ Relevant Agents - Only the ones you actually need
✅ Helpful Commands - Based on your workflow
✅ settings.json - Sensible defaults
✅ Personalized Guide - Your specific next steps
No manual configuration needed!
# Download the script
curl -O https://[your-url]/claude-code-jumpstart.sh
# Make it executable
chmod +x claude-code-jumpstart.sh
# Run it in your project directory
./claude-code-jumpstart.shTime: 3-5 minutes
- Your Experience - Never used it / Tried once / Week or two / Pretty comfortable
- Project Type - Web app / Backend / Full-stack / Mobile / Data/ML / DevOps
- Primary Language - JavaScript/TS / Python / Go / Java / Ruby / Rust / PHP
- Project Phase - Starting / Active dev / Maintenance / Refactoring
- Team Size - Solo / Small (2-5) / Medium (6-15) / Large (15+)
- Pain Points - Boilerplate / Tests / Reviews / Debugging / Refactoring / Docs
- Existing Project - Yes / No
Based on your answers, it creates a customized setup.
Answers:
- Experience: Tried once
- Project: Web app
- Language: TypeScript
- Phase: Just starting
- Team: Solo
- Pain: Writing boilerplate, tests
- Existing: No
Creates:
- Basic CLAUDE.md for TypeScript/React
- test-agent (you want help with tests)
- /frontend:component command (for boilerplate)
- /testing:unit command
- Beginner-focused guide
Answers:
- Experience: Pretty comfortable
- Project: Backend
- Language: Python
- Phase: Major refactoring
- Team: Small (5 people)
- Pain: Refactoring, code reviews
- Existing: Yes
Creates:
- CLAUDE.md for Python backend
- refactor-agent (you're refactoring)
- code-reviewer (you're a team)
- /backend:endpoint command
- Team collaboration tips
Answers:
- Experience: Never used it
- Project: Data/ML
- Language: Python
- Phase: Active development
- Team: Solo
- Pain: Documentation, debugging
- Existing: Yes
Creates:
- CLAUDE.md for Python/Data
- test-agent (good for any project)
- Extra beginner guidance
- Realistic timeline (Week 1 slower)
your-project/
├── .claude/
│ ├── CLAUDE.md ← Customized for your project
│ ├── GETTING_STARTED.md ← Your personalized guide
│ ├── settings.json ← Configuration
│ ├── COMMIT_THIS.sh ← Helper to commit to git
│ ├── agents/ ← Only what you need
│ │ ├── test-agent.md (if applicable)
│ │ ├── code-reviewer.md (if team/review pain)
│ │ └── refactor-agent.md (if refactoring)
│ └── commands/ ← Based on project type
│ ├── frontend/ (if web app)
│ ├── backend/ (if backend)
│ └── testing/ (if testing pain)
└── .gitignore ← Updated to ignore local settings
CLAUDE.md - Contains:
- Project overview
- Tech stack (pre-filled for your language)
- Code standards (language-specific)
- File organization
- Development workflow
- Project-specific sections
GETTING_STARTED.md - Contains:
- What was set up
- Your next 3 steps (10 minutes)
- First request suggestion (based on your phase)
- Expected timeline (based on experience)
- Common mistakes to avoid
- Personalized tips
Agents - Created based on:
- test-agent: For intermediate+ users OR testing pain point
- code-reviewer: For teams OR review pain point
- refactor-agent: For refactoring phase OR refactoring pain point
Commands - Created based on:
- /frontend:component: For web apps (TypeScript)
- /backend:endpoint: For backend projects
- /testing:unit: For testing pain points
test-agent:
IF experience >= intermediate
OR pain_point = testing
THEN create
code-reviewer:
IF team_size > solo
OR pain_point = review
THEN create
refactor-agent:
IF project_phase = refactor
OR pain_point = refactoring
THEN create
/frontend:component:
IF project_type = webapp OR fullstack
AND language = typescript
THEN create
/backend:endpoint:
IF project_type = backend OR fullstack
THEN create
/testing:unit:
IF pain_point = testing
THEN create
CLAUDE.md varies by:
- Language (Python vs TypeScript vs Go, etc.)
- Project type (API structure, frontend patterns)
- Phase (focus areas differ)
GETTING_STARTED.md varies by:
- Experience level (timelines, detail level)
- Phase (suggested first request)
- Pain points (relevant tips)
- Team size (collaboration advice)
Manual Setup:
- Read documentation (1-2 hours)
- Copy templates
- Figure out what you need
- Customize everything
- Easy to miss key steps
Jumpstart Script:
- Answer 7 questions (2 minutes)
- Auto-generated, tailored setup (1 minute)
- Read personalized guide (3 minutes)
- Start coding (immediate)
Time saved: 1-2 hours
Generic Template:
- Everything included (overwhelming)
- Not specific to your needs
- Lots to delete/customize
- May include wrong patterns
Jumpstart Script:
- Only what you need (focused)
- Specific to your project
- Nothing to delete
- Correct patterns for your stack
Better user experience
# Team lead sets up
./claude-code-jumpstart.sh
# Customize CLAUDE.md for team
vim .claude/CLAUDE.md
# Commit to repository
./.claude/COMMIT_THIS.sh
git push
# Team members pull and use
git pull
claudeEveryone has the same baseline setup.
- Consistent CLAUDE.md across team
- Shared agents and commands
- Same workflow patterns
- Easier onboarding
- Team-specific customizations preserved
The script creates a starting point, not a final state.
CLAUDE.md (do immediately):
- Add your specific tech stack
- Document your code patterns
- Add your common commands
- Update as project evolves
Agents (add as needed):
- Create project-specific agents
- Modify existing agent instructions
- Add more agents when pain points emerge
Commands (grow over time):
- Add commands for repetitive tasks
- Create shortcuts for your patterns
- Document team workflows
Non-interactive mode for CI/CD and automation is planned for v2.0.
What it will look like:
# Coming in v2.0!
./claude-code-jumpstart.sh \
--experience intermediate \
--project webapp \
--language typescript \
--phase active \
--team small \
--pain testing,review \
--existing yes \
--silentCurrent workaround:
Run the script once interactively, commit the .claude/ directory to your repository, and your team can pull it down.
Want this feature? Star the repo and let us know in discussions!
# Make it executable
chmod +x claude-code-jumpstart.sh
# Or run with bash
bash claude-code-jumpstart.shScript will warn you:
Warning: .claude/ directory already exists.
Overwrite? (y/n)
Choose n to keep existing setup, or y to regenerate.
Script creates git-related files only if git is available.
If git command not found, script skips git integration.
Q: Can I run it multiple times?
A: Yes! Re-run to regenerate based on new answers. Back up first if you've customized.
Q: Will it overwrite my existing setup?
A: It asks before overwriting. Answer 'n' to keep existing.
Q: What if I picked wrong answers?
A: Just re-run the script. Or manually edit the generated files.
Q: Can I customize the generated files?
A: Absolutely! They're meant to be customized. Start with generated, then evolve.
Q: Does it work on Windows?
A: Requires bash. Use Git Bash, WSL, or run on Mac/Linux.
Q: What if my language isn't listed?
A: Choose "Other" - creates generic setup you can customize.
Q: Can I add silent mode parameters later?
A: Currently interactive only. Silent mode is for future enhancement.
The script is ~600 lines of bash with:
- Input validation
- Conditional logic for personalization
- Template generation
- Colored output
- Error handling
Fully open source - customize for your organization!
As Claude Code evolves:
- Update agent templates
- Add new commands for new features
- Update CLAUDE.md templates
- Improve decision logic
Community contributions welcome!
"Before: everyone configured differently, spent 2 hours setting up. After: jumpstart creates team baseline in 5 minutes. Saved 10 hours (5 devs)." - Tech Lead
"New hires run jumpstart, get personalized guide, up and running in 15 minutes vs 2-3 days of documentation reading." - Engineering Manager
"Had Claude Code installed for weeks but never started. Jumpstart got me past the 'blank page' problem. Now using it daily." - Solo Developer
| Approach | Time | Customization | Beginner-Friendly |
|---|---|---|---|
| Read Full Docs | 2-3 hours | Full | No |
| Copy Template | 30 min | Partial | Medium |
| Jumpstart Script | 5 min | Smart | Yes |
| Manual Setup | 1 hour | Full | No |
Jumpstart = 80% value, 20% effort
- Main Best Practices Guide
- Agent Files - Reference for what gets created
- CLAUDE.md Template - Full manual template
- Quick Start - Commands reference
Ideas to improve the script:
- Add more project types (Rust, Elixir, etc.)
- Better detection of existing tools
- Import from package.json/requirements.txt
- Team templates repository
- VSCode/JetBrains plugin integration
- Analytics to improve recommendations
PRs welcome!
MIT - Use freely, modify as needed, share with your team.
Get started: Download and run ./claude-code-jumpstart.sh in your project! 🚀