When adding or modifying UI elements, ensure their test/automation identifiers follow the existing naming conventions and remain stable. Apply these rules: - Prefer component-supported prefixing (e.g., `testIdPrefix`) so generated IDs stay consistent across related CTAs. - If you must set `data-testid` directly, follow the local established pattern for that area (for example, `client-settings--` where `` reflects the control type like `switch` / `input`). - Keep identifiers predictable: use a scope/feature prefix, then the setting/feature name, then the UI element type. Example patterns: ```tsx // Prefer prefix props when the component generates IDs // Follow the local convention when setting explicitly ``` This keeps automated tests resilient and avoids one-off/unstable identifiers that break CI and slow down debugging.