メニュー
Load when choosing, adding, fixing, or reporting Mandate402 verification across Vitest, route tests, store tests, Foundry, Go tests, smoke checks, typecheck, lint, or build.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Load when backend API work touches authentication, authorization, rate limiting, CORS, input validation, public endpoints, or security remediation in Mandate402.
Load when architecture choices, ADRs, trade-off evaluation, technical debt, or pattern selection need explicit decision records for Mandate402.
Load when designing or reviewing backend systems, APIs, auth, databases, security, performance, scalability, CI/CD, monitoring, or production runtime patterns.
Load when reviewing Mandate402 code for secrets, auth, authorization, input validation, payment safety, blockchain integration, or release security risks.
Load when testing Cloudflare Workers, Vitest worker pools, binding mocks, integration tests, coverage, or worker test failures.
Load when planning or building React/Next.js UI with CO-STAR structure, design tokens, dashboards, hero sections, or custom UI prompts.
| name | mandate402-test-harness |
| description | Load when choosing, adding, fixing, or reporting Mandate402 verification across Vitest, route tests, store tests, Foundry, Go tests, smoke checks, typecheck, lint, or build. |
package.jsonvitest.config.ts.github/workflows/ci.ymlreferences/test-harness-matrix.mdTESTS.mdRun focused tests first, then broaden to type/lint/build when shared contracts changed.
Final reports must name exact commands run and any known gaps.
main.go changes