Skip to contentllms.txt

Get your Claude Code rules into Cursor

You have rules configured in Claude Code and want the same guidance in Cursor — without maintaining two copies by hand. This guide moves them through syllago in four commands.

  • syllago installed and initialized (syllago init)
  • Claude Code with at least one rule configured (CLAUDE.md or .claude/ rules)
Terminal window
syllago add --from claude-code

Without a positional argument, add runs in discovery mode: it lists the content Claude Code has available without importing anything.

Terminal window
# Import all rules
syllago add rules --from claude-code
# Or import one specific rule
syllago add rules/security --from claude-code

The rules are copied into your library (~/.syllago/content/), where syllago manages them independently of Claude Code. Run syllago list to confirm what landed.

Terminal window
syllago install security --to cursor --dry-run

--dry-run shows exactly what would be written to Cursor’s directories without touching anything. Nothing changes until you run the command without the flag.

Terminal window
syllago install security --to cursor

By default syllago installs a symlink, so future edits to the rule in your library show up in Cursor immediately. Pass --method copy if you want a standalone file instead.

Look in your project’s .cursor/rules/ directory — you should see the rule as an .mdc file:

Terminal window
ls .cursor/rules/

Open Cursor and the rule is active. You can also confirm syllago’s view of the install with syllago list.

Claude Code stores rules as plain Markdown; Cursor expects MDC format (.mdc files with metadata frontmatter like description, alwaysApply, and globs). syllago performs that conversion automatically during install — the copy in your library stays in canonical form, so the same rule can also be installed to any other provider. See Format Conversion for the details.