01 · Mechanics

How it works.

Every skill is a guided flow that turns a short brief into crue-grade output. Every improvement you make flows back to the whole team. Here is the machine.

Inside a skill

One loop runs everything.

A name, a logo, a deck, a video, a website. Same five beats. The interview is where the quality comes from, not a one-shot guess.

Input to output

What goes in. What comes out.

A skill takes a little context and your answers, applies the standard, and returns a finished artifact plus a write-back block for the Core.

Example · an offer
Input
  • The need, in plain words
  • Client Core: brand, archetype, language
  • Pricing engine (House)
  • Your answers: scope, tier, express
crue-os does
  • Maps the need to our products
  • Prices from the catalog, checks the floor
  • Writes each module, on voice
  • Runs the offer Roman Pass
Output
  • A clean, tiered offer
  • Created in Bexio, open-in-Bexio link to review and send
  • A future-opportunities upsell
  • A Save to Client Core block
Example · a website
Input
  • Their current URL or docs
  • Industry, audience, the goal
  • Style picks (Mobbin, references)
  • Direction Lock
crue-os does
  • Structure and copy to the blueprint
  • Design system, then the build
  • SEO, performance, accessibility
  • web-finish, the Roman Pass
Output
  • An Awwwards-grade site, live on Vercel
  • On the locked pro stack
  • Search-visible and fast
  • Decisions logged to the Core
The sync

Change it once. Everyone gets it.

The repo is the single source of truth. A commit bundles the shared standards and the latest Client Core template into every pack, then the org marketplace pushes the whole brain to every teammate.

Edit the repo
A skill, a standard, a price band.
Pre-commit + CI
Bundles foundation and the Core template into each pack. Guards the brand.
Push to main
One source of truth, updated.
Org marketplace
Auto-sync to the org. Around 30 minutes.
Every teammate
chat · Cowork · Claude Code.
Standards stay in lockstep

Foundation, bundled

The shared standards live in one place and ship inside every pack automatically. The pre-commit hook and CI regenerate the bundled copies on every commit, so a standard can never drift from the skills that depend on it.

Confidential, split out

crue-house, founders only

Pricing, client data and proof live in a separate private repo, crue-house, mounted read-only in the House Project. The team repo carries no pricing, so the team can get every skill without it. Edit in crue-house, push, then Sync.

Four repos in all, one job each: crue-os (the engine, everyone), crue-house (confidential, founders), crue-clients (a Client Core per client), crue-projects (the websites and apps). Full breakdown on Install.
The loop that compounds

Spot a fix. Push it. Done.

The brain gets sharper by use, correction, push. Every real correction makes the team's next output better.

Work in Projects Spot a fix Edit the repo Commit + push Auto-sync to everyone
What's next

The cockpit, and a real Lock button.

Today the brain runs across Claude. Next is an internal cockpit on the same data spine: finances, open invoices, projects, per-project links, single sign-on.

In chat, today

The lock card

When something worth keeping changes, the skill shows a summarized lock card, the item, the file it lands in, the diff and the commit, and on "lock it" commits it to the client's Core in crue-clients, then the Project syncs. One glance, one word.

In the cockpit, next

A real Lock button

The same detail view becomes a real button. It appears when a change is worth saving, opens the card, and on click commits to the client repo and re-syncs. Same guardrails: client repos only, never the confidential layer, never a force-push.