Projects Folder & Repo Organization¶
Status: Active (monolith → multi-repo migration in progress) Project: Operations · General
What this is¶
The story of how Sam's Projects/ working directory evolved from an
unorganized local folder into a single Git repo, then into a
well-organized monolith, and most recently into a multi-repo split
that separated concerns across Website_project, Litify_AI_Integration_Project,
Template-Refresh_project, Marketing_project, and others.
Every Claude/Cowork session reads from and writes to this workspace, so keeping it orderly is foundational — a messy workspace creates drift, duplicates, and hard-to-find files faster than any agent can be taught to navigate it.
Timeline¶
March 3 — Git Repo Organization and GitHub Setup for All Project
Folders. First pass: standardized folder naming, added git, pushed
to GitHub. Established the samaguiar1982-cpu/projects remote as the
single source of truth.
March 11-13 — Projects Folder Cleanup, Git Init, GitHub Setup, and
Agent Briefing System. Rewrote the folder structure, added the
Agent Briefing System (agents should read CLAUDE.md + subfolder
CLAUDE.md files before starting work), and finalized the monolith
layout.
April 7 — Workspace V2 Bootstrap and Template Repo Thinning. Started V2 of the workspace structure, thinned out the template reference repos that weren't being used.
April 7 — Projects Folder Cleanup + Server Migration Log Consolidation. Parallel to V2 bootstrap, consolidated server migration logs that had been scattered.
April 12 — Projects Monolith to Multi-Repo Migration. The big split: broke the monolith into multiple repos to reduce accidental cross-project damage and let each project have its own CI/hooks.
April 9 — Repo Cleanup Session 2: Template-Refresh Split & GitHub Reconciliation. Repo-level cleanup focused on the template-refresh split.
April 12 — Batch Clone 28 GitHub Repos to Reference-Repos Folder.
Cloned 28 related repos into a reference-repos/ folder as read-only
references so agents could look at them without touching them.
What's in each project directory (current state)¶
Website_project/— WordPress content, pages, templatesLitify_AI_Integration_Project/— Salesforce / Litify field exports, scripts, dashboardsMarketing_project/— branding, ads, contentGoogle_Ads/— Google Ads campaigns, skills, exportsAdmin_projects/— session logs, handoffs, firm admin docsSkills_Library/— Claude skill definitions (the live library)UPS-Case_project/— active case materials (LaDuke)Template-Refresh_project/— template batch intake and QAagent-playbook/— runbook for agents.credentials/— vault (gitignored)
Related: recurring organizational hygiene¶
- Downloads Cleanup (multiple passes) — Sam's Downloads folder gets noisy; 3-pass organization scripts keep it sane
- Mac File Cleanup — Desktop/Documents/Downloads organization
- S-drive duplicate cleanup sweep — shared drive dedup
- Projects Folder Major Cleanup: 132 Files Organized (April 2026) — 132 stray files rehomed in a single pass
Sources¶
- Git Repo Organization and GitHub Setup for All Project Folders (March 3, 2026)
- Projects Folder Cleanup, Git Init, GitHub Setup, and Agent Briefing System (March 11-13, 2026)
- Workspace V2 bootstrap and template repo thinning - 2026-04-07
- Projects Folder Cleanup + Server Migration Log Consolidation - 2026-04-07
- Projects Monolith to Multi-Repo Migration - 2026-04-12
- Batch Clone 28 GitHub Repos to Reference-Repos Folder (April 12, 2026)
- Repo Cleanup Session 2: Template-Refresh Split & GitHub Reconciliation
- Projects Folder Major Cleanup: 132 Files Organized (April 2026)
- S-drive duplicate cleanup sweep - 2026-04-07