Agent Guidelines for Documenso

Build/Test/Lint Commands

Use TypeScript for all code; prefer type over interface
Use functional components with const Component = () => {}
Never use classes; prefer functional/declarative patterns
Use descriptive variable names with auxiliary verbs (isLoading, hasError)
Directory names: lowercase with dashes (auth-wizard)
Use named exports for components
Never use 'use client' directive
Never use 1-line if statements
Structure files: exported component, subcomponents, helpers, static content, types

Use custom AppError class when throwing errors
When catching errors on the frontend use const error = AppError.parse(error) to get the error code
Use early returns and guard clauses
Use Zod for form validation and react-hook-form for forms
Use error boundaries for unexpected errors

Use Shadcn UI, Radix, and Tailwind CSS with mobile-first approach
Use <Form> <FormItem> elements with fieldset having :disabled attribute when loading
Use Lucide icons with longhand names (HomeIcon vs Home)

Each route in own file: routers/teams/create-team.ts
Associated types file: routers/teams/create-team.types.ts
Request/response schemas: Z[RouteName]RequestSchema, Z[RouteName]ResponseSchema
Only use GET and POST methods in OpenAPI meta
Deconstruct input argument on its own line
Prefer route names such as get/getMany/find/create/update/delete
"create" routes request schema should have the ID and data in the top level
"update" routes request schema should have the ID in the top level and the data in a nested "data" object

Use <Trans>string</Trans> for JSX translations from @lingui/react/macro
Use t\string`` macro for TypeScript translations
Use (params: Route.Params) and (loaderData: Route.LoaderData) for routes
Directly return data from loaders, don't use json()
Use superLoaderJson when sending complex data through loaders such as dates or prisma decimals