Use whenever a document is produced for the user to read and react to while it evolves: a brainstorm board, a plan, a design language, a prototype, a PR analysis, a review report, a live PDF. Also when a document must be registered, opened, listed, moved or retired, or a prototype's bindings checked. Not for code, tests or configuration, or any file nobody opens in a browser.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
aiview is the local viewer and index for the documents an agent writes for a person to read. The tool is <skill-dir>/aiview.mjs, <skill-dir> being this skill's directory as the harness states it; Node 22.5 or later. $A --help lists every verb with its flags; every verb takes --json, preferred when parsing.
| Root | Holds |
|---|---|
The checkout, <skill-dir> | code, dist/, dist-cli/; rebuildable |
The data home, $SWARMSTORM_HOME or swarmstorm_appdata in the OS home directory | aiview.sqlite, the server's pid and port files, every document under docs/<project>/ |
references/setup.md.Ask the tool for the path: a hand-built one is wrong on the next OS, the next machine, or in PowerShell.
A="node <skill-dir>/aiview.mjs"
$A status --json # cwdProject: the project this working directory belongs to
$A use <slug> # only if cwdProject differs from the default project; it moves no tab
F=$($A path 2026-08-24-topic.brainstorm.md) # the absolute path, joined for this OS
# write the document at $F
$A open "$F" --tag <topic>
open is the standard gesture, on creation: it registers the file, starts a detached server if none runs, and prints the URL. Its last line says what the person now sees (one tab shown or switched, updated in place, or no tab: give the link in chat); tell the person that and nothing more. Each tab keeps its own project: references/projects.md.docs/<slug>/; refiling is move <ref> --project <slug>, and status --json says which project claims a working directory.list already shows before inventing one.status --json reports no cwdProject: references/projects.md.YYYY-MM-DD-<topic>.<kind>.md, flat in the project's folder.--kind: brainstorm, plan, task, module, reference, prototype, workbench, pr-analysis, report, pdf, roadmap (one per project). A kind is a type of document; a topic is a tag.--group <slug> per piece of work, titled once with --group-title, at most one group per document.<topic>-plan, shared with its task documents and nothing else.--started <ISO> when the discussion began before the file existed.update. aiview.sqlite is the tool's to write, and scratch files stay unregistered.design-prototype skill.<stem>/ beside it, read only through the frame's bridge, per the create-workbench skill; a trace is a workbench. move carries the sidecar with the page./board page, never a document: swarm open adds the run's repository to it with aiview board --repo <path>, and aiview board alone prints its link. aiview draws it through swarm's client/reader.ts, a client of swarm's board server, and never opens swarm's store. /board#run=<id> opens one run's tab.pending add puts a card at the head of the document for each unit of work still running; pending done removes it when the section is written. On a fan-out, one card per subagent as it is dispatched, closed when its result lands, on the failure paths too. The properties and the wording: references/pending.md.
show <file|#id> --component <Name>... [--variant <v>] moves one tab to the prototype and lights those components (the tab already on its project, else the last used), dimming the rest, until the next show, until show --done sends that tab back to what the person was reading, or until the person stops it themselves. components <file|#id> lists every name on the page and its variants, and show refuses any other, listing the ones it has. It prints the link that does the same in a tab opened later, and its last line says which tab showed it; with no tab it says so, returns at once, and the link goes in chat. When to point and how to word the question: the point-at skill.
A skill that produces documents says "through the aiview skill", then states only its document's metadata: kind, tags, group, and a start time that predates the file. Command syntax and directories stay here.
A document opens on a part written for a person who was not there (a brainstorm board, and any kind that adopts it): references/human-part.md.
To describe the viewer, a mode or a toolbar to the person: references/viewer.md.
| Thought | Reality |
|---|---|
| "I'll show it as a claude.ai artifact instead" | Documents stay local and offline, in the data home. |
| "I'll run serve in a background task and watch it" | open and serve --detach daemonise; status finds the server. |
"I'll add --path pointing at where the documents are" | paths are working directories. Documents live in docs/<slug>/. |
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produces a board in aiview holding the decisions, the diagrams and what was investigated. Not for a swarm of seats working it (brainswarm), not for an implementation plan and not for bug fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a person wants a swarm of role seats to work a topic on the swarm board under a chosen protocol: a brainstorm (ideas before any judgment), a debate (questions argued to decisions, a skeptic endorsing) or an editorial (one text drafted, read by seats standing for its readers, revised), a protocol or template the project keeps as a `protocol-<name>` skill (or an older `brainswarm-<name>` one), or a custom protocol recommended for the person's intent, or a seat's brief names a brainswarm protocol. Produces the run's record in aiview, written by the orchestrator alone. Not for one person thinking aloud with the agent (brainstorm, interview) and not for a plan's slices (execute-plan).
日本語の概要は準備中です。原文の説明を表示しています。
Use when dispatched to cold-read a plan, as an agent that was not in the conversation that wrote it, to say whether it can be carried out from the document alone. Produces what the reader would build, its questions, and a verdict, ready or not ready, repeated as the writer fixes the plan. Not for judging the design (interview, pr-review), not for the mechanical checks (aiview plan check, tracker check), and not for writing the plan (write-plan).
日本語の概要は準備中です。原文の説明を表示しています。
Use when code is hard to follow and is to be audited or reworked: long if/else or switch chains, cascades of type checks or parse attempts, kind fields compared to strings, flag parameters, deep nesting, a function hard to read. Also for complexity guardrails, or one long conditional function pasted. Produces a ranked audit of families, one family reworked behind characterization tests, or the guardrails.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a page is wanted to work on something with the person during development, fed the project's real data (comparing model answers, walking an agent call by call, measuring an output against its template), when such a workbench has to change, be reworked or its feed broke, or mid-session when turns went into aligning with the person on how to do a kind of work that recurs and real project data could show it. Produces the page in aiview, kind `workbench`, and the project's `workbench-<bench>` skill with its feed and operating steps. Not for designing a product screen (design-prototype) or verifying user stories (verification-skill-create).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a person asks to design a new module's interface or to rework an existing module so that it hides much behind little, in any tier (backend, frontend, test support, tooling), or says a module's callers know too much about it. Produces a module document in aiview, how a caller uses it, its one public entry point as signatures, what stays outside and the gap from today, discussed with the person until agreed. Not for writing the task that carries the rework out (orchestrate's tasks) and not for the rework itself.
日本語の概要は準備中です。原文の説明を表示しています。