Andrew Yim
c750fa7f5e
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>
3.5 KiB
3.5 KiB
Canonical folder shapes
What "well-organized" looks like at each level. Use these as anchors when deciding whether to create a new subfolder or which existing one a file should live in.
Top-level practice area (e.g., 02_SEO in Action/)
NN_Practice Area/
├── README.md # auto-indexed root
├── 00_Brand Management/ # 00–05: frameworks / always-on
├── 01_Active Workspaces/ # current client engagements
├── 02_{Practice} Audit Toolkit/ # reusable audit assets
├── 03_{Practice} Hack Library/ # external reference / research
├── 04_Case Studies/ # past engagement portfolio
├── 05_Working Template/ # blank quote/audit/coaching templates
├── 10_{Productized Tool}/ # 10–13: productized specialty
├── 11_{Specialty Module}/
├── 20_{Data Source}/ # 20s: data integrations
├── 98_Training/ # 98: training materials
└── 99_Project Archive/ # 99: completed engagements
Maturity convention by NN range:
- 00–05: foundational / framework / always-on
- 10–13: productized tools / specialties
- 20–29: data integrations
- 90–99: archive / training / closed work
Active workspace shape (01_Active Workspaces/)
01_Active Workspaces/
├── README.md
├── 00_{Client A}/
│ ├── {client-prefix}-{deliverable}-{date}.{ext}
│ ├── [Note] {topic} {date}.gdoc
│ └── AI Reference/ # if engagement uses AI tools
└── 01_{Client B}/
└── ...
Each client gets one subfolder, NN-prefixed in chronological onboarding
order. Files use a short client prefix (e.g., JAM- for Jamie, SLA- for
신라호텔, JHR- for 조선호텔).
Case study shape (04_Case Studies/)
Flat — files at the root, no subfolders:
04_Case Studies/
├── README.md
├── {ClientName} SEO {DeliverableType}.pdf
├── {ClientName} {DeliverableType} {date}.gdoc
└── ...
Each file is a portfolio-quality deliverable. No working files here.
Project archive shape (99_Project Archive/)
99_Project Archive/
├── README.md
├── 01_{First archived client}/
│ ├── 00_{topic}/ # may have its own NN-prefixed subfolders
│ ├── 09_사전 진단 / # diagnostic phase
│ ├── 10_계약 관련/ # contract phase
│ ├── 90_고객사 수급자료/ # client-supplied materials
│ └── {original-filename}.{ext} # plus loose root files
└── 02_{Second archived client}/
└── ...
Sub-folder structure inside each archived client mirrors the original engagement folder layout — nothing renamed or normalized.
Audit toolkit shape (02_SEO Audit Toolkit/)
02_{Practice} Audit Toolkit/
├── README.md
├── 참고 자료/ # references
├── 예시 자료 모음/ # neutralized example deliverables
├── 문서 양식/ # blank document forms
├── 교육 자료/ # internal training assets
├── {tool}_standard check_{date}/ # versioned tool snapshots
├── Google Business Profile/ # specialty subdomain
├── robots.txt/ # specialty subdomain
└── sitemap.xml/ # specialty subdomain
Subfolders here are topic-grouped reusable assets. Each subfolder is purpose-named (Korean OK) — not NN-prefixed because order doesn't matter.