04 · Memory

Templates & the Client Core.

Every new project starts from the latest template, automatically. Every result that should stick is locked into the client’s Core in GitHub with one phrase: lock to client. The Core, not the chat, is the memory.

Start a project

The latest template, every time.

The Client Core template has one source of truth in the repo. It is bundled into the initialize-project skill on every commit, so improvements to the template reach every future project with no manual copying.

Template in the repo
20-client-template. The single source.
Bundled on commit
Carried inside initialize-project, always current.
Run initialize-project
Pick or create the client. Set archetype, goal, inputs.
Committed Core
Five files in crue-clients/clients/<slug>/, mounted in the Project.
What comes in

The five Client Core files.

Mounted read-only from crue-clients into the client’s Project. The first thing every skill reads.

brand-pack.md

The brand

Colour, type, voice, archetype, rules. The source of truth for everything we make for them.

imagery-lockins.md

The look

Registered image and video styles, so the whole team stays consistent.

reference-packs.md

The references

Saved, reusable reference and moodboard packs.

decisions-log.md

The memory

Every meaningful decision, dated. The client's history.

legal-templates.md

The scaffolding

Swiss legal scaffolding for that client.

archetype

Set first

One tag that modulates how every skill renders for them. A bank is never a startup.

After a result

Lock it in. One phrase.

When a palette, a voice, an image style or a decision locks, the skill offers a lock card. Say lock to client and it commits to that client’s Core. That is what makes the next chat, today or months later, start warm and on brand.

Lock card

File   crue-clients/clients/<slug>/brand-pack.md

Action   replace section "Visual tokens"

Content

Primary  #1A1A1A
Accent   #C8552B
Display  Funnel Display, 500
Body     Funnel Sans, 300
Radius   16px · Grid 12-col

How the lock works

  1. The skill detects what changed and shows the lock card: the item, the file, the change, the commit.
  2. Say lock to client. It commits to crue-clients through the GitHub write MCP, or with git in Claude Code. Never a force-push.
  3. Re-sync the Project so the next chat reads the new state.
  4. The newest commit wins. The change and the why are logged in decisions-log. No write MCP connected? You get the block to paste and commit.
Drift detection. If a result changes a locked value or contradicts a logged decision, the block is flagged CHANGE or CONFLICT, old to new, and asks you to confirm before overwriting. A full audit runs via client-core-sync.
Two stores, two directions

Both live in GitHub. Both sync down.

House Core

crue-house is the truth

The confidential layer lives in the admins-only crue-house repo and flows one way into the House Project (GitHub connector, read-only). Edit in crue-house, push, then Sync. Never edit a synced file in the Project.

Client Core

crue-clients is the truth

One folder per client in crue-clients, mounted read-only into that client’s Project. The team updates it by lock to client, then Sync. Confidential House content never enters a client Core.