Roo-Code/.roo/rules/rules.md
Chris Estreich 62c3914034
Farewell jest (#4607)
Co-authored-by: ellipsis-dev[bot] <65095814+ellipsis-dev[bot]@users.noreply.github.com>
2025-06-16 21:39:45 -07:00

992 B

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 describe, test, it, etc functions are defined by default in tsconfig.json and therefore don't need to be imported
    • Tests must be run from the same directory as the package.json file that specifies vitest in devDependencies
  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: <div className="text-md text-vscode-descriptionForeground mb-2" /> instead of style objects

Adding a New Setting

To add a new setting that persists its state, follow the steps in docs/settings.md