coding-best-practices

Organize by feature under src/features/, keep shared UI in src/components/ with no domain imports, and compose screens in src/app/. Place unit and component tests in sibling __tests__/ folders using Vitest, and e2e tests in a root e2e/ folder with Playwright.

Use an exclusive arc: one nullable foreign key per parent with ON DELETE CASCADE, plus a CHECK constraint using num_nonnulls to enforce exactly one owner. Add partial indexes WHERE the FK IS NOT NULL for list-by-parent queries, and avoid owner_type/owner_id polymorphic columns.

Use Vitest for unit and component tests with jsdom and React Testing Library, placing files in sibling __tests__/ folders. Use Playwright in a root e2e/ directory for user-visible journeys, and do not add a second test framework if one already exists.

Yes. If a stack file is missing, the workflow requires researching current practice from official docs first, adding a new stack file with sources, folder tree, dependency direction, and testing guidance, then writing code against that file.

When files go to object storage, memoryStorage avoids writing temp files to disk before the put call. Always cap fileSize and files limits since the default fileSize is unlimited, and handle MulterError LIMIT_FILE_SIZE with a 413 response.

Do not create empty folders for later or copy enterprise starter directories. Create src/hooks/ only when a generic shared hook exists, and add shared modules only when roughly three consumers need them.