Improved agent rules and instructions

Author: sergeyklay

.cursor/commands/implement.md

@@ -97,8 +97,8 @@ IF the task involves fixing a documented BUG:
 You are PROHIBITED from responding "Done" until you have verified runtime execution for Database Logic.
 
 1. **Static Analysis:**
-   - `npx tsc --noEmit` (MUST pass - no errors or warnings)
-   - `npm run lint` (MUST pass - no errors or warnings)
+   - `npx tsc --noEmit 2>&1` (MUST pass - no errors or warnings)
+   - `npm run lint 2>&1` (MUST pass - no errors or warnings)
 
 2. **Runtime Validation (For DB/Logic):**
    - IF you modified database logic (actions/services):

.cursor/commands/test.md

@@ -78,7 +78,7 @@ Steps to verify:
 
 1. run `npm run test` to perform testing.
 2. If the tests fail, FIX the code and RETRY loops until success.
-3. run `npx tsc --noEmit` to check for type errors.
-4. run `npm run lint` to check for linting errors.
+3. run `npx tsc --noEmit 2>&1` to check for type errors.
+4. run `npm run lint 2>&1` to check for linting errors.
 5. If the tests AND linting AND type checks pass, respond "Done".
 6. NEVER respond "Done" until you have verified that the tests are complete and cover all the functionality of the source file and that there are no linting/type errors or warnings.

.cursor/rules/testing.mdc

@@ -11,6 +11,7 @@ When testing Server Actions, NEVER import the real `db` instance.
 - Use `jest.mock('@/db')` to mock the Drizzle client.
 - Mock return values of queries using `mockReturnValue` or `mockResolvedValue`.
 - Example for insert: `(db.insert as jest.Mock).mockReturnValue({ values: jest.fn().mockReturnValue({ returning: jest.fn().mockResolvedValue([mockData]) }) })`.
+- **Don't mock `@/db/schema`:** just mock `@/db`. Schema is side-effect-free and gives real Column objects needed by `drizzle-orm`.
 
 ## 2. React Testing Library
 - **Queries:** Prioritize `getByRole`, `getByLabelText`, `getByText` (Accessibility-first). Avoid `getByTestId` unless necessary.