# Developer (https://docs.vitrinka.ai/dev)



## Three ways in [#surfaces]

Everything a developer touches goes through one of three surfaces, all speaking to the same server: the `vitrinka` CLI on your machine, the MCP endpoint your agent connects to directly over HTTP (`/mcp`, OAuth), and the plain HTTP API underneath both. The skills teach an agent the workflows so it arrives knowing what a board is and what to do with one. The exact lists — every verb, tool, variable and card kind — live in the generated [Reference](/reference) tab; the pages here tell you how to use them.

## The CLI [#cli]

One npm install (`@vitrinka/cli`) for macOS, Linux and Windows, one binary, one `vitrinka setup` that sets the rest up.

| Page                                         | What it covers                                                                                                                                                          |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Installing the CLI](/dev/cli/install)       | `npm i -g @vitrinka/cli`, what `vitrinka setup` sets up, check and repair.                                                                                              |
| [The commands](/dev/cli/commands)            | A tour of the nouns — board, work, task, sprint, intake, qa, me, review, search, project, config, setup — with `--base`, `--json`, `--no-input` and `--yes` throughout. |
| [Sets: capture and publish](/dev/cli/sets)   | A set is a directory of files with a share URL; how one gets made, filled, checked and sent, documents and pages included.                                              |
| [Boards, tags and diagrams](/dev/cli/boards) | Turning a set into the surface people actually mark up, opening and sharing it, and keeping it findable.                                                                |
| [The work queue](/dev/cli/work)              | How a machine reads released annotations, how an agent session holds the queue, and where the session stands.                                                           |
| [Machine and repo setup](/dev/cli/setup)     | Credentials per deployment, bindings per repository, the operator persona, the committed repo file, hooks and commit trailers.                                          |
| [Todos, reminders and time](/dev/cli/me)     | `vitrinka me` — todos that ripen on a condition the server evaluates, reminders, milestones and automatic work time.                                                    |

## Agents [#agents]

| Page                                              | What it covers                                                                                                                             |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| [Skills](/dev/skills/overview)                    | Nineteen skills in four plugins — core, PM, QA and the opt-in experimental one — for Claude Code and Codex.                                |
| [Capture and publish](/dev/skills/capture)        | Getting work onto a board — screens as they are built, journeys, reports.                                                                  |
| [Working the queue](/dev/skills/queue)            | Picking up annotations, fixing them in the repo, closing the loop with proof.                                                              |
| [Sessions to shipped fixes](/dev/skills/sessions) | Recorded user-testing sessions into changed code and maintained tests.                                                                     |
| [Authoring](/dev/skills/authoring)                | Documentation, architecture, pages and design decisions — the skills that write.                                                           |
| [Running the project](/dev/skills/pm)             | The task engine, the release and the work loop from the repository.                                                                        |
| [Workflows](/dev/skills/workflows)                | `make-idea` and `cleanup` — the plugin's unattended Claude Code workflows, from an idea to an opened PR and from a backlog to a clean one. |
| [Composing boards](/dev/compose)                  | How an agent composes one batch per coherent unit, anchored by relation, and how the server owns the layout.                               |
| [MCP for any client](/dev/mcp/clients)            | Registering the deploy's `/mcp` endpoint with Claude Code, Codex, Cursor, OpenCode, VS Code, Gemini CLI or any OAuth-capable MCP host.     |
| [MCP tool reference](/reference/mcp-tools)        | Every tool the MCP endpoint serves.                                                                                                        |

## Live loops and the raw wire [#more]

| Page                         | What it covers                                                                                                   |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| [Live pairing](/dev/pairing) | `vitrinka qa pair` — fix while the tester keeps testing.                                                         |
| [HTTP API](/dev/api/http)    | The contract the CLI, the MCP endpoint and the recorders all speak, family by family, and the live event stream. |