đ Structure
Folder Structure
The complete folder layout for your machine. Colours show stability: blue = folders, green = stable files, yellow = CLAUDE.md files, red = ephemeral, purple = skills.
Global Claude Config â Always Loaded
C:\Users\matt_\ â âââ .claude\ â Global Claude Code config (auto-created) âââ CLAUDE.md â Writing style, your role, global prefs âââ memory\ â Auto-managed by Claude â do not edit â âââ MEMORY.md â Auto index of all memory files âââ commands\ â Global skills (always available) âââ clone-repo.md â /clone-repo â delete and re-clone a repo for a new session âââ create-customer.md â /create-customer â create a new customer workspace âââ create-project.md â /create-project â create a new project under a customer âââ create-repo.md â /create-repo â first-time repo setup for a project âââ fabric-cicd-setup.md â /fabric-cicd-setup â set up Fabric CI/CD pipeline âââ handover.md â /handover â save a structured session handover note âââ update-handover.md â /update-handover â update an existing handover note
Everything in
~/.claude/ is available in every session from every folder. This is where your writing style and global skills live. Work Root â Disseminate Limited
C:\Users\matt_\OneDrive\Claude\ â Stable working root (create this) â âââ CLAUDE.md â Disseminate context: stack, standards, structure â âââ _claude-guide\ â My Claude Compass (this website) â âââ assets\ â âââ index.html â âââ ... â âââ _global\ â Global Claude config (symlinked from ~/.claude) â âââ CLAUDE.md â Writing style, rules, global preferences â âââ memory\ â Memory files (always loaded) â âââ commands\ â Global skills / slash commands â âââ _output\ â Root-level Claude outputs and handover notes â âââ _temp\ â Temporary uploads: screenshots, files to share with Claude â âââ Customers\ â âââ CustomerA\ â â âââ CLAUDE.md â Customer: env names, contacts, workspace IDs â â âââ _temp\ â Screenshots, files to share with Claude (this customer) â â âââ _context\ â Stable reference â never deleted â â â âââ urls-connections.md â Fabric endpoints, DevOps URLs â â â âââ security-notes.md â â Non-secret config only â â â âââ architecture.md â â â â â âââ Project1\ â OPEN THIS for Project1 work â â â âââ CLAUDE.md â Project scope, tables, naming â â â âââ _temp\ â Screenshots, files to share with Claude (this project) â â â âââ .claude\ â â â â âââ commands\ â Project-specific skills â â â âââ _context\ â â â â âââ design-docs\ â Upload design docs here â â â âââ _output\ â Claude responses, generated docs â â â âââ Project1.code-workspace â Multi-root VS Code workspace â â â âââ repos\ â All clones live here â â â âââ Project1-Bronze\ â git clone (ephemeral) â â â âââ Project1-Silver\ â git clone (ephemeral) â â â âââ Project1-Gold\ â git clone (ephemeral) â â â âââ Project1-PowerBI\ â git clone (ephemeral) â â â â â âââ Project2\ â â â âââ ... same structure ... â â â â â âââ _powerbi-crossproject\ â Cross-project PBI (spans all projects) â â âââ repos\ â â âââ CustomerA-PowerBI\ â Refresh less often than project repos â â â âââ CustomerB\ â âââ ... same structure ... â âââ Disseminate\ â Work done on the business (not for clients) â âââ CLAUDE.md â Internal context, business goals â âââ _assets\ â Logo, branding, images, brand guidelines â âââ _templates\ â Proposal, SoW, report and email templates â âââ _admin\ â Contracts, insurance, company documents â âââ Projects\ â Internal projects with defined scope â âââ Personal\ âââ CLAUDE.md â Personal: learning goals, tech stack âââ Projects\ âââ App1\ âââ App2\
Stability Reference
| Folder / File | Stable? | Rule |
|---|---|---|
~/.claude/ |
Permanent | Never delete. Auto-managed by Claude Code. |
CLAUDE.md files at any level |
Permanent | Live outside repos. Always preserved. |
_context\ folders |
Permanent | Design docs, URLs, notes. Never inside a repo. |
_output\ folders |
Semi-stable | Claude's outputs. Keep until no longer needed. |
.code-workspace files |
Permanent | Lives at project root above repos\. Survives re-clones. |
repos\ProjectX-Bronze\ |
Ephemeral | Delete and re-clone freely. Nothing important here. |
Your Repo Workflow
Since you delete and re-clone repos rather than keeping them long-lived, the key rule is: the project folder above repos\ is your stable anchor.
| Step | Action | Location |
|---|---|---|
| 1. Start work | Clone into repos\ subfolder | Project1\repos\Project1-Bronze\ |
| 2. Open VS Code | Open workspace file (not the repo) | Project1\Project1.code-workspace |
| 3. Work with Claude | Claude has full context cascade | Reads CLAUDE.md at project â customer â Kerv |
| 4. Commit & PR | Commit, push, raise PR in Azure DevOps | Normal git workflow |
| 5. Done for now | Delete the repo folder | Project1\repos\Project1-Bronze\ deleted |
| 6. Next session | Re-clone into same subfolder name | Workspace file reconnects automatically |
Because the
.code-workspace file uses relative paths like "path": "repos/Project1-Bronze", re-cloning with the same folder name instantly reconnects all roots in VS Code.