Quick Start

In the next five minutes you’ll move real content between AI coding tools — no manual format conversion, no copy-pasting config files.

There are two paths to get started, depending on what you have today:

Import from your existing tools — pull in rules, skills, or context you already have configured in an AI coding tool
Browse a registry — discover and install shared content from a team or community registry

Import from your existing tools

If you already have AI coding tools configured (Claude Code rules, Cursor rules, etc.), syllago can discover that content and bring it into your library.

Initialize syllago

syllago init

Follow the terminal prompts: init detects the AI coding tools (providers) on your machine and asks you to confirm which ones to manage. In the provider picker, space toggles a selection and enter confirms. When it finishes, your config exists at .syllago/config.json. To skip the prompts and accept defaults, pass --yes.

Discover available content

syllago add --from claude-code

Without a positional argument, add runs in discovery mode — it shows what content the provider has available without importing anything.

Add content to your library

Once you know what’s there, add it:

# Add all rules from a provider
syllago add rules --from claude-code

# Add a specific item
syllago add rules/security --from claude-code

Content is copied into your library (~/.syllago/content/), where syllago manages it independently of the original provider.

Tip: Use --dry-run to preview what would be written without making changes. Use --all to add everything at once.

Install to another provider

syllago install my-rule --to cursor

That’s the payoff: the item moves from your library into Cursor’s expected location, with the format converted automatically. By default, syllago uses a symlink so changes stay in sync. Pass --method copy if you need a standalone file.

# Preview what would happen without writing anything
syllago install my-rule --to cursor --dry-run

See what you have

syllago list

Output is grouped by type (rules, skills, agents, etc.). Use --source to filter by origin and --type to filter by content type.

Browse a registry

Registries are git repos of shared content — team standards, community collections, curated configurations. A registry isn’t a central remote service: it’s an ordinary git repository that someone creates and publishes. You can add any registry you have the URL for, or create your own with syllago registry create.

Initialize syllago

Skip this if you already ran it above.

syllago init

Follow the terminal prompts to confirm the detected providers.

Add a registry

The example below uses the official syllago meta-registry — swap in your team’s registry URL if you have one.

syllago registry add https://github.com/OpenScribbler/syllago-meta-registry.git

You can optionally pass --name to give it a short alias, or --ref to pin a specific branch or tag.

Sync registry content

syllago registry sync

This pulls the latest content from all registered registries. To sync a specific one, pass its name: syllago registry sync my-registry.

Browse available items

syllago registry items

Filter by type to narrow results:

syllago registry items --type skills

Install from the registry

syllago install some-skill --to claude-code

Same install command as before — syllago resolves the item from your registries, converts the format for the target provider, and symlinks it into place.

Or use the TUI

Launch the interactive terminal UI to browse and install content visually:

syllago

Running syllago with no arguments opens the TUI, where you can explore your library, registries, and providers in one place.

Next steps

Now that you have content flowing between tools, learn how the pieces fit together in Core Concepts.