Authoring

#/vitrinka:docs

Turns a repository into a living documentation board: scans for truth sources — docker-compose, OpenAPI, SQL DDL, migrations — creates the board, imports each diagram into its section, authors the pages, and wires the deep links both ways.

#/vitrinka:diagram

Composes one architecture diagram, either from repository truth or from a system you describe. You send semantics — lanes, groups, typed nodes, ports, edges — and the server lays it out.

You never send coordinates. Layout is computed, so adding a node cannot break the picture.

#/vitrinka:pages

Authors and maintains page cards as markdown. A repo-file-backed page carries a source and a revision, refreshes after repository edits, and can be written back to the file and committed.

#/vitrinka:brainstorming

Decision-led design. It maps the decisions that actually matter, puts them to you as batched multiple choice with a recommendation each, and ends in a committed decision log — then builds from it.

#/vitrinka:recall

A pre-build memory pass. Before designing or restyling a screen, it pulls what vitrinka already knows: the project memory document, prior shots of that screen, and the indexed component vocabulary.

It exists to fight the rebuild-from-scratch failure mode.

#/vitrinka:release

Drives a project's release board from the repository — sweep merged pull requests into the rolling next-release board, or cut the release.