Skip to main content
Any coding agent that can run terminal commands can work with Fimo. Connect it once on each machine, then let it load version-matched instructions for the task at hand.
1

Install the global skill

fimo init offers this during setup. To connect an agent later, run:
Choose the coding tools installed on this machine. In a non-interactive shell, pass them explicitly:
Hermes Agent uses the same bootstrap. Select it with --agents=hermes; when HERMES_HOME is set, Fimo installs the skill into that active Hermes profile.The command installs a small bootstrap skill. It does not copy the full Fimo instructions into every project.
2

Open the project

The agent should work from the project root and read AGENTS.md. New projects also include CLAUDE.md. Run fimo rules sync when another tool needs its own rule-file format. The command creates missing variants and does not overwrite files you have edited.
3

Load instructions for the task

Check the available instructions, then ask the agent to load only the skill it needs:
Use fimo-code for application code and fimo-cli for project workflows. fimo-studio covers Studio tasks. fimo-migration covers the migration workflow, which is still in development. It is not for routine work on an existing linked codebase.
If the agent is doing the initial setup, send it to Get started for AI coding agents.

​
Supported tools

The interactive picker lists the supported agent IDs. Tools that read AGENTS.md directly do not need a generated project rule file. Other tools can use a variant created by fimo rules sync. Each teammate runs fimo skills install on their own machine. Project rule files stay in the repository and arrive with the code.

​
What’s next

Skills and rules

Understand how global skills and project rules fit together.

Agent onboarding guide

Give the stable setup guide directly to your coding agent.

MCP server

Connect an MCP client to Fimo documentation.