tomevault-io Slop Detector
Analyze repository architecture to identify structural slop: excessive layering, fragmentation, and organizational overhead.
Workflow
1. Run Architecture Scan
bash /path/to/skill/scripts/analyze-slop.sh <repository-path> [output-dir]
- Default output:
./docs/slop-report-YYYYMMDD-HHMMSS.md - Creates
docs/folder if missing
2. Patterns Detected
| Pattern | Problem | Fix |
|---|---|---|
| 🪆 Deep nesting (5+ levels) | Hard to navigate | Flatten structure |
| 📁 Single-file directories | Unnecessary fragmentation | Move file up or merge |
| 🛢️ Barrel files (index.ts) | Circular deps, bundle bloat | Direct imports |
| 🕳️ Empty directories | Dead code | Remove |
| 🏢 Enterprise layers | Passthrough overhead | Consolidate or justify |
| 🪞 Mirrored structures | Same entity in many places | Colocate by feature |
| 📝 Centralized types | Scattered from implementation | Colocate with code |
| 🧰 Utils/helpers folders | Dumping grounds | Move to consumers |
3. Review Checklist
For each flagged item, ask:
- Layers: What value does this layer add? (validation, caching, logging, transformation)
- Directories: Could this folder be flattened or merged?
- Separation: Should these files be colocated by feature instead?
Pattern Reference
See references/slop-patterns.md for:
- Architecture anti-patterns with examples
- Feature-based vs layer-based organization
- When layering is justified
Output
Report saved to docs/slop-report-YYYYMMDD-HHMMSS.md with:
- Issues by category
- Summary metrics (dirs, files, depth)
- Actionable recommendations
Converted and distributed by TomeVault — claim your Tome and manage your conversions.