interop-forge

What This Skill Does

Interop Forge is a specialized architectural skill for OpenClaw designed to solve the complexities of monorepo communication. In modern web development, teams often manage multiple frontend and backend applications within a single repository (using tools like Turborepo, Nx, or pnpm workspaces). Over time, these projects suffer from 'siloed' development where types, API schemas, and authentication strategies diverge. Interop Forge acts as your senior integration architect, systematically aligning these disparate apps.

This skill automates the creation of shared contract packages, enforces API-first development through OpenAPI specifications, and scaffolds standardized MCP (Model Context Protocol) servers for every application. By normalizing these interfaces, Interop Forge ensures that your AI agents and micro-services can communicate without friction. It is stack-agnostic, meaning it intelligently scans your repository to detect your specific technologies (e.g., Supabase, Vercel, GCP) and applies the correct idiomatic code patterns. It handles the heavy lifting of TypeScript configuration, Zod schema synchronization, and cross-app JWT forwarding, all while maintaining a strict 'no-touch' policy regarding your sensitive local environment files.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/guifav/interop-forge

Ensure your terminal is pointed at the root of your monorepo workspace to allow the skill to scan your package.json and configuration files correctly.

Use Cases

• Shared Type Sync: Creating a 'contracts' package in your monorepo that holds all shared Zod schemas and TypeScript interfaces to prevent type drift between a Next.js frontend and a Node.js backend.
• AI Orchestration: Scaffolding MCP servers for existing apps to expose their internal API functions as tools that an AI agent can execute.
• API-First Design: Generating OpenAPI specs for legacy internal services to enable automated SDK generation for other apps in the monorepo.
• Cross-App Auth: Implementing secure credential propagation so that an authenticated user session in your 'Admin' portal is recognized by your 'Reporting' micro-app.

Example Prompts

1. "Interop Forge, survey my monorepo and create a 'shared-types' package that standardizes User and Order schemas across our Next.js dashboard and our Express internal API."
2. "I need to expose my Supabase-backed inventory service to an AI agent. Can you scaffold an MCP server that uses the current OpenAPI spec and maps the inventory lookup tools?"
3. "Refactor our authentication handshake so that our 'Billing' app accepts JWTs forwarded from our 'Main' app; provide the necessary shared utility functions."

Tips & Limitations

• Mandatory Planning: Always allow the skill to complete its 'Planning Protocol' before authorizing any file generation. This ensures the architecture is sound.
• Non-Destructive: The skill is designed to extend existing projects, not rewrite them. It will suggest additions like new packages/ or updated turbo.json pipelines.
• Credential Security: Note that this skill is 'credential-aware' but 'credential-safe'. It will generate code that accesses process.env but it will never read or commit your actual secret values.