Files
Andrew Yim c750fa7f5e feat(our-gdrive-organizer): add new skill at slot 82, rename old 82 → 92
New Python CLI + dual SKILL.md (Code + Desktop) for organizing Google
Drive folders under OurDigital conventions:

- Refresh root README index (preserves manual Topics/Notes between
  AUTO-STRUCTURE markers)
- Ensure per-subfolder README.md meta files
- Propose filename + folder renames (D.intelligence → OurDigital with
  SEO-context caveat documented in patterns/gotchas.md)
- Propose moves for cluttered files (screenshots, temp downloads)
- Sensitive-folder skip list (04_Case Studies, 99_Project Archive,
  *Archive*, 진단*)
- shared/patterns/ gotcha library: canonical-files, canonical-folders,
  categorization-rules, 12 known gotchas — grows over time as the
  system encounters new edge cases

Slash command: /organize. CLI: ~/.local/bin/our-gdrive-organize.

82-tui-design-template renumbered to 92 (no content change) to free
slot 82. AGENTS.md and CLAUDE.md updated for both moves.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 23:02:45 +09:00

1.4 KiB

Patterns library — gotcha folder

The "gotcha folder" Claude consults when doing content-based reorganization. Filename pattern matching is handled deterministically by code/organizer.py; this folder is for the judgment-calls Claude makes when reading file contents to decide where something belongs.

Files

  • canonical-files.md — examples of well-named files in their proper homes. When Claude sees a file and isn't sure where it goes, it pattern-matches against these canonical examples.
  • canonical-folders.md — well-organized folder shapes. What goes in 02_SEO Audit Toolkit/ vs 03_SEO Hack Library/ vs 99_Project Archive/.
  • categorization-rules.md — explicit IF→THEN rules for placement decisions. These trump heuristics; if a rule applies, follow it.
  • gotchas.md — edge cases, ambiguous files, common mistakes, and how to resolve them.

How to extend

When the user encounters a new edge case or pattern that the script can't handle automatically, add it here:

  1. If the rule is deterministic (filename pattern → action), put it in code/organizer.py (RENAME_RULES, MOVE_RULES) and document in shared/conventions.md.
  2. If the rule is judgment-based (read content, decide), add a new entry here and reference it from code/SKILL.md's content-based workflow.

The patterns library should grow over time as Claude + user encounter more edge cases. Each addition is a "gotcha" the system has learned.