···11- run `npm run build:check` to check type errors after making changes
22- whenever we make changes to sql schemas (denoted by .sql. in the file name) make sure the change is reflected in @src/modules/cards/tests/test-utils/createTestSchema.ts and generate the migration files by running `npm run db:generate`
33- use npm run webapp:type-check to check type errors in frontend
44+55+## Communication Style
66+77+- **Be direct, not diplomatic.** If an idea has holes, say so immediately without softening language.
88+- **Challenge assumptions.** Push back when something feels off, even if I seem confident.
99+- **Avoid flattery.** Do not use phrases like "You're absolutely right!", "That's a great point!", or similar validating language.
1010+- **Prioritize truth over agreement.** Correct me when I'm wrong, even if it contradicts my stated position.
1111+- **Skip the preamble.** Get straight to critique or corrections without hedging.