# Referenční přehled skillů (https://docs.vitrinka.ai/cs/reference/skills)



{/* Code generated by tools/gen-docs-skills from internal/skillcat. DO NOT EDIT. Regenerate: go run ./tools/gen-docs-skills */}

Kit dodává **Vitrinka** (core — ten `vitrinka setup` instaluje vždy), **Vitrinka PM**, **Vitrinka QA** a **Vitrinka Experimental** (volitelný, jen Claude Code). Každý plugin dělí své skilly do modulů — stejná jména, podle kterých se vymezuje katalog MCP — a `vitrinka setup modules` je zapíná nebo vypíná pro zařízení či projekt. Holé `/<skill>` funguje, pokud si jméno nenárokuje jiný nainstalovaný příkaz; `/<plugin>:<skill>` funguje vždy (`$<skill>` v Codexu). Popisy níže pocházejí přímo z katalogu pluginu a zůstávají anglicky.

## Vitrinka [#vitrinka]

The vitrinka experience: capture UI work as journeys and walkthroughs, author documents, pages and diagrams, brainstorm on a decision board, and service a board's annotation queue. Registers nothing itself — `vitrinka setup` adds the MCP endpoint. Instaluje každý `vitrinka setup`. Claude Code a Codex.

### Core [#core]

Boards, capture, authoring, the annotation loop. Vždy zapnuté.

#### `publish` [#publish]

Use when asked to capture or visualise UI work on vitrinka — 'publish', 'screenshot', 'journey', 'walkthrough', a testing-suite board; authored documents, pages and diagrams are artifact. — `/vitrinka:publish` v Claude Code, `$publish` v Codexu.

#### `artifact` [#artifact]

Use when asked to author a standalone document, page, diagram or living-docs board on vitrinka — 'artifact', 'vitrinka this', 'publish this analysis/report', 'make this a page/diagram', 'document this repo'; capturing UI work is publish. — `/vitrinka:artifact` v Claude Code, `$artifact` v Codexu.

#### `brainstorming` [#brainstorming]

Use before any creative work — a new feature, component, capability or behaviour change — and on 'brainstorm', 'design this', 'think this through with me' before code is written. — `/vitrinka:brainstorming` v Claude Code, `$brainstorming` v Codexu.

#### `listen` [#listen]

Use when a session should service a vitrinka annotation board live — '/vitrinka:listen \[board-slug]' from the app's repo, 'listen to the board', 'watch the annotations'; a backlog is resolve. — `/vitrinka:listen` v Claude Code, `$listen` v Codexu.

#### `resolve` [#resolve]

Use when a board's annotation backlog should be worked down — '/vitrinka:resolve \[board-slug]' from the app's repo, 'resolve the board', 'work through the annotations'; live servicing is listen. — `/vitrinka:resolve` v Claude Code, `$resolve` v Codexu.

## Vitrinka PM [#vitrinka-pm]

The work loop on top of core: pick a task up, hand it back, file what you spot, drive the task engine and a project's release, keep personal todos and reminders. Ships the session hooks that stamp a run, cue a pickup and gate the hand-back. Instaluje se automaticky; vypnete přes `vitrinka setup modules`. Claude Code a Codex.

### PM [#pm]

The task engine: pickup, hand-back, intake, triage, release boards. Zapnete nebo vypnete přes `vitrinka setup modules`.

#### `pickup` [#pickup]

Use when a vitrinka task id or URL arrives in the prompt, or '/pickup \<id|url>' is invoked, to start work in a fresh session; ending work is handoff, filing what you will not do here is spot. — `/vitrinka-pm:pickup` v Claude Code, `$pickup` v Codexu.

#### `handoff` [#handoff]

Use when work on a bound vitrinka task ends — '/handoff', the Stop gate asking for a hand-back, or a session wrapping up; starting a task is pickup. — `/vitrinka-pm:handoff` v Claude Code, `$handoff` v Codexu.

#### `tasks` [#tasks]

Use when working a project's task engine from the repo — '/tasks \[list|intake|file|epic|rule]', 'file a task', 'find the X epic', 'file this under the X epic', 'plan the epic', 'triage intake', 'sprint start', 'add an automation rule'. — `/vitrinka-pm:tasks` v Claude Code, `$tasks` v Codexu.

#### `release` [#release]

Use when driving a project's vitrinka release from the repo — '/release \[status|refresh|cut|notes]', 'cut the release', 'refresh the release board', 'what is in the next release', 'write the release notes'. — `/vitrinka-pm:release` v Claude Code, `$release` v Codexu.

### Me [#me]

Personal todos, milestones and reminders the session judges. Zapnete nebo vypnete přes `vitrinka setup modules`.

#### `me` [#me]

Use for personal todos, reminders, milestones and the agenda in vitrinka — '/me \[add|list|done|drop|remind|milestone|agenda]', 'remind me', 'add a todo', 'what is ripe', 'add to today's todos \<task>', 'plan X for tomorrow', 'what's on my agenda'. — `/vitrinka-pm:me` v Claude Code, `$me` v Codexu.

## Vitrinka QA [#vitrinka-qa]

The testing pipeline on top of core: test like a user, process recorded sessions, pair with a human who is testing live, review a board's screens or a journey, and spot what you will not fix now. Instaluje se automaticky; vypnete přes `vitrinka setup modules`. Claude Code a Codex.

### QA [#qa]

Recorded sessions, live pairing, exploratory user-testing, AI review. Zapnete nebo vypnete přes `vitrinka setup modules`.

#### `usertest` [#usertest]

Use for 'user test this', 'explore the new feature', 'QA this like a user', 'run the tests and publish', or 'vitrinka qa run|usertest' from the app's repo; a human's recorded session is sessions. — `/vitrinka-qa:usertest` v Claude Code, `$usertest` v Codexu.

#### `review` [#review]

Use when asked to review a vitrinka board's screens or a journey pass for defects — 'review the board', 'review this journey', '/vitrinka-qa:review \[board] \[journey] \[eve]', 'have Eve review it'; fixing accepted findings is resolve, live human annotations are listen. — `/vitrinka-qa:review` v Claude Code, `$review` v Codexu.

#### `sessions` [#sessions]

Use for a recorded user-testing session or its backlog — 'process the session', 'pending sessions', 'generate journey tests from the session' — and for 'vitrinka qa session archive|continue'; exploratory testing by you is usertest. — `/vitrinka-qa:sessions` v Claude Code, `$sessions` v Codexu.

#### `pair` [#pair]

Use when a human is user-testing the app live and wants bugs fixed as they appear — '/vitrinka-qa:pair' from the app's repo, 'pair with me while I test', 'fix while I test'; a backlog of annotations is resolve. — `/vitrinka-qa:pair` v Claude Code, `$pair` v Codexu.

#### `spot` [#spot]

Use for '/vitrinka-qa:spot \<what you saw>' or whenever a 'later', 'out of scope' or 'someone should decide' thought appears mid-work on a vitrinka task; ending work is handoff. — `/vitrinka-qa:spot` v Claude Code, `$spot` v Codexu.

## Vitrinka Experimental [#vitrinka-experimental]

Flows still proving themselves, beside core: build-idea takes a committed brief to a draft PR with one quick check, make-idea runs a brainstorm into it, test asks which lanes and device checks to run, cleanup reconciles a project's tasks against reality. Claude Code only; opt in with `vitrinka setup --experimental`. Zapnete přes `vitrinka setup --experimental`. Jen Claude Code.

### Experimental [#experimental]

Unattended workflows and ask-first device testing, opt-in. Zapnete nebo vypnete přes `vitrinka setup modules`.

#### `build-idea` [#build-idea]

Use when a committed brief should become a running feature and a draft PR with no device pass — '/vitrinka-experimental:build-idea', 'build it and hand it to me'; the device pass afterwards is test. Claude Code only, as a workflow. — `/vitrinka-experimental:build-idea`.

#### `make-idea` [#make-idea]

Use when an idea should become a running feature and a draft PR, deciding only at the brainstorm and the look — '/vitrinka-experimental:make-idea \<idea>', 'make this idea', 'build this end to end'. Claude Code only, as workflows. — `/vitrinka-experimental:make-idea`.

#### `test` [#test]

Use when a built branch should be tested on viewports, simulators or iOS 26 Safari at a chosen thoroughness — '/vitrinka-experimental:test', 'test this on iOS', 'run the device pass'. Asks ONE batched question, then runs unattended; Claude Code only. — `/vitrinka-experimental:test`.

#### `cleanup` [#cleanup]

Use when a project's tasks need cleaning against reality — '/vitrinka-experimental:cleanup \[project]', 'clean up the tasks', 'dedupe the backlog', 'fix the statuses against the code and PRs', 'close finished epics'. Claude Code only: it runs as a workflow. — `/vitrinka-experimental:cleanup`.