hireproof-architecture

To safely modify Next.js API routes without breaking SSRF protections, apply architectural guardrails that preserve origin validation, rate limiting, and payload-size constraints during edits to security-sensitive audit endpoints.

The best way to update MCP tooling while maintaining agent workflow compatibility is to route fraud verdict logic through existing audit APIs and shared utilities, ensuring validation and logging hygiene remain intact.

To preserve rate limiting and validation when refactoring TypeScript schemas, constrain changes to established security boundaries and ensure schema updates do not bypass existing payload constraints or provenance checks.

You cannot use Cursor to implement product fraud decisions directly; operational integrity requires directing fraud verdict logic through the existing audit APIs and shared MCP tools to prevent misuse and maintain disclosure integrity.

The HireProof architecture skill supports both live and demo environments by guiding repository edits across Next.js App Router and SSE endpoints while keeping live versus demo disclosure behaviors intact and secure.

You should avoid bypassing the audit API for security-sensitive endpoint changes whenever outbound fetches, secret-handling rules, or evidence-backed user-facing copy are involved, as direct edits risk breaking disclosure integrity and provenance checks.