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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.