Flovart — скилл

---
name: flovart
description: Work in the user's visible Flovart Workflow canvas. Use when the user asks to open Flovart, look at or change their Workflow, build shots or generation nodes, or run image and video generation.
---

# Flovart

Flovart is the visible Workflow canvas the user is looking at. You change it
through the local `flovart` CLI; the user sees every change live. Flovart
prepares its own local session: never ask the user for connection details and
never rebuild a connection flow in the conversation.

The CLI needs Node.js 22.19.0 or newer. In this source checkout, when the
packaged `flovart` command is not installed, use the repository entrypoint
instead, for example `npm run flovart:cli -- ensure --json`. Do not use `npx flovart-cli` as an automatic fallback: an unpublished checkout can make
npx fetch an unrelated package.

## Prepare for this job

Do these in order at the start of every task. Each step has a stop condition;
never skip ahead. Details are in `references/environment.md`.

1. **Understand the request.** Decide what the user wants to see on the canvas
   when you are done, and whether it needs paid generation. Ask only when a
   different reading would change the result.
2. **Make Flovart ready.** Run `flovart ensure --json`. Continue only when it
   returns `ok: true` and `state: "ready"`; otherwise tell the user the public
   state it returned and stop. `ensure` also opens the user's browser on the
   canvas when needed.
3. **Get on the user's canvas.** Run `flovart status --json`, then
   `flovart workflow.inspect --agent-identity <host> --json`. Compare the
   project title, node titles and node count with what the user describes or
   shows you. If they disagree, you are reading another canvas: stop and fix
   that first (see "Operate the user's visible canvas").
4. **Check AI services only when generation is needed.** Run
   `flovart provider.status --json`. It lists configured services with masked
   keys only. If the route you need is missing, tell the user where to add it
   in Flovart Settings (`references/providers.md`). Never ask for a key in the
   conversation, and never read, write or move one yourself.
5. **Quote and agree.** Before any paid run, tell the user how many runs, which
   model, and what each run is for, and wait for their go-ahead.
6. **Work and narrate.** Make the change, inspect again, and tell the user what
   is now on their canvas in their terms.

## The stable surface

Use `ensure` to prepare, then these five operations for all normal work:
`status`, `workflow.inspect`, `workflow.selection.get`, `workflow.apply`, and
`workflow.node.run`.