The .syntic Directory

The .syntic/ directory is where Syntic Code keeps everything project-specific: configuration, rules, skills, commands, and memory. Committing it to version control means your whole team shares the same setup and Amara behaves consistently for everyone.

settings.json and rules

settings.json is the central configuration file. It holds permissions (which commands Amara may run without asking), environment variables, hook definitions, and MCP server declarations. Rules files sit alongside it and describe constraints and preferences in plain language — coding standards, directories to avoid, or conventions to follow. Amara loads these at session start and treats them as guardrails throughout the agent loop.

Skills and commands

Reusable workflows live under .syntic/skills/, each in its own folder with instructions Amara can follow when a task matches. Custom slash commands are defined similarly and give you explicit shortcuts during a session. Keeping both in the directory means they are versioned, reviewable, and easy to share — the same way you would treat any other code in the project.

Memory

Long-lived project context belongs in a memory file, typically SYNTIC.md at the repository root or inside .syntic/. This is where you record architecture notes, how to run the app, common pitfalls, and anything you would otherwise repeat to Amara every session. It is read automatically, so Amara starts each session already oriented. Because the whole directory is just files, you can inspect, diff, and review it like the rest of your codebase. See context window for how this content is loaded efficiently.