Stats
Actions
Tags
From agent-primary-ts-starters
Add zod to a TypeScript npm project and install the boundary-only parsing convention. Use when starting a new TS project that needs runtime schema validation, or when layering zod onto an existing TS npm project — even if the user doesn't explicitly say "zod" or "validation".
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-primary-ts-starters:ts-npm-zod-starterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this when adding zod to a TypeScript npm project. In a monorepo, edit the workspace the user names — ask if it isn't named.
Use this when adding zod to a TypeScript npm project. In a monorepo, edit the workspace the user names — ask if it isn't named.
zod is in dependencies of the target package.json.npm add zod
zod ships runtime code, so it belongs in dependencies (not devDependencies). When zod is already declared, keep its current version unless the user asks for a change.
z.parse / z.safeParse. Downstream code takes the parsed value as trusted and does not re-parse.z.infer<typeof Schema> is the single source of truth for the static type — let it stand alone instead of declaring a parallel interface or type alias.Why: parsing at every layer doubles the work and obscures where the trust boundary actually is.
When the project has a concrete shape worth validating, add its schema under src/schemas/<name>.ts, exporting the schema, its z.infer type, and a parse(raw: unknown) wrapper used at the boundary.
When src/schemas/ already exists, defer to the project's existing convention.
npx tsc --noEmit passes.zod appears under dependencies in package.json.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub kongyo2/agent-primary-ts-starters --plugin agent-primary-ts-starters