Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Explore the codebase to answer "how does X work?" questions. Produce architectural explanations at the level of a senior engineer onboarding onto a subsystem, enough to build a working mental model, not so much that it reads like annotated source code. For this repository, explain maintained NeoHaskell framework, language, and toolchain internals. Trace only the mechanisms relevant to the question.
Follow the delegation instructions in AGENTS.md. Use the current environment's configured exploration and explanation roles and its available delegation interface. Inherit supported runtime defaults when no role override is configured; report an unsupported override rather than inventing a fallback identifier. Every delegate investigates source read-only and must not edit files. Use enforced read-only access when available; otherwise state the no-write constraint in the task. Select only reasoning and speed settings supported by the current environment.
For source navigation in this repository, use the Codemap reference to locate maintained source, signatures, and likely references. Read each source location before using it as evidence.
If the scope is ambiguous, state your interpretation and explore. The user can redirect.
references/explainer-prompt.md without the explorer-findings section. Go to step 4.When in doubt, take the simple path.
Decompose the question into 2 to 4 angles, each a distinct slice of the subsystem. Launch the explorers concurrently within the available delegation capacity, each with references/explorer-prompt.md and its angle filled in.
Once all explorers have returned, spawn one explainer with references/explainer-prompt.md and every explorer's findings filled in.
Present the explainer's output. Light edits for clarity or context from the conversation are fine. Do not substantially rewrite it.
The explanation uses the sections defined in references/explainer-prompt.md, dropping any that do not apply: Overview, Key Concepts, How It Works, Where Things Live, Gotchas.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect or supervise a PR or stack through review and CI to merge-ready, using current GitHub evidence and the requested mode.
日本語の概要は準備中です。原文の説明を表示しています。
Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you benchmark or report a measured speedup or regression, including complete framework flows and compilation of projects that consume the framework.
日本語の概要は準備中です。原文の説明を表示しています。
Restate the last message in plain human language, with no jargon.
日本語の概要は準備中です。原文の説明を表示しています。
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
日本語の概要は準備中です。原文の説明を表示しています。