Enforce Valibot schema-first typing for runtime-validated TypeScript boundaries.
npx skills add https://github.com/niconiahi/ethernauta --skill conventions-niconiahi
Please help me install this Agent Skill. Skill: conventions Source: https://github.com/niconiahi/ethernauta/tree/main/skills/conventions Command: npx skills add https://github.com/niconiahi/ethernauta --skill conventions-niconiahi
This Skill prevents type drift by requiring that every value-bearing boundary be defined with a Valibot schema first, then typed via InferOutput, ensuring the runtime contract and compile-time contract always agree.
Ask the AI to follow the monorepo rule by defining a Valibot schema for any new boundary value, deriving the TypeScript type from it, and parsing the value at function entry before using it.
High-intent search queries and answers about installing and using this skill.
Schema-first typing is enforced by declaring Valibot schemas for every runtime-validated boundary and deriving TypeScript types via v.InferOutput. This ensures the runtime contract and compile-time contract always agree without hand-written interfaces.
Type JSON-RPC envelopes and Chrome runtime messaging by defining Valibot schemas for each payload structure, then parsing the values at function entry before use. This guarantees accurate TypeScript types for cross-context messages.
Prevent type drift by requiring every value-bearing boundary—function inputs, outputs, storage records, and window postMessage payloads—to be defined with a Valibot schema first, then typed via InferOutput to eliminate unsafe casting.
Yes, Valibot is required to enforce schema-first typing in this workflow. You must declare Valibot schemas with parse at boundaries and derive types via v.InferOutput, forbidding hand-written interfaces and bypassing casts.
Your TypeScript type may not match your runtime JSON-RPC payload because hand-written interfaces lack runtime validation. Defining a Valibot schema first and deriving the type via InferOutput ensures both contracts agree.
No, hand-written interfaces for storage records are forbidden in a schema-first monorepo. You must declare Valibot schemas with parse at boundaries and derive types via v.InferOutput to ensure runtime and compile-time contracts match.
niconiahiEnforce TypeScript and Valibot boundary validation rules in the ethernauta monorepo.
djankiesValidate external data against Zod schemas for runtime type safety.
Ferhatr10Enforce module boundaries and explicit public interfaces in Python projects.
tundrarayEnforce React/TypeScript type safety with Zod schemas and runtime validation.
