
Scratch Workspace
- 37 installs
- 186 repo stars
- Updated July 19, 2026
- thebushidocollective/han
Helps with ai & agent building tasks during AI-assisted development.
About
scratch-workspace is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- scratch-workspace
- AI & Agent Building
- AI-coding skill
Scratch Workspace by the numbers
- 37 all-time installs (skills.sh)
- Ranked #8,545 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/thebushidocollective/han --skill scratch-workspaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 37 |
|---|---|
| repo stars | ★ 186 |
| Last updated | July 19, 2026 |
| Repository | thebushidocollective/han ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Scratch Workspace Management
This skill covers proper use of the .claude/.scratch/ directory for temporary, exploratory, and draft work.
Purpose
The scratch workspace provides a gitignored location for:
- Draft implementations
- Experimental code
- Temporary test files
- Planning documents
- Any work-in-progress that shouldn't be committed
Setup Checklist
Before creating scratch files:
1. Ensure directory exists
mkdir -p .claude/.scratch2. Verify gitignore
Check .gitignore contains:
.claude/.scratchIf missing, add it:
echo '.claude/.scratch' >> .gitignoreDirectory Structure
Organize scratch files by purpose:
.claude/
├── .scratch/
│ ├── drafts/ # Work-in-progress implementations
│ │ └── feature-x.ts
│ ├── experiments/ # Exploratory code
│ │ └── perf-test.js
│ ├── notes/ # Planning and notes
│ │ └── architecture.md
│ └── temp/ # Truly temporary files
└── settings.json # Claude settings (NOT scratch)Best Practices
DO
- Create subdirectories for organization
- Use descriptive file names
- Clean up when work is complete
- Move finalized code to proper project locations
DON'T
- Put sensitive data in scratch (still on disk)
- Use scratch for files that should be committed
- Leave stale scratch files indefinitely
- Put scratch files outside
.claude/.scratch/
Workflow
Starting Exploratory Work
# Create scratch area
mkdir -p .claude/.scratch/experiments
# Work on experiment
# ... create files in .claude/.scratch/experiments/Promoting to Real Code
When scratch work is ready:
1. Review and refine the code 2. Move to appropriate project location 3. Delete scratch version 4. Commit the promoted code
Cleanup
Periodically clean scratch:
# Review what's in scratch
ls -la .claude/.scratch/
# Remove old experiments
rm -rf .claude/.scratch/experiments/old-test/Integration with Other Tools
With Git
The .claude/.scratch directory is gitignored, so:
git statuswon't show scratch filesgit add .won't stage scratch files- Scratch files won't appear in commits
With IDE
Most IDEs will show .claude/.scratch in the file tree. You can:
- Add to IDE's exclude patterns
- Keep visible for easy access
- Use IDE's "mark as excluded" feature
Common Patterns
Draft Implementation
.claude/.scratch/drafts/
└── new-feature/
├── index.ts
├── types.ts
└── test.tsPerformance Experiment
.claude/.scratch/experiments/
└── perf-comparison/
├── approach-a.ts
├── approach-b.ts
└── benchmark.tsArchitecture Notes
.claude/.scratch/notes/
└── refactor-plan.mdTroubleshooting
Scratch files appearing in git status
# Verify gitignore entry
grep -r ".claude/.scratch" .gitignore
# If missing, add it
echo '.claude/.scratch' >> .gitignoreDirectory doesn't exist
mkdir -p .claude/.scratchAccidentally committed scratch files
# Remove from tracking but keep locally
git rm -r --cached .claude/.scratch
git commit -m "chore: remove scratch files from tracking"