Author once, emit per tool

AmbyKit’s core design is author-once, emit-per-tool. There is exactly one neutral source of truth for the workflow — the templates and phase prompts. Per-tool emitters translate that source into each assistant’s native command/rules format. You never hand-maintain per-tool files; you edit the neutral source and run ambykit sync.

A single neutral source (src/templates + src/prompts) is translated by emitters into native files for Claude Code, GitHub Copilot (+ CLI), Cursor (+ CLI), OpenCode, and Antigravity (+ CLI).

One neutral source; per-tool emitters produce native files.

This keeps the workflow consistent across every assistant a team uses, and makes adding a new tool a thin emitter rather than a fork of the whole workflow.