mandate402

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.

Load when applying core engineering principles such as SOLID, OOP, encapsulation, abstraction, DRY, KISS, YAGNI, composition, or dependency design.

Load when creating or updating contributor onboarding, setup docs, README guidance, local development instructions, or new maintainer handoff material.

Load when creating or reviewing production-grade frontend components, pages, layouts, visual polish, interaction design, or non-generic UI aesthetics.

Load when reviewing or changing Mandate402 accessibility, keyboard flow, focus states, modals, tables, status semantics, color contrast, aria labels, or destructive UI flows.

Load when changing Mandate402 API routes, request/response envelopes, status codes, Zod validation, idempotency, correlation IDs, auth failures, or route-level tests.

Load when changing Mandate402 APIs, auth, validation, persistence, request-path logic, database behavior, limits, expected traffic handling, CI/CD, or deployment-grade backend runtime semantics.

Load when the backend task is broad or spans multiple runtime lanes in Mandate402 and you need a strict router for backend-runtime, blockchain, and workers plus the shared rules for validation, security, DB behavior, and deployment-grade execution.

Load when changing Mandate402 chain-facing code on Morph such as network manifests, RPC handling, contract registry, ABI ownership, treasury execution, chain health, or frontend/backend boundaries that depend on onchain truth.

Load when changing Mandate402 Solidity contracts, Foundry tests, deploy scripts, ABI ownership, Morph explorer verification, contract metadata, or artifact hygiene.

Load when changing Mandate402 frontend pages, components, visual states, responsive behavior, landing layout, or UI polish and you need strict project-specific implementation rules for stack, tokens, page scope, accessibility, performance, and lane ownership.

Load when adding or changing Mandate402 frontend tests, UI regression checks, React state assertions, form flows, route-driven UI behavior, or frontend verification strategy.

Load when changing Mandate402 treasury settlement assets, token decimals, Pyth feeds, fiat conversion, stale oracle handling, facilitator settlement assumptions, or onchain payment amounts.

Load when changing Mandate402 Postgres, Supabase pooler/direct URLs, migrations, store integrity, locking, transactions, read/write scaling, or persistence tests.

Load when changing Mandate402 GitHub Actions, semantic-release, changesets, repo safety checks, branch protection, smoke tests, release notes, or public-remote safety.

Load when checking or changing Mandate402 responsive layouts, mobile behavior, desktop density, landing split layout, modals, tables, drawers, or visual QA.

Load when changing Mandate402 auth, secrets, worker auth, production env gates, vendor/facilitator boundaries, security headers, sensitive errors, or fail-closed runtime behavior.

Load when choosing, adding, fixing, or reporting Mandate402 verification across Vitest, route tests, store tests, Foundry, Go tests, smoke checks, typecheck, lint, or build.

Load when changing Mandate402 worker execution, durable task queues, leases, retries, internal worker routes, background processing, reconciliation ownership, or scheduler-facing runtime behavior.

Load when changing Mandate402 x402 payment attempts, vendor dispatch, facilitator separation, payment identifiers, receipts, execution_unknown, status correlation, or reconciliation truth.

Load when changing Mandate402 main.go, Go x402 vendor routes, Morph HMAC signing, facilitator config, provider data, status endpoints, or Go verification.

Load when a task needs real browser automation, UI flow debugging, screenshots, form interaction, visual checks, or frontend behavior validation.

Load when reviewing Mandate402 for security risks across API, auth, database, payment, x402, worker, Morph, contract, or release boundaries.

Load when Mandate402 work touches EVM contracts, chain integration, signing, custody, onchain/offchain boundaries, audits, or blockchain operations.

Load when working on Postgres schema, migrations, Supabase pooling, query performance, indexes, RLS, or database scaling decisions.

Load when Mandate402 requirements need architecture boundaries, component design, interface contracts, scaling choices, or integration trade-offs.

Load when turning PRDs, requirements, acceptance criteria, sprint scope, or feature specs into structured test cases and coverage matrices.

Load when implementing complex TypeScript types, generics, conditional types, mapped types, template literals, utility types, or compile-time safety.

Load when reading or writing TypeScript or JavaScript files, TSX components, JS modules, or tsconfig settings.

Load when solving advanced TypeScript or JavaScript issues involving type-level programming, performance, migrations, tooling, or complex diagnostics.

Load when planning, building, reviewing, or improving UI/UX, layouts, palettes, typography, components, interaction states, accessibility, or responsive design.

Load when writing, reviewing, or refactoring React/Next.js components, pages, data fetching, bundle optimization, rendering behavior, or performance patterns.

Load when writing or debugging Vitest unit tests, mocks, fixtures, coverage, filtering, or Next.js TypeScript test harness behavior.

Load when reviewing UI code, checking accessibility, auditing design, reviewing UX, or checking web interface best practices.

Load when testing Solidity contracts, Foundry suites, fork tests, gas behavior, contract verification, or blockchain integration scenarios.