Freelancer Toolkit for Claude Code

A collection of production-ready Claude Code slash commands built for freelance developers. Stop writing boilerplate, chasing scope creep, and formatting client emails by hand — let Claude handle it.

---

Commands

Command	What it does
/project-init	Scaffold a new client project with the right structure
/code-review	Get a structured code review of all changed files
/deploy-checklist	Verify your project is safe to ship
/client-report	Generate a plain-English progress report for your client
/estimate	Estimate hours, complexity, and rate for any task

---

Installation

Requirements: Claude Code installed and authenticated.

Option 1: Use in any existing project

# Clone this repo
git clone https://github.com/your-username/freelancer-toolkit.git

# Copy the .claude folder into your project
cp -r freelancer-toolkit/.claude /path/to/your-project/

# Open your project with Claude Code
cd /path/to/your-project
claude

Option 2: Use globally (all your projects)

# Copy commands to your global Claude config
cp -r freelancer-toolkit/.claude/commands ~/.claude/commands/

After installation, all commands are available inside any Claude Code session. Type / to see them in the autocomplete menu.

---

Command Reference

/project-init

Scaffolds a new client project from scratch. Ask for project name and tech stack, then creates a complete, production-ready folder structure.

Usage:

/project-init
/project-init acme-api python
/project-init shopify-bot node

Creates:

my-project/
├── src/
├── tests/
├── .env.example        # All environment variables documented
├── .gitignore          # Stack-appropriate
├── README.md           # With setup instructions
├── requirements.txt    # (Python) or package.json (Node)
└── [git initialized with first commit]

Example output:

Project initialized: acme-api

  src/              ✓
  tests/            ✓
  .env.example      ✓
  .gitignore        ✓
  README.md         ✓
  requirements.txt  ✓

Git: initialized with 1 commit

Next steps:
  1. Copy .env.example → .env and fill in your values
  2. git remote add origin <url> && git push -u origin main

---

/code-review

Acts as a senior code reviewer. Analyzes all files changed since your last commit and produces a structured report with severity levels.

Usage:

/code-review                    # All git-changed files
/code-review src/payments.py    # Specific file
/code-review src/               # Specific directory

Checks for:

• Bugs and logic errors
• Security vulnerabilities (injections, hardcoded secrets, missing auth)
• Performance issues (N+1 queries, unbounded loops)
• Code style and maintainability
• Missing error handling

Example output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 CODE REVIEW REPORT
 2024-11-15  ·  3 files reviewed  ·  main
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SUMMARY
  🔴 Critical  : 1
  🟡 Warning   : 2
  🔵 Info      : 1

FINDINGS
────────────────────────────────────────────────
src/auth.py

  [CRITICAL] Hardcoded secret key
  Line 12: SECRET_KEY = "abc123supersecret"
  → Move to environment variable

VERDICT:  BLOCKED

---

/deploy-checklist

Scans your project before deployment. Catches the things that get you at 2am: exposed secrets, missing env docs, unpinned dependencies.

Usage:

/deploy-checklist
/deploy-checklist staging
/deploy-checklist production

Checks:

• All .env variables are documented in .env.example
• No hardcoded secrets, API keys, or credentials in source code
• Dependency lock files are present and versions are pinned
• Ports and hosts are environment-driven, not hardcoded
• README has deployment instructions
• No pdb, debugger;, or stray console.log in production code
• Test suite exists
• Docker configuration is correct (if applicable)

Example output:

  ✅ PASS   Environment variables documented
  ❌ FAIL   Hardcoded secret found — src/config.py:14
  ✅ PASS   Lock file present (requirements.txt)
  ⚠️  WARN   README missing deployment section
  ✅ PASS   Port configured via environment variable
  ✅ PASS   No debug code detected

RESULT: 🚫 NOT READY TO DEPLOY  ·  1 fail  ·  1 warning

---

/client-report

Reads your git log and generates a polished, plain-English progress report you can send directly to your client — no technical jargon.

Usage:

/client-report              # Last 10 commits
/client-report 20           # Last 20 commits
/client-report --since "2024-01-01"
/client-report --save       # Also writes to client-report-{date}.md

Translates commits like:

• fix: resolve n+1 query in user endpoint → "Improved loading speed for the user list page"
• feat: implement OAuth2 with Google → "Built secure Google login so users can sign in with their Google account"
• chore: update dependencies → (omitted or noted as maintenance)

Example output:

# Project Progress Report
**Period:** Nov 1 – Nov 15, 2024

## Work Completed
- **User Authentication** — Built secure login with Google sign-in.
- **Dashboard** — Created main dashboard with account activity and metrics.
- **Performance** — Key pages now load ~40% faster.

## By the Numbers
| Metric | Value |
|--------|-------|
| Updates shipped | 12 |
| Files modified | 23 |
| Lines of code added | 847 |

---

/estimate

Give it a task description, get back an honest estimate with hours, complexity, rate range, and risks.

Usage:

/estimate Add Stripe payment integration to the checkout flow
/estimate Fix the bug where users are logged out after 10 minutes
/estimate Build a REST API for a mobile app with user auth and CRUD for posts

Example output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 TASK ESTIMATE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TASK
  Add Stripe payment integration to the checkout flow

ESTIMATE
  Complexity    ████████░░  MEDIUM
  Hours         8h – 20h  (most likely: 12h)
  Rate range    $80 – $130 / hr
  Project value $640 – $2,600

RISKS
  🔴 Stripe webhook reliability in dev environment
  🟡 Client hasn't confirmed which payment methods are needed
  🔵 Does this need refunds/partial refunds? Not in scope.

RECOMMENDATION
  Charge for the pessimistic range. Stripe integrations
  always surface edge cases after initial testing.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

---

Screenshot

$ claude
> /estimate Build a dashboard with real-time data updates

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 TASK ESTIMATE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  Complexity    ██████████  HIGH
  Hours         24h – 60h  (most likely: 38h)
  Rate range    $100 – $175 / hr
  Project value $2,400 – $10,500
...

(Replace this block with an actual screenshot of Claude Code in your terminal)

---

Contributing

Found a bug or have a command idea? Open an issue or PR. Keep commands:

• Self-contained (no external dependencies)
• Focused on a single job
• Written for real freelance workflows

---

License

MIT — use freely, modify freely, ship confidently.

---

Built with Claude Code