Cline rules

1---
2description: Testing, linting, formatting, and safe change workflow for account-switcher
3globs: ["src/**/*.ts", "src/**/*.tsx", "package.json", "eslint.config.*", ".eslintrc*", ".prettierrc*"]
4alwaysApply: false
5---
6 
7Quality rules:
8- Apply formatting and linting through the repository's existing scripts.
9- Do not introduce a new formatter, linter, or test approach unless explicitly asked.
10- Keep fixes scoped to the user request; avoid mixing feature work with broad refactors.
11 
12Safe change workflow:
13- For bug fixes, describe the failing scenario and the smallest viable fix.
14- For behavior changes, state what remains backward compatible and what changes.
15- If no automated test exists, still reason through affected flows before suggesting a final change.
16- When relevant, call out follow-up checks for popup behavior, background messaging, storage handling, and manifest impact.