Files
Andrew Yim 2ee018a146 docs(our-gdrive-organizer): add 3 gotchas from Brand in Action audit
- D_intelligence (underscore) — typo, NOT a regex variant. Fix one-off
  via mv; do not widen RENAME_RULES (false-positive risk on legit
  underscore-separator filenames).
- Externally-generated filenames vs OurDigital convention. Default to
  normalize {Client}_/Client_/client_ → CLIENT- inside Active Workspaces;
  drop 14-digit timestamps to YYYYMMDD; preserve only when an external
  system requires the literal name.
- Reference library naming inconsistency — DO NOT bulk-normalize. Mixed
  naming reflects source provenance (Slideshare slugs, vendor whitepapers,
  Korean blog captures). Group by topic into subfolders instead
  (frameworks/, examples/, ko/) when count exceeds ~15 at root.

Patterns library now at 15 gotchas. Validated by live application during
01_Brand in Action audit.

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

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.