cspell

Prioritized strategy for handling cspell unknown word warnings. Classify each flagged word, pick the narrowest fix, and optionally bootstrap cspell config for projects that don't have it yet.

Core Principles

1. Config Check First — Verify repo has cspell config before any action; offer bootstrap if missing
2. Adjust Text Before Adding to Dictionary — Restructure words (hyphenate, camelCase) when safe
3. Narrowest Scope Wins — Inline directive for one-off words; project dictionary for recurring terms

Documentation: Fetch cspell syntax and config details via Context7 (/streetsidesoftware/cspell) at runtime; never rely on hardcoded syntax.

Workflow

1. Check for cspell config — Search from the file's directory upward for cspell config files: package.json (cspell field), .cspell.json, cspell.json, cspell.config.{json,mjs,js,cjs,yaml,yml,toml}, cspell.{yaml,yml}, and their ./.config/ prefixed variants (e.g., .cspell.config.yaml, .config/cspell.json). Also check .vscode/cspell.json. If none found: notify user, do NOT auto-fix, offer to bootstrap (see below). Note: cspell.* settings in .vscode/settings.json are IDE-local and do not count as project config.
2. Apply fix priority — Stop at the first applicable level (see table below).
3. Select directive — When using inline directives, consult decision-tree.md for the selection guide.

Fix Priority