CommunityProgramación y desarrollogithub.com

pproenca/zod

Mejores prácticas de validación de esquemas Zod para seguridad de tipos, análisis y manejo de errores.

¿Qué es zod?

Esta habilidad proporciona las mejores prácticas para utilizar Zod en la validación de esquemas, garantizando la seguridad de tipos, el análisis sintáctico correcto y el manejo robusto de errores. Está diseñada para desarrolladores que necesitan definir esquemas con z.object, aplicar validaciones con z.string, utilizar safeParse para análisis seguros, o inferir tipos con z.infer. No cubre la integración con React Hook Form (consulta la habilidad 'react-hook-form') ni la generación de clientes OpenAPI (consulta la habilidad 'orval').

Compatible con~Claude Code~Codex CLI~Cursor
Part ofReact
npx skills add https://github.com/pproenca/dot-skills/tree/main/skills/zod

Installed? Explore more Programación y desarrollo skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace zod?

Mejores prácticas de validación de esquemas Zod para seguridad de tipos, análisis y manejo de errores. Esta habilidad debe usarse al definir esquemas con z.object, al aplicar validaciones con z.string, al utilizar safeParse o z.infer. Esta habilidad NO cubre patrones de integración con React Hook Form (usa la habilidad 'react-hook-form') ni la generación de clientes OpenAPI (usa la habilidad 'orval').

Individual skills in this repo

This repo contains 7 individual skills — each has its own dedicated page.

pproenca/clean-architecture

Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.

pproenca/code-simplifier

Code simplification skill for improving clarity, consistency, and maintainability while preserving exact behavior. Use when simplifying code, reducing complexity, cleaning up recent changes, applying refactoring patterns, or improving readability. Triggers on tasks involving code cleanup, simplification, refactoring, or readability improvements.

pproenca/emilkowal-animations

Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.

pproenca/nuqs

nuqs (type-safe URL query state) best practices for Next.js and other React frameworks. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, limitUrlUpdates, Standard Schema, NuqsAdapter, or Next.js routing with state.

pproenca/react-hook-form

React Hook Form performance optimization for client-side form validation using useForm, useWatch, useController, useFieldArray, and the v7.55+ subscribe() API. This skill should be used when building client-side controlled forms with React Hook Form library. This skill does NOT cover React 19 Server Actions, useActionState, or server-side form handling (use react-19 skill for those).

pproenca/typescript

TypeScript performance, tsconfig, type errors, async patterns — triggered when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.

pproenca/vitest

Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.

Skills relacionados