Cleanup Guide
Smart cleanup utility for migrated projects. Remove legacy files and maintain a clean RAPIDS-optimized structure.
📖 Overview
rapids-clean removes old project files and documentation after migrating to RAPIDS framework. It helps you maintain a clean, RAPIDS-optimized project structure.
⏰ When to Use
🚀 Usage
# After migrating your project
cd your-project/
rapids-migrate
# Then clean up old files
rapids-clean🧹 What Gets Cleaned
Legacy Documentation
• README.old.md
• CONTRIBUTING.old.md
• docs/old/**
• docs/legacy/**
Environment Files
• .env.local
• .env.production
• .env.development
• .env.example
Build Artifacts
• .next/ - Next.js build cache
• dist/ - Build output (regenerated on build)
• build/ - Build output
• __pycache__/ - Python cache
• *.pyc - Python bytecode
• .pytest_cache/ - Pytest cache
Replaced Helper Scripts
• scripts/setup.sh
• scripts/init.sh
• scripts/bootstrap.sh
• bin/setup
• bin/init
Old CI/CD Configs
• .travis.yml
• .circleci/
• azure-pipelines.yml
Migration Artifacts
• .claude.backup/ - Backup created during migration
🛡️ Safety Features
Pre-Cleanup Verification
• Checks if RAPIDS has been initialized (.claude/ and CLAUDE.md exist)
• Will not run on non-RAPIDS projects
• Shows preview of items to be removed before cleaning
Cleanup Log
All removed items are logged to .rapids-cleanup.log with:
• Timestamp
• Item path
• Reason for removal
• Size freed
• Success/failure status
Size Reporting
Shows total disk space that will be freed before cleanup
📺 Output Example
⚡ RAPIDS Clean Found 12 items to clean up: 📄 .env.local - Use .env only (per CLAUDE.md) (1.2 KB) 📄 .env.production - Use .env only (per CLAUDE.md) (980 B) 📁 .next/ - Next.js build cache (45.3 MB) 📁 __pycache__/ - Python cache (2.1 MB) 📄 scripts/setup.sh - Replaced by RAPIDS migration (3.4 KB) 📁 .claude.backup - Migration backup (15.2 KB) ... and 6 more items Total space to free: 47.7 MB ⚡ Starting cleanup in 2 seconds... (Log will be saved to .rapids-cleanup.log)
💡 Philosophy
✅ Non-Destructive
🔄 Workflow
┌─────────────────┐
│ Existing Project│
└────────┬────────┘
│
▼
┌─────────────────┐
│ rapids-migrate │ ← Sets up RAPIDS
└────────┬────────┘
│
▼
┌─────────────────┐
│ rapids-clean │ ← Removes old files
└────────┬────────┘
│
▼
┌─────────────────┐
│ Clean RAPIDS │
│ Project │
└─────────────────┘❓ FAQ
Q: Can I run rapids-clean multiple times?
A: Yes. It's idempotent - subsequent runs will find nothing to clean.
Q: What if I need a file that was removed?
A: Check .rapids-cleanup.log for the complete list. Most removed files are regenerated on build or replaced by RAPIDS patterns.
Q: Does it remove node_modules/?
A: No. Package dependencies are never removed. Use npm/yarn/pnpm prune for that.
Q: What about my custom scripts?
A: Only common setup/init scripts are removed. Custom build or utility scripts are preserved.