The new process is here.
The website system we've been talking about in Slack and at all-hands. Same craft, same Fusion — but now built around Cowork and the punch-website plugin, validated as a content-first wireframe before any page is designed, and shipped with structural QA at every gate. Start with At a Glance below.
punch-website plugin · install via Cowork's plugin manager.
The high-level deltas in how Punch ships work. The phase paragraphs in At a Glance go deeper; this is the snapshot for skim-readers.
-
Before
Copy lived in Google Docs. Clients reviewed copy in one place, design in another, and reconciling the two was its own project.
→NowPer-page briefs land in
content/*.mdand pour into a content-first wireframe. Clients read and sign off on the entire site before any page is designed. -
Before
Pages were designed straight in Figma from a Webflow template, then handed to dev. Compositional decisions made in Figma rarely matched the build.
→NowTokens and components export from Figma into a sandbox. Pages are composed in Cowork against those exports — so the build matches the design system, not Cowork's guess at it.
-
Before
The Creative Brief, the three theme directions, and the sitemap took days of manual synthesis from kickoff transcripts and brand docs.
→NowStrategy skills first-pass all three from discovery materials. Strategist time goes to refining the argument, not staring at a blank Google Doc.
-
Before
The standard 80% of pages got the same designer attention as showcase pages — or worse, got rushed at the end.
→NowStandard pages are amplified from the homepage rhythm by Production Artists. Designer time freed up here goes to custom heroes, motion, and photography.
-
Before
Copy checks, link checks, asset audits, and accessibility — all eyeballed at the end of the project by whoever was free.
→NowOne orchestrated pre-launch QA report covers all of it. Production is verified within 48 hours of launch instead of waiting for the client to spot something.
-
Before
End of project meant moving to the next thing. Lessons stayed in people's heads.
→NowA 20-minute retrospective at the end of every project captures what fired and what didn't — and those findings feed the rules so the next project starts a little sharper.
Read the system, end to end.
The 5-minute orientation to how a Punch website ships now. Four phases, one continuous loop, six roles. The shared mental model the team will reference for everything else.
Two to three hours, hands-on.
Role-specific onboarding tracks — module-based, self-paced, with exercises in your own files. Every team member runs their role's track in the first two weeks, regardless of tenure.
Pin these on every engagement.
The reference layer — row-by-row playbook for every step and every gate, the cheat sheet for which skill to run when, and the leadership briefing you'd hand to a client or prospect.
The things people will ask you, and that you might be wondering yourself. If your question isn't here, see Who to ask below.
-
Am I supposed to stop what I'm doing right now? What about projects in flight?
For now, we'll let you know which process to use on each project — your manager or PM will flag it at kickoff. Soon, you can assume we're using the new process for everything.
-
Is designing straight in Figma, then building in the CMS, fully dead?
Mostly, yes. The new path is tokens + components exported from Figma into a sandbox, then composed in Cowork. If we're doing a project the old way for some reason, your manager or PM will let you know. Figma is still the source of truth for design system values — what changed is how those values reach a built page. Brand projects, collateral, and motion work all continue in Figma as before.
-
Do I need to memorize plugin commands?
No. You ask Cowork in natural language and the right skill fires automatically. The Skill Reference lists every skill if you want to know what exists, but you'll rarely type a skill name directly — Cowork picks the right one from what you describe.
-
What if I'm not sure which skill to run?
Reach for the Skill Reference doc (in the nav) — every skill on one page, sorted by phase. If you're still unsure, just describe what you're trying to do to Cowork in plain English. Cowork will pick a skill, suggest one, or tell you nothing matches yet.
-
What if I make a mistake in the new process?
You won't break anything that can't be re-run. Every skill is idempotent — point Cowork at the same brief twice and you get the same output. If a wireframe is off, regenerate it. If a copy brief is wrong, edit it and re-run. The retrospective at the end of each project captures patterns of confusion so the next time is easier.
-
Where do I report bugs or weird behavior?
Post in
#punch-process, or DM the rollout leads directly. Bugs and friction patterns feed the next Quarterly Refresher and the rule docs. Don't quietly work around something — surface it. That's how the system gets better. -
Do I need to read every doc in the nav?
No. The nav is the directory; you only read what's relevant to your role and what you're doing right now. The rollout sequence (At a Glance → live launch session → your role's onboarding → pair on first project) is the only required path. Everything else is reference for when you need it.
-
1Ask your manager first. They're closest to your work and usually the fastest answer — and they'll know if your question is something the whole team would benefit from hearing the answer to.
-
2Then ping the rollout leads in
#punch-process: Laura · Joe · Brian · Josue
What changed lately
Full changelog →- May 21, 2026 Wireframe principles codified. Ten rules synthesized from the Auria build now govern every wireframe — source-fidelity rendering, eyebrow scarcity, light/dark theme toggle, canonical Punch Docs feedback splash.
- May 21, 2026 No-enhancement rule introduced. The renderer no longer auto-strips trailing periods or invents eyebrows. Copy discipline moves to writers and strategists.
-
May 21, 2026
Two new operating skills.
punch-term-driftcatches stale terminology against the glossary;punch-retrospectiveritualizes the end-of-project learning loop. -
May 14, 2026
The May 2026 reset shipped. Two AI surfaces (Cowork + Claude Code), automated QA at Gates 5–6, nine gates with named owners, single
punch-websiteplugin. The largest single version change in Punch's history.
For the team
- What's New at PunchOngoing changelog · vet entry point
- Quarterly Refresher · Q2 2026Launch event · format for future refreshers
- Punch GlossaryShared vocabulary for the system
- How Punch WorksAgency overview
Operations & runbooks
- PM Asana Scope GuideScoping templates & structure
- Rush Test RunbookAccelerated timelines
- Library & Modes GuideFigma library + modes reference
- Figma Starter SpecSetup spec for new client forks
- Engagement Talk TrackSales / client conversation guide