DOCS · WORKFLOWS
Features describe what the system can do. Workflows describe how those features fit together when you actually work on something. Every workflow starts the same way: let the assistant orient itself. Every workflow ends the same way: let the assistant verify, not assume.
Read the full source →Workflow · 01
You join a project. You don't know its layout, its frameworks, its conventions, or where the bodies are buried. cix turns the first session from a slow tour built from twenty file reads into a structured one-page summary with everything you need to start contributing.
Read the deep dive →Workflow · 02
Orient → search for existing parts → reuse where appropriate → create the new pieces → enforce that they land in the right places. The assistant stops reinventing helpers it didn't know existed and stops misplacing files in folders the team has agreed not to use.
Read the deep dive →Workflow · 03
Impact analysis converts the anxious sweep-and-pray exercise into a structured task list. You see what depends on the target — directly, transitively, in routes, in tests, in tables — decide deliberately, and move forward.
Read the deep dive →Workflow · 04
A real run on a Laravel + Vue project surfaced eleven distinct issues — including a hardcoded credential in a production-served directory — in a fraction of the tool calls and tokens an indexer-free pass needed.
Read the deep dive →The general shape
For any task more involved than a one-line edit, cix shifts the assistant from 'read until I have enough context, then write' to 'query for what I need, query again to verify, then write — and only the parts that are missing.'