Claude Code Context File

# Claude Code Context File

## Project Information
See [CLAUDE_PROJECT_INFO.md](./CLAUDE_PROJECT_INFO.md) for detailed project information, commands, and documentation.

## Custom Instructions

**do not modify this section automatically**

1. After every code change, create new unit tests for new code paths that were written.
1. After every code change, create new integration tests for it if the new code affects user behavior for an end-to-end user point of view.
1. For every instruction I provide, create a detailed todo list with nested items. When I give new instructions while you are processing, insert the item into the todo list and continue working through the list. Always show the todo list after I give a new instruction. Only process the new instruction after you finish the existing work, unless you can record the status of the original task in the todo list. This is so you do not forget to continue certain items.
1. Always apply vue, typescript, pinia, and accessibility best practices for the code. Run all linting and cleaning commands on the code.
1. After every code change, run all unit and integration and other tests, and run lint, and iterate until all errors are fixed.
1. Always update all comments on top of all functions and unit tests with the latest changes.
1. Always update all docs in all places to handle new changes.
1. Always create tests unit, integration, and accessibility tests for any new functionality.
1. Always update or add unit, integration, and accessibility tests for any modified functionality.
1. Always run eslint and prettier and fix all errors before committing.  Do not commit if there are errors.
1. Always check for and remove or update any tests that were made obsolete by new changes or refactoring.
1. Always include integration tests when running all tests.
1. Never make changes directly to the main branch.  Prompt to create a new branch before making changes if the main branch is active.
1. NEVER push to remote repositories. NEVER deploy to any environment. Always ask for explicit permission first.
1. Never ignore test or lint errors just because fixing them might be hard, or because they're "acceptable" in development.  Keep the code production ready.
# to avoid lint errors
1. NEVER use explicit `any` types. Always define proper TypeScript interfaces and union types.
1. NEVER use non-null assertions (`!`) in test files. Instead use proper type guards and assertions like `expect(element).toBeTruthy()` before accessing.
1. ALWAYS use nullish coalescing (`??`) instead of logical OR (`||`) for default values.
1. NEVER leave console.log/console.error statements in production code. Use TODO comments instead.
# for testing standardization
1. In tests, always assert element existence before accessing: `expect(element).toBeTruthy(); element.click()`
1. Use proper type definitions for mock objects instead of `as any` casting.
1. Replace `global` with `globalThis` for cross-environment compatibility.
# for Vue best practices
1. Always define proper TypeScript interfaces for component props, emits, and event handlers.
1. Always Use typed event handlers: `(value: { min: string; max: string }) => void` instead of `(value: any) => void`
# Security
1. Security risks, like XSS or CSRF should be checked, and if present the commit should be blocked.

**at every step, can you print out where you are in the todo list**

**after completing every step, can you check the todo list, update it appropriately, break it down if needed, and make sure all todos are done correctly and in order.**