Use this skill when contributing to InsForge's shared schema package. This is for maintainers editing published Zod contracts, exported types, and shared API payload definitions consumed by InsForge packages in this repo and other InsForge tooling.
Use this skill for packages/shared-schemas/ work in the InsForge repository.
packages/shared-schemas/src/**@insforge/shared-schemas package, including consumers not present in this repositoryTreat packages/shared-schemas/ as the source of truth for cross-package payloads.
Keep schemas organized by domain.
*.schema.ts and *-api.schema.ts split when it fits the current package pattern.packages/shared-schemas/src/index.ts aligned with the intended public API.Use schema changes as a synchronization trigger.
packages/dashboard/.packages/*, frontend/, and backend/ before finishing.any type. Shared contracts should stay explicit and trustworthy across package boundaries.cd packages/shared-schemas && npm run buildcd backend && npx tsc --noEmitcd packages/dashboard && npm run typecheckRun package-specific tests as needed where behavior changed. If external consumers such as MCP or SDK cannot be validated from this repo, say that clearly instead of implying they were covered.