Use this skill when the user wants to verify CLAUDE.md is still accurate, or after significant code changes that may have invalidated documented claims. Triggers include "audit CLAUDE.md", "is CLAUDE.md still correct", "check docs drift", "verify claude.md", or after dep bumps / refactors. Diffs every concrete claim in CLAUDE.md against current code reality and reports stale/missing entries.
Use this skill when the user wants to scaffold a new React component in this project. Triggers include "add a component", "create a new React component", "scaffold a feature page". Follows the project's folder-per-feature, CSS-Modules-with-SCSS, relative-path import conventions used by `Counter` and `Titlebar`. Components are TypeScript (`.tsx`); the project completed its TS migration.
Use this skill when the user wants to run the app in dev mode, hits "white screen / loading screen never goes away", or asks how the React + Electron + Flask processes start together. Triggers include "yarn start", "dev server stuck", "Flask not responding", "port already in use", "loader hangs". Walks through the dev-mode handoff and the most common failures.
Use this skill when the user wants to wipe build artifacts and rebuild from scratch, or when stale `build/`, `dist/`, `resources/`, `node_modules/`, or PyInstaller `__pycache__` is causing weird failures. Triggers include "clean the project", "fresh build", "yarn clean", "stale artifacts", "PyInstaller cache problem". Explains exactly what `yarn clean` and `yarn clean:all` remove and what they do NOT.
Use this skill when the user wants to add a new Python/Flask endpoint and call it from the React frontend. Triggers include "add a Python endpoint", "expose a Flask route to React", "wire a new backend service", "add /something route". Covers the full round-trip — Flask side, renderer side, and the rebuild step that production needs.