zod

• Organize Zod schemas logically for readability and maintainability. Group related schemas together and structure your Zod code for improved clarity, especially in larger projects.
• Compose and reuse related schemas to avoid repetition. Use Zod's composition features (e.g., z.intersection, z.union, z.extend) to create reusable schema components and reduce redundancy.
• Implement schema versioning for better management. As your application evolves, version your schemas to handle data migrations and maintain compatibility with older data formats.
• Use Zod for type-safe data validation and transformation. Leverage Zod's capabilities for both validating and transforming data to ensure data integrity throughout your application.

Project Tech Stack:

ALWAYS USE THE FOLLOWING IN CONJUNCTION WITH EACHOTHER TO HAVE A SAFE CODEBASE WHERE WE CAN MOVE FAST AND BREAK NOTHING

• Next.js
• Typescript + ESlint
• Zod + Prisma + tRPC + React Query
• Prisma (supabase) + Redis
• ShadCN + TailwindCSS v4
• Vitest Unit Tests

1. Code Organization and Structure:

• Directory Structure Best Practices:
  • Consider grouping Zod schemas within dedicated directories (e.g., schemas/, models/schemas/).
  • Organize schemas by domain, feature, or data model.
  • Use subdirectories for complex schemas or schema families.
• File Naming Conventions:

• Consistent Case: Maintain a consistent casing convention (e.g., camelCase for variables, PascalCase for components). Use kebab-case for file names e.g. user-profile.tsx or user.router.ts
  • Name schema files descriptively (e.g., user.schema.ts, product.schema.ts).
  • Use a consistent naming pattern throughout the project.
  • Consider including the data model name or the schema's purpose in the filename.

• Module Organization:
  • Export schemas as named exports from each module.
  • Create index files (e.g., index.ts) to re-export schemas from subdirectories for easier access.
  • Use clear and concise module names.
• Component Architecture:
  • If you are building React components, consider creating a components/schemas/ directory where you house your schema related to specific components.
  • Use Zod to validate the props passed to React components using z.infer and z.ZodType<Props>
  • You can create a custom hook that handles validation with Zod and stores the parsed result in React state.
• Code Splitting Strategies:
  • For large schema definitions, split them into smaller, more manageable files.
  • Use Zod's composition features to combine these smaller schemas into larger, more complex schemas as needed.