Extend Syntic Code
Out of the box, Syntic Code reads and edits code, runs commands, looks things up online and hands work to subagents. These are the ways to give it more.
| Add | So that | Lives in | Page |
|---|---|---|---|
| Skills | The agent knows how your team does a task, and you can run it as /name | .syntic/skills/<name>/SKILL.md | Skills & custom commands |
| Custom commands | You can fire a saved prompt with arguments | .syntic/commands/<name>.md | Skills & custom commands |
| Hooks | Your script runs every time, at a fixed point (format after edits, block risky commands) | hooks in settings | Hooks |
| MCP servers | The agent can use outside systems: databases, trackers, docs, browsers | .mcp.json | MCP servers |
| Custom agents | A specialist with its own instructions and tools | .syntic/agents/<name>.md | Subagents |
| Output styles | Replies are written in a voice that suits you | output-styles/*.md | Output styles |
| Plugins | All of the above, packaged and shared | A marketplace | Plugins |
| Mods | A small program draws extra interface (footer, band, pane) | ~/.syntic/mods/ | Mods |
| Memory | Project knowledge loads into every session | SYNTIC.md | Memory |
Which one do I need?
- “Every time it edits a file, run the formatter.” → a hook. It does not depend on the agent remembering.
- “When we write a migration, follow these seven steps.” → a skill. The agent picks it up when relevant.
- “Give me
/standupthat summarizes yesterday’s commits.” → a custom command. - “Let it read our Jira tickets.” → an MCP server.
- “Always use pnpm, never npm.” → a line in
SYNTIC.md. - “Share our setup with ten repositories.” → a plugin.