Set up unit testing with /tests or /tests unit, or explicitly set up browser and end-to-end testing with /tests browser. Reuse or install a suitable test runner, add one example or smoke test, document commands, and verify. Use check for one-time live verification.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
First action: Before project inspection, preflight, or any other tool call,
publish running to blueprint/.state/run.json using the dashboard activity
contract in AGENTS.md. Use tests as the command for either setup mode.
/tests or /tests unit: set up stack-native unit testing. Read and follow
reference/unit.md only./tests browser: set up a repeatable browser harness. Read and follow
reference/browser.md only./tests Playwright remains a unit request with a runner
preference to clarify, not permission to install browser automation.Load only the selected reference. Do not read both references preemptively. Treat any remaining runner or stack arguments as preferences to verify against project files, never as permission to expand the selected setup.
Follow the selected reference's inspection, approval, verification, and report steps. Unit setup may add tests to an existing Verify command; browser setup must not add its slower gate to Verify or CI without a separate request or an existing project requirement. Neither mode creates CI just by being invoked. Do not commit, merge, push, publish, or begin product feature work.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup. Use for /adopt or requests to bootstrap Blueprint into an established app. Use onboard for a fresh scaffold.
日本語の概要は準備中です。原文の説明を表示しています。
Audit current changes, a path, or the full project for quality, security, performance, or test problems and record durable findings. Independent mode prepares or completes a fresh-reviewer checkpoint handoff. Use for /audit, independent review, security review, code quality review, dead code, duplication, or standards drift.
日本語の概要は準備中です。原文の説明を表示しています。
Run one explicit bounded Blueprint spec and implementation pass through configured quality gates, then stop before completion or external actions. Use only when the user directly invokes /autopilot, $autopilot, or asks for Autopilot.
日本語の概要は準備中です。原文の説明を表示しています。
Brief an upcoming build-plan feature without writing files. Explain scope, dependencies, affected areas, size, and likely splits for the next item or a named item. Use for /brief, feature previews, what comes next, or build-order decisions before /feature.
日本語の概要は準備中です。原文の説明を表示しています。
Check the running app, CLI, or server against the active spec's done-when criteria and capture observable pass or fail evidence without editing source. Use /check to verify real feature behavior, or /check guide [latest|scope] for a read-only manual walkthrough: how to test manually, where to click, expected and incorrect results, or a human review path.
日本語の概要は準備中です。原文の説明を表示しています。
Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook. Use for /ci, GitHub Actions setup, pull-request checks, automatic checks, pre-push hooks, or aligning typecheck, test, and build verification.
日本語の概要は準備中です。原文の説明を表示しています。