View as markdown

Teach your AI systemHUB

AI sessions forget. These docs make any connected agent capable today; this page makes it capable every day — by saving a short systemHUB briefing into your own workspace (your repo’s CLAUDE.md, your project instructions, or wherever your AI keeps standing context), so future sessions start already knowing how to drive systemHUB well.

The first-session prompt

Paste this into your AI once systemHUB is connected (see Getting started):

You’re connected to our systemHUB via the MCP connector. Do four things:

  1. Fetch https://systemhub.com/llms-full.txt and read it — it’s the full guide to driving systemHUB well.
  2. Map our Systems folder tree and give me a one-paragraph read on how our library is organised and where the gaps look biggest.
  3. Pick one process we clearly run but haven’t documented, and draft it as a system for my review — follow the docs’ authoring contract: trigger, steps, definition of done, ORANGE state, yellow-highlight anything you’d have to guess.
  4. Save a concise systemHUB briefing into our standing context (CLAUDE.md or equivalent) so future sessions don’t need to re-learn any of this — the docs suggest what to include at systemhub.com/docs/teach-your-ai.

Then tell me: what did the docs not explain that you needed?

What the saved briefing should contain

The generic layer lives in these docs — don’t copy it all. The briefing is the bridge: just enough standing context plus pointers back here. A good one:

## systemHUB (via MCP connector)

Our process library. Systems (SOPs), Policies, Trainings. Connected via the
systemHUB MCP connector. Note: MCP scoping is workspace-level today
(a known issue — the connection follows the workspace token, not the
individual), so treat what the agent can see as account-wide.

Ground rules (full docs: https://systemhub.com/llms-full.txt):
- Orient before acting: get_folder_tree / search_by_name first; never create
  into a guessed location; check for duplicates before creating.
- New work goes in ORANGE (state: 1 = needs review). Never set GREEN (3)
  yourself — approval is human. Note "draft" is ambiguous here: state 0 is
  GREY/draft, and `publish: false` is a separate, unrelated hidden-draft
  concept. Our convention is ORANGE for anything awaiting human review.
- Edits and even tagging auto-publish. There is no quiet-editing mode by
  default — assume any write to a live document is immediately visible.
- Author to the contract: Overview in `description`; body = Trigger, then
  <h3> steps, then Definition of done. H1–H3 only, 4 marker-* highlights,
  no inline <code>, no external images (yellow-flag an upload spot instead).
- Yellow-highlight every gap — never invent names, links or thresholds.
- Never touch master templates (isMasterTemplate: true).
- Can't do: deletes, seat provisioning, workspace analytics.
- If a tool behaves unexpectedly, check the changelog:
  https://systemhub.com/docs/changelog

Our specifics:
- Folder convention: [e.g. numbered departments — 1. Marketing, 2. Sales…]
- Owners: [who owns which department's systems]
- House style: [anything your business wants systems to always include]

The Our specifics block is the part only you can supply — your AI should fill it in from what it finds in your library, and you should correct it. That’s the piece these docs can never know.

Why this works

Next: Quick wins →