메뉴
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