Skip to contentllms.txt

Choose Your Path

Syllago serves several different jobs, so the docs are dense enough that it helps to pick a path. Find your role below and follow the suggested route — you can wander into the rest later.

You manage your own machine. You use one or two AI coding tools, want them in sync, and want to switch contexts between projects (Python work, frontend work, security audits) without retyping the same setup every time.

Read in order:

  1. Install syllago
  2. Quick Start: import from your existing tools
  3. Loadouts — bundle a “Python stack” or “frontend review” profile and switch with one command
  4. The TUI — browse, install, and manage content interactively

Commands you’ll lean on: syllago init, syllago add, syllago install, syllago loadout create, syllago loadout apply --keep, syllago loadout remove.

You own a repo and want every contributor (human or AI) to get the same AI-tool configuration when they clone it. You probably commit .syllago/ to Git. You want CI to fail if the config drifts.

Read in order:

  1. Local vs. Global architecture — why and how to commit .syllago/ to your repo
  2. .syllago.yaml Format — the file your team will share
  3. syllago sync-install — one command in CI that pulls registries and installs to a provider
  4. Team setup — multi-developer workflows

Commands you’ll lean on: syllago init, syllago sync-install --to <provider>, syllago compat, syllago doctor.

You’re standing syllago up for an organization. You need a private registry, signed manifests, and guardrails that prevent internal rules from leaking to public registries.

Read in order:

  1. Registries — how shared content distribution works
  2. Registry privacy — privacy gates and taint propagation
  3. MOAT trust tiers — signing, provenance, and trusted roots
  4. Sandbox — running AI providers under bubblewrap restrictions

Commands you’ll lean on: syllago registry create, syllago manifest generate, syllago moat sign, syllago moat trust, syllago sandbox.

If you’re evaluating syllago for the first time, the solo-developer path is the shortest route to a working setup. The other roles build on top of that foundation — you can pick them up later as your needs grow.