📋 Copy Blueprint Command { } Inspect JSON API Ground-Truth Source ↗

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor

### 1. The Workflow Bottleneck & Problem Statement Frontend and mobile clients crash in production when backend engineers rename or drop JSON response fields without updating shared contracts. ### 2. Synthesized Agent Architecture & Connected Stack **End-to-End API Schema & OpenAPI Contract Drift Enforcer** (`monorepo-zod-contract-enforcer`) is a verified production blueprint curated from **@mattpocockuk**'s real-world implementation. - **Primary Capability:** Audits backend route handlers, Zod schemas, and frontend fetch clients on every PR to prevent undocumented breaking API changes. - **Connected Tool Stack:** GitHub MCP, Git MCP, Mintlify MCP - **Execution Governance:** `Read-Only Discovery` → `Deterministic Policy Check` → `Ask-First Human Approval` - **Certified Builder Source:** [@mattpocockuk](https://github.com/colinhacks/zod) ### 3. Step-by-Step Implementation Blueprint 1. **Trigger & Data Ingestion:** Configure your agent routine to watch **GitHub MCP** on a scheduled cadence or event webhook. Treat all external text as untrusted data inside XML fences. 2. **Cross-System Enrichment & Verification:** Query **Git MCP** to validate live capacity, account status, or code state before generating recommendations. 3. **Human-in-the-Loop Action Staging:** Post a structured summary card to **Mintlify MCP** with 1-click approve/edit controls so your team retains full oversight. ### 4. Copy-Paste System Prompt & Routine Configuration ```text Implement the 'End-to-End API Schema & OpenAPI Contract Drift Enforcer' workflow curated with @mattpocockuk. 1. OBJECTIVE: Audits backend route handlers, Zod schemas, and frontend fetch clients on every PR to prevent undocumented breaking API changes. 2. CONNECTED TOOL STACK: GitHub MCP, Git MCP, Mintlify MCP 3. STEP-BY-STEP EXECUTION LOOP: - Step A (Ingest & Ground): Query live inputs from GitHub MCP and cross-reference state in Git MCP. - Step B (Analyze & Validate): Apply strict filtering rules, verify schema/policy constraints, and flag any anomalies or missing fields. - Step C (Stage & Report): Prepare the structured output, draft replies/tickets in Mintlify MCP, and request human confirmation before executing any external send or production write. ``` ### 5. Measured ROI & Production Impact - **Verified Outcome:** Blocks 100% of breaking API schema changes before code review. - **Builder Portfolio:** [Explore all capabilities by @mattpocockuk →](/u/mattpocockuk)

Tags: #monorepo-zod-contract-enforcer#use-case#engineering#mattpocockuk#github-mcp#git-mcp

View All 9 Items by @mattpocockuk →

mcp · ⚡ 93

Neon Serverless Postgres Branching & Instant Read-Clone MCP

Official Neon Serverless Postgres MCP server: create ephemeral database branches for testing migrations, run SQL queries, and compare branch schema diffs.

skill · ⚡ 86

Prisma & Drizzle Zero-Downtime Expand/Contract Migration Skill

Execute expand-and-contract Postgres schema migrations without table locks: nullable column addition, batched background backfill, concurrent index creatio

skill · ⚡ 94

Strict TypeScript AST & Runtime Zod Boundary Validation Skill

Enforce end-to-end type safety across API boundaries, environment variables, and LLM structured outputs using strict `tsconfig.json` flags and composable Z