From 2581fcc8bf97c2607e8532e603e19aaa47b21a0a Mon Sep 17 00:00:00 2001 From: Matt Rubens Date: Mon, 25 Aug 2025 17:13:20 -0400 Subject: [PATCH] Remove existing .roo/rules/rules.md --- .roo/rules/rules.md | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 .roo/rules/rules.md diff --git a/.roo/rules/rules.md b/.roo/rules/rules.md deleted file mode 100644 index 5726770a28..0000000000 --- a/.roo/rules/rules.md +++ /dev/null @@ -1,24 +0,0 @@ -# Code Quality Rules - -1. Test Coverage: - - - Before attempting completion, always make sure that any code changes have test coverage - - Ensure all tests pass before submitting changes - - The vitest framework is used for testing; the `vi`, `describe`, `test`, `it`, etc functions are defined by default in `tsconfig.json` and therefore don't need to be imported from `vitest` - - Tests must be run from the same directory as the `package.json` file that specifies `vitest` in `devDependencies` - - Run tests with: `npx vitest run ` - - Do NOT run tests from project root - this causes "vitest: command not found" error - - Tests must be run from inside the correct workspace: - - Backend tests: `cd src && npx vitest run path/to/test-file` (don't include `src/` in path) - - UI tests: `cd webview-ui && npx vitest run src/path/to/test-file` - - Example: For `src/tests/user.test.ts`, run `cd src && npx vitest run tests/user.test.ts` NOT `npx vitest run src/tests/user.test.ts` - -2. Lint Rules: - - - Never disable any lint rules without explicit user approval - -3. Styling Guidelines: - - - Use Tailwind CSS classes instead of inline style objects for new markup - - VSCode CSS variables must be added to webview-ui/src/index.css before using them in Tailwind classes - - Example: `
` instead of style objects