Hidden Folder Audit

When to Use

Repository has accumulated multiple hidden folders over time
Multiple AI/agent configuration directories exist (.agent-os/, .ai/, .claude/)
Symlinks point to non-existent targets
Unclear which configuration is authoritative
Preparing for repository restructure or cleanup
After inheriting or forking a repository
Before establishing new folder standards

1.2.0 (2026-01-20): Added Related Directory Patterns section
- Added benchmarks/ entry to reference table (SPLIT action)
- Added Related Directory Patterns section for non-hidden directories
- Added specs/archive/ as standard location for completed plans
- Added benchmarks/ separation pattern (fixtures vs generated outputs)
- Updated verification commands for new patterns
1.1.0 (2026-01-20): Updated reference table and added verification commands
- Updated Common Hidden Folders Reference table with verified recommendations
- Added .drcode/ as DELETE (confirmed legacy AI config)
- Added .slash-commands/ as CONSOLIDATE to .claude/docs/commands/
- Added .git-commands/ as CONSOLIDATE to scripts/git/
- Added .benchmarks/ as DELETE (usually empty)
- Added .githooks/ as KEEP (standard location)
- Added Verification Commands section with:
  - Verify Hidden Folder State commands
  - Verify Consolidation Targets commands
  - Verify Git Status commands
  - Final State Checklist script
- Added Notes column to reference table for additional context
1.0.0 (2025-01-20): Initial release based on digitalmodel repository hidden folder audit session