fimo skill. Two CLI namespaces manage all three — fimo skills for skill artifacts and fimo rules for rule files.
The three layers
Global skills
fimo-cli, fimo-studio, and fimo-migration — installed once per machine. They describe the CLI workflows, the Studio web app, and migrations, and load in any compatible AI tool.Rule files
AGENTS.md (universal) plus per-agent variants (CLAUDE.md, .cursor/rules/fimo.mdc, .windsurfrules, GEMINI.md) generated for the tools each project supports.Project fimo skill
The code-side skill — schemas, forms,
t(), fimo/ui — installed into the project and version-locked to the project’s installed fimo package.The project fimo skill vs the global fimo-cli skill
- The global
fimo-cliskill covers what the CLI does — creating projects, building content, deploying, managing domains and analytics. It’s machine-wide and the same for every project. - The project
fimoskill covers how to write code in this project — the exact package surface installed here. It’s version-locked, so its shapes always match what your code can use.
fimo skills — install, sync, uninstall
fimo skills install is context-aware: outside a project it installs only global skills; inside a project it also writes the project skill and generates each selected agent’s rule file. It shows a preview of every path it will touch, and prints exactly what it wrote.
Skills mostly stay current on their own — global skills auto-refresh when a newer CLI runs, and the project skill auto-refreshes when the
fimo package version bumps. Run fimo skills sync to force a refresh.fimo rules — rule files only
fimo rules sync is purely additive — it creates missing variant files but never overwrites existing ones, so your project-specific edits are preserved. To regenerate a stale variant, delete it first, then re-run. Rules are generated config; skills are reusable knowledge artifacts — the split is deliberate.
What’s next
Install skills
The step-by-step setup.
Connect your coding agent
Supported agents.
CLI reference
Every
fimo command.