Use when about to ask the person a question, answer one of theirs, or explain something to them, about a screen, a region or a component of the interface: in an interview, a plan, a board, a review or plain chat. Also when the person says they do not see what is meant on a screen. Finds the screen's prototype and points the person's viewer at the components concerned, so the question or the answer is given in the prototype's own names with the thing lit in front of them. Not for designing or changing a prototype (design-prototype), and not for a question with no screen in it.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
A screen is talked about with the screen in front of the person, in the prototype's own names, whether the agent is asking or answering.
aiview skill: list --kind prototype --tag <project>, or the one the person named. Read the prototype that draws the screen, the screen's own file and never the library it pulls from, and run components on it. Its page and variants lines are the vocabulary: every name the person can be shown on that page.file:line. A comparison with another screen points at the screen the decision changes, and names the other by its prototype and component.show <prototype> with --component <Name> once per component, and --variant when they exist only in one. Three components at most, the ones the question is about. A name the command refuses is not on that page: go back to 1, never rephrase around it. show writes each name on the component it outlines, so the question uses the same names, and carries the link the command prints.show replaces the last. Questions about different regions are asked one at a time, the one the others depend on first.show --done: the person's tab goes back to what they were reading before the first pointer. Between two questions in a row there is no --done: it closes the run.file:line. A layout that exists nowhere goes to the design-prototype skill first, never described in prose for the person to choose in.An answer follows the same steps: the person asks where something is, what a name means or how two regions relate, and the reply points at it before it explains, with the link in the reply, and show --done once they have it. "Which one is that?" is answered by a show, never by a longer description.
tabs: 0 in the command's answer means no viewer is open: the link in the question is how the person gets there.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。