shared-schemas

Manage and update shared Zod schema contracts for InsForge packages.

12.7k|1.1k|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/InsForge/InsForge --skill shared-schemas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shared-schemas
Source: https://github.com/InsForge/InsForge/tree/main/.agents/skills/insforge-dev/shared-schemas
Command: npx skills add https://github.com/InsForge/InsForge --skill shared-schemas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit addresses the need for maintainers to edit and manage InsForge's shared schema package, ensuring consistency across various InsForge packages and tooling.

Core Features & Use Cases

  • Schema Editing: Allows maintainers to edit published Zod contracts, exported types, and shared API payload definitions.
  • Cross-Package Consistency: Ensures that shared payloads are consistent across different InsForge packages and tooling.
  • Use Case: When a new contract is needed for a shared payload across multiple InsForge packages, this Skill unit can be used to define and manage that contract.

Quick Start

Run the cd packages/shared-schemas && npm run build command to build the shared schemas.

Frequently Asked Questions about shared-schemas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage shared Zod contracts for API payloads across multiple packages?

To manage shared Zod contracts for API payloads across multiple packages, use this Skill to edit published schemas, exported types, and payload definitions, ensuring cross-package consistency throughout the InsForge platform.

How do I build and validate shared schema changes for InsForge?

To build and validate shared schema changes for InsForge, run the command `cd packages/shared-schemas && npm run build`, which requires npm to compile and validate the updated Zod contracts and payload definitions.

When do I need to update cross-package schema definitions?

You need to update cross-package schema definitions when a new Zod contract is required for a shared API payload across multiple InsForge packages, ensuring that shared payloads remain consistent across different tooling.

Does the shared schema package require any specific dependencies to edit payload definitions?

Editing the shared schema package requires npm to build and validate schema changes. The Skill manages Zod contracts and exported types to maintain API payload consistency across InsForge packages.

What is the best way to ensure cross-package consistency for shared API payload definitions?

The best way to ensure cross-package consistency for shared API payload definitions is to centralize Zod contracts and exported types in a shared schema package, validating updates through an npm build process before deployment.

Can I use this Skill to edit published Zod contracts for InsForge tooling?

Yes, you can use this Skill to edit published Zod contracts, exported types, and shared API payload definitions for InsForge tooling, ensuring that all shared payloads remain consistent across different packages.