Forge core workflows
Three recipes that cover most of what teams actually do in Forge.
Overview
Forge has one main sequence (intake → naming → lock → scaffold), but three distinct jobs run through it in practice: starting a brand-new site, renaming or re-registering something already underway, and keeping prompts consistent across a whole fleet of sites.
How it works
Each workflow below is the same underlying Forge tools — Site Forge intake, Brand naming, Forge Prompt Studio, and Root Brand Studio — run in a different order or emphasis depending on what you're actually trying to do.
Steps
- •
Workflow 1 — start a brand-new site
Run Site Forge intake end to end: pattern brief → route classes → Brand naming → Brand DNA lock. Nothing scaffolds until the lock clears.
- •
Workflow 2 — settle on a name before anything else
Some teams want the name locked before they've fully scoped the site. Run Brand naming on its own inside intake, lock it, then come back and finish the rest of the pattern brief.
- •
Workflow 3 — keep prompts consistent across the fleet
Author and tag prompts in Forge Prompt Studio per workflow step, then use Root Brand Studio to check status across every site in your fleet rather than re-deriving each site's prompt setup from scratch.
Capabilities
- One intake, three entry points — full pattern brief, naming-first, or fleet-wide prompt governance.
- A single Brand DNA lock gate shared by every workflow above — nothing downstream builds around it.
- Prompt reuse across sites via Prompt Studio's tagging and versioning.
Limits & honest scope
- These are usage patterns on top of the same Forge tools, not separate features — see each linked page for what's actually live versus still shipping.
- Renaming or re-locking Brand DNA after the fact means reopening the gate deliberately; it's not a live-editable toggle.