Scaffold Reference

Client Workspace · How We Set It Up

One scaffold.
Every client on the same operating system.

A visual walkthrough of how Storystak AI structures a client workspace. Every engagement is a self-contained universe with its own read-only Vault, its own team workspace, and its own governance — but they all obey the same rules, so Claude behaves predictably no matter which client it's working inside.

Click any small info dot for the mechanics behind that piece.

One folder per client One isolated Vault each Skills + plugins per Vault Vault writes: owner only

01.The big picture

A workspace root sits at the top. Client engagements branch from it as siblings — the same scaffold every time, at whatever stage of maturity that engagement happens to be in. The brand-colored top stripe is swapped per client; the structure underneath never changes.

Workspace Root / root
Workspace-wide rules · Shared skills library · Client siblings below
CLAUDE.md CONTEXT.md Skills/
Client A
Established engagement
Mature
Vault Fully populated
Positioning, personas, voice, validated copy, skills, plugins
Shared Deliverables · Reports
Draft → Review → Release pipeline live
Personal Per teammate
One sandbox per person on the account
Production Steady cadence
Client B
Active build
Growing
Vault Populating
Brand guidelines, services, copy, and strategy going in
Shared Reports
Vault-updates queue live
Personal Per teammate
Same template as siblings
Active build Buildout in progress
Client C
Early stage
Early
Vault Partial
Brand identity in; positioning still being defined
Shared Reports · Web
First deliverables in progress
Personal Per teammate
Same template as siblings
Onboarding Positioning phase
Client D
Scaffold only
New
Vault Empty shell
Folder structure created; content TBD
Shared Reports
Vault-updates queue ready
Personal Per teammate
Same template as siblings
Just created Awaiting kickoff
Vault — read-only canonical reference
Shared — team deliverables
Personal — individual workspaces
Governance — CLAUDE.md, identity rules
Mature
Growing
Early / new

02.Anatomy of a Vault

Every Vault is the client's canonical reference — the one place Claude trusts for facts about that brand. Each Vault ships with its own skills/ and plugins/ capability libraries, so brand-specific tooling travels with the engagement instead of living in a global pile.

The Vault

Read-only · Permission-protected · single editor (the workspace owner)
_The Vault/
├─CLAUDE.mdVault read rules
├─README.mdcontents map
├─Brand Assets/logos, fonts, color tokens
├─Company Reference/positioning · personas · voice
├─skills/
│  └─INDEX.mdbrand-specific .skill packages
└─plugins/
   └─INDEX.mdbrand-specific plugins

Read freely

Claude pulls voice, audience personas, positioning, validated copy, and brand tokens directly from the Vault — not from training memory or cross-client assumptions.

Never write directly

Two-layer protection: CLAUDE.md instructions plus storage-level permissions. Even if a user insists, Claude won't edit a Vault file unless the verified workspace owner is the user.

Log change requests

Vault edits from anyone other than the owner get appended to Shared/Reports/_Vault-updates.md as Pending. The owner reviews the queue and applies changes manually.

Capabilities travel here

Each Vault carries its own skills/ and plugins/ libraries. Trigger language propagates to three places — the file frontmatter, the folder INDEX.md, and the client's CLAUDE.md "Available Vault Capabilities" section.

03.Vault Powered OutputExample from justwavy.com

Voice in one paragraph

Confident, plain-spoken, and operator-to-operator. The brand sounds like a sharp growth lead explaining how things actually work — not a salesperson and not a brand poet. The voice is calm and declarative: short truths stated as fact, then a clear explanation of what they do about it. It avoids hype words, avoids jargon for its own sake, and never oversells. Confidence comes from specificity and from numbers, not from adjectives.

Tone attributes

  • Confident, not boastful — states capability plainly; no "world-class" or "revolutionary."
  • Plain & direct — simple words, real explanations, no buzzword soup.
  • Operator-credible — talks process and systems like a practitioner.
  • Calm authority — no urgency tricks, no fake scarcity.
  • Partner-minded — "an extension of your team," never vendor framing.
  • Outcome-anchored — revenue, ROAS, retention, CAC.

Signature sentence patterns

  • The contrast statement — name the wrong way, then the right way: "We don't run ads. We engineer growth systems."
  • Plain truth, then the fix — a hard reality stated flat, followed by what they do about it.
  • The "more than" qualifier — "requires more than simply launching ads."
  • The short fragment — one-line sentences that land like a stamp: "Creative that converts."
  • Named, ordered process steps — bold step name, then a sentence or two.

Vocabulary

Use: growth engine, growth systems, engineer, scale, DTC, paid media, performance creative, customer acquisition, CAC, ROAS, LTV, retention, founder-led, data-driven, roadmap, hands-on, extension of your team.

Avoid: synergy, cutting-edge, world-class, revolutionary, disrupt, ninja/rockstar/guru, vague "unlock your potential," unbacked superlatives, heavy exclamation points.

Messaging pillars

  • Systems, not ads. Growth is engineered infrastructure — anyone can run ads; they build the engine.
  • Founder-led = closer, faster, accountable. Small team, no management layers, senior people doing the work.
  • Built specifically for DTC. Not a generalist agency — deep, category-specific experience.
  • Measured the way clients measure. Success = revenue, ROAS, retention. Full transparency.

CTA style

Warm, momentum-oriented, low-pressure. The recurring family: "Let's Grow Together," "Book a Free Strategy Call," "Let's Get To Work." Invitational and specific — no countdown urgency.

Sample 1 — New service page
Headline

Turn First Orders Into Repeat Revenue

Most brands spend everything on the first sale and nothing on the second. Lifecycle marketing is how you change that — turning one-time buyers into a revenue base that compounds.

Acquisition gets you customers. Retention is what makes them profitable.

As CAC keeps rising, the brands that scale aren't the ones spending more to acquire — they're the ones keeping the customers they already paid for.

That's what lifecycle marketing does. Email, SMS, and retention flows that bring customers back, raise LTV, and grow revenue without adding a dollar of ad spend.

We build that system in four steps:

  • Map the Journey — find where revenue is leaking between first order and second.
  • Build the Flows — welcome, post-purchase, replenishment, win-back, segmented.
  • Test & Refine — subject lines, timing, offers, segments, continuously.
  • Scale What Works — winning sequences become a revenue channel that runs on its own.

Sample 2 — Short social caption

Your best growth channel isn't a new platform. It's the customers you already have.

We build the lifecycle systems that turn first orders into repeat revenue — no extra ad spend required.

Let's grow together.


Why this sounds on-brand
Voice ruleWhere it shows up
Contrast statement"Acquisition gets you customers. Retention is what makes them profitable."
Plain truth, then the fix"Most brands spend everything on the first sale…"
Named, ordered stepsMap → Build → Test → Scale
Outcome-anchored vocabularyCAC, LTV, ad spend, repeat purchase
CTA voice"Let's grow together."
No hype / no fake urgencyZero superlatives throughout