Use at every point of a conversation where one of this collection's skills would serve the person better than going on as is, and they have not named it: an idea still vague or choices left open (offer the interview), decisions worth keeping (a brainstorm board), agreement on something to build (a plan, or a swarm with its protocol filled in), a question to decide or a text to write from several viewpoints (a brainswarm), a run that just closed (its follow-up). Produces one offer in one line; never runs the skill unasked. Not for explaining how the collection works, mid-work or to a new person (help). Not for running any of those skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
The person should never have to know a skill's name to get its help. You notice the moment one fits and offer it in one line, with why and what it would produce; the person says yes, no, or something else. A yes loads that skill; it takes over from there.
| You notice | You offer | It produces |
|---|---|---|
| an idea still vague, several choices open, the person hesitating or contradicting an earlier answer | the interview skill: "Want me to interview you on this, one question at a time?" | the decisions settled one by one, a recommendation on each |
| decisions taken in chat that someone will need later | the brainstorm skill: "Keep this as a board?" | a board in aiview: the decisions, diagrams, what was looked into |
| agreement on something to build, larger than one sitting | the write-plan skill: "Write it as a plan?" | the plan, its phases and seats, run later on the board |
| agreement on work that splits into parts or must be seen working, no plan needed | the swarm skill, with the protocol filled in: "Run it as build-verify: 3 builders, verifiers sized from the steps (2 here) each on its own instance, until ready (cap 5), effort low. Adjust or go?" | the run on the board, the merged branch |
| a question to decide, options to explore, or a text to write, better from several viewpoints | the brainswarm skill, its protocol named: debate, brainstorm, editorial | the run's record in aiview |
| a screen to build or change | the design-prototype skill | a prototype in the project's design language |
| a project's conventions just decided, or about to be | the write-conventions skill | the rule in the conventions file |
At a run's close, its follow-up: a brainstorm or a debate settled → a plan; a plan approved →
its run, with build-verify when the result must be walked; a run whose setup will recur → keep it
as the project's protocol-<name> skill (the orchestrate skill's protocols); a delivery to go
over together → the validate-delivery skill.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.