Documentation
Every repo describes what it owns in .architecture/; Furio checks it on every pull request and draws the map of all of them. To see what you get, open the live demo: three repos of a small shop. To start in one of yours:
npx @getfurio/cli init # the manifest, and the skill for your coding agent
npx @getfurio/cli validate # check itGuides
- Set up FurioFrom one repo on your machine to the map of the whole organization, with a check on every pull request.
- The manifestEach repo has one YAML file, .architecture/architecture.yaml, that says what the repo runs and what each part talks to.
- Reading the mapThe map shows every component of your workspace and what depends on what.
- Furio CloudFurio Cloud hosts the map of your workspace at getfurio.com/w/<name>, private on a paid plan, with nothing to run: each repo sends its own manifest from its GitHub Action.
- Coding agentsA map is only as good as its last update. Furio's skill makes AI coding agents (Claude Code, Codex and anything that reads AGENTS.md) update the manifest in the same change as the code.