FOLDER STRUCTURE · v0.7.7

Project folder structure

How Punch projects live on Google Drive. Clients 2.0 is the team root; every client gets a folder with workstream subfolders (_Digital / _Physical / _Website); _Website is where the Punch website scaffold lives. The underscore prefix sorts these to the top alphabetically.

Team convention: every Punch project lives in Google Drive at My Drive / Clients 2.0 / [Name] Client / _Website /, mounted locally via Google Drive for Desktop with the project folder marked Available offline. The website scaffold (brand, source, content, sandbox, assets) is created automatically inside _Website/ by punch-project-init. See the Google Drive Setup Guide for one-time setup.
Google Drive — manually created, organized by humans
▾My Drive/ Google Drive root (synced via Google Drive for Desktop)
└─▾Clients 2.0/ Team root. Shared with all of Punch. Pin to Finder sidebar. SHARED
├─▸_Claude Master Skills/ Shared reference for the plugin / skills / canonical templates. Read-only for most.
└─▾[Name] Client/ One folder per client. Underscore-prefixed workstreams below.
├─▸_Digital/ Digital-channel workstream (ads, email, social).
├─▸_Physical/ Physical / print collateral workstream.
└─▾_Website/ Where Cowork mounts. The Punch website scaffold lives here.
Inside _Website — created by punch-project-init
├─·README.md Project meta: client info, sectors, tier mix, dev target. AUTO
├─▾brand/ Creative direction + voice for this project
├─·copy-brief.md Big Idea, voice notes, banned + preferred words
├─·theme-notes.md Picked creative theme direction
└─·visual-direction.md Decoded references, palette, surface, type discipline
├─▾source/ Authoritative client material — required for factual pages. PM OWNS
├─·README.md Explains the auto-discovery convention
├─·_missing.md Auto-maintained chase list. PM ticks off as files land. AUTO
├─▸products/ Subfolder by topic (per product, per page, per theme — your call)
│ └─·hub-tech-spec.pdf Example: client-provided data sheet
├─▸case-studies/
└─▸compliance/
├─▾content/ Strategist's working space — page briefs + sitemap
├─·sitemap.yaml The site's pages
├─·homepage.md First page brief — others follow this pattern
├─·products-cerux-kos.md Per-page briefs. Citations + MISSING SOURCE markers
├─·_brief-template.md Template to copy when adding new page briefs
└─·assets-manifest.yaml Asset → page+section map (verified by punch-asset-audit)
├─▾sandbox/ Where Cowork builds. Skills write here.
├─·tokens.css Generated by punch-token-export from Figma
├─·text-styles.css Generated by punch-component-export (with line-break auto-layer)
├─·components.html Generated by punch-component-export
├─·index.html Composed homepage
└─▸wireframe/ Generated by punch-wireframe. Newspaper-greyscale. Reading material.
└─▾assets/ Logo variants + project-specific images
├─·logo-full-color.svg Default. Used by nav + footer.
├─·logo-reverse.svg
├─·logo-white.svg
├─·logo-mark-full-color.svg
└─·logo-mark-white.svg

The two layers

Humans create the green-pill layer once per client. The CCO (or whoever's onboarding the new client) creates [Name] Client / inside Clients 2.0 /, then the workstream subfolders (_Digital, _Physical, _Website). This is a 30-second setup.

Claude creates the red-pill layer via punch-project-init. Once you mount _Website / in Cowork, run the project-init prompt and the entire website scaffold (brand, source, content, sandbox, assets) lands inside it with templated stub files. "Initialize a new Punch project for [Client Name]. Scaffold the standard folder structure with the templated stub files."
▸Clients 2.0/
The team root in Google Drive. Shared with everyone at Punch. All client work — every workstream, every project — lives under here.
▸_Claude Master Skills/
Shared reference for the punch-website plugin and any team-wide skill templates. Read-only for most.
▸_Website/
The workstream folder Cowork mounts. The website scaffold (brand/source/content/sandbox/assets) lives inside it.
▸brand/
Creative direction, voice notes, decoded references. Strategist + Lead Designer own.
▸source/
Client-provided authoritative material — data sheets, specs, capability docs. Required for any factual page brief. PM owns. Auto-discovered by the skills.
▸content/
Sitemap + per-page content briefs. Strategist owns. Briefs carry <!-- source: ... --> citations and MISSING SOURCE markers.
▸sandbox/
Where Cowork composes. Tokens, components, the wireframe, the composed pages. Skills write here; humans edit only in polish phase.
▸assets/
The five logo variants + project-specific imagery. Logos exported by punch-component-export from the Figma fork's Brand Marks group.