Plugins

Plugins bundle everything that customizes Syntic Code into a single installable package. A plugin can carry rules, Agent Skills, slash commands, MCP server definitions, and hooks, so instead of configuring each piece by hand, you install one plugin and get a complete, coherent setup. Plugins are how teams standardize their workflows and how the community shares reusable capabilities.

What a plugin can contain

A plugin is a versioned bundle of any combination of the following:

• Rules that shape how Amara behaves in your project.
• Skills packaged as .syntic/skills/ directories the agent loads on demand.
• Commands that add new slash commands to your sessions.
• MCP servers pre-wired so external tools connect the moment the plugin is installed.
• Hooks that run at defined points in a session’s lifecycle.

Because these pieces travel together, a plugin can capture an entire way of working, a house style, a review workflow, a connection to your internal systems, and reproduce it on any machine with one command.

Why use plugins

Plugins solve the drift that happens when every developer configures Syntic Code slightly differently. Publish a plugin for your team and everyone gets the same skills, the same commands, and the same guardrails, all versioned so upgrades are explicit. They also make good building blocks for the wider ecosystem: you can install a well-tested plugin to add a capability rather than assembling it yourself.

Where to go next

Read Install a Plugin to discover and add prebuilt plugins from a marketplace or a repository. When you are ready to package your own conventions, Create a Plugin walks through the bundle layout and how to include rules, skills, commands, MCP servers, and hooks.