Facebook tracking pixel Skip to main content

Core modules

Get a workspace built for you.

Start with an empty folder and your website. It reads the site and any documents you share, works out your offers, buyers, voice and pricing signals, then asks a short set of skippable questions about whatever it could not find. After that it writes the full structure for Solo, Team or Agency, seeds a numbers log with your first baselines, and finishes with a first plan and a report card on what is still thin.

Request access Have us build it
  • Reads your site first
  • Never overwrites a workspace
  • Ends with a report card

At a glance

Group
Core modules
Command
/setup
Uses
Your website, documents and answers
Writes
Folders, rules and a first plan
Sends
Nothing. Drafts only.

01When to use it

Start here, before any other skill.

  • You have an empty folder, a synced one is fine, and want to start working with the toolkit.
  • A workspace exists but has pieces missing, needs its profile chosen again, or holds context too thin to work from.
  • You want the other core modules to run. They need a workspace, and this skill needs only an empty folder.

Not for

  • Planning and closing out each day once you are set up. Use /daily
  • Tidying a workspace that has grown, from dead links to stale files. Use /optimizer
  • Adding a teammate later, or changing who sees which clients. Use /team

02What it needs

Your site first, then a few answers.

  • Write access to the folder. A synced folder is the default, and needs no other infrastructure.
  • One or more website addresses, plus any documents you can share: a deck, a brand guide, a pricing page, an about page.
  • Optional: one tool to read from, such as a CRM, an inbox or an analytics export. It reads only what it needs and sends nothing.
  • Your profile: Solo, Team or Agency. It recommends one from what it has seen, and you confirm.
  • Answers to fill the gaps: a one-line description, offers and pricing, who you serve, your voice, your top goal for the next 90 days, and any channel, disclosure or claim your business is barred from or bound to.
  • The person who approves anything outbound, and the caps on how much later runs may read and write. Skip the caps and it sets defaults.

03What it writes

A full workspace, seeded and mapped.

CLAUDE.md, plus one per folder
Routers that map every concept to its home: the root one in 150 lines or fewer, and one of up to 60 lines in each top-level folder.
_system/
The config file (profile, owner, approval contact, and hard caps on reads, writes, transcripts, emails, messages and housekeeping), a rules file (approval gates, the client firewall, one home per fact, an append-only ledger), and starting connector and permission files.
Company/
Profile, brand, offers, buyers, strategy and constraints, from what the import found and you confirmed. Market, competitor and tool files are added only when there is real content for them.
Memory/
The numbers log, with its header and your first baseline rows aimed at your top goal, plus an empty signals queue and files for decisions, lessons and terms.
Daily/, Projects/, Library/
Today's note, a first deliverable (a seven-day growth plan, or a first brief in today's note), and the templates your profile needs, copied by name.
Pipeline/, Team/ or Clients/
Solo gets a pipeline. Team gets a folder per person and permission rows. Agency gets a firewalled folder per client, every file in it marked confidential, plus team folders and a pipeline for prospects.

04Limits

What it never does.

  • Overwrite a workspace that already exists. It reports what is there, offers to add only the missing pieces, and asks before writing.
  • Send a message, delete a file, publish, change prices or offers, edit permissions or contact a client. Anything outbound is drafted for the approval contact.
  • Fill a gap with a bracket placeholder or an invented fact. Empty sections are left out and show up on the report card.
  • Set any work cap to unlimited.
  • Log an unknown baseline as zero or a guess, or call a figure you give it confirmed before a system of record shows it.

What stays with you.

  • Answering or skipping the questions, and confirming the profile it suggests.
  • Deepening the areas the report card rates thin or missing, then running the next skill it suggests.

05Sample output

A report card after the first run.

For a made-up mobile pet groomer that shared its website and skipped two questions. A real card rates each context area that applies to your profile.

Report card Illustrative, not a client result.
Company profile Solid
Brand Solid
Offers Thin
Competitors Missing
KPI baselines Thin

Handoff

  • Start from CLAUDE.md, the root router.
  • First deliverable: a seven-day growth plan in Projects/.
  • Deepen next: offers, competitors and baselines.
  • Suggested next skill: daily, to plan the first day.

06Related skills

Often run beside it.

07Questions

Before you run it.

What if I already have a workspace?

It looks for one first: the root router, the config file and the company folder. If they exist, it overwrites nothing. It tells you what is there, offers to repair or add only what is missing, and asks before it writes.

Which profile should I choose?

Solo is for one person and adds a pipeline. Team is for several people inside one business and adds a folder for each of them. Agency is for serving outside clients and gives every client a firewalled folder. It suggests one from what it has seen, and you confirm.

How long does it take?

The machine work was timed once, on 2026-09-01, at 1 minute 39 seconds for 35 files. The rest is however long you spend on its questions.

What do I need to run it?

Claude Code, in the terminal, its desktop app or an IDE, not Claude Desktop. Access to the toolkit is free by request.

Have us build it

We can build it for you.

Start with the free plan. A person names the first fix.

Get your free plan Or run it yourself with the toolkit.