ticket-work
Ticket work
In a fresh clone or worktree, run pnpm install before anything else. It installs the toolchain and runs lefthook install, which writes the git hooks. src/routeTree.gen.ts is committed, so pnpm check works without a dev server, and pnpm dev rewrites it whenever a file under src/routes/ changes.
The steps are sequential. Do not skip one because the change looks small: a change that looks small is the one that skips step 2 and lands in the wrong layer.
1. Clarify
Settle what would change the work before writing any of it: which behavior the user wants, which existing module owns it, and what the acceptance is. Where the user is present and one question blocks the most work, ask that one with AskUserQuestion and hold the rest. Where they are not, write the assumption into the pull request body.
A premise you cannot check is a question, not a fact. Open the file, run the command, or say you could not.
2. Locate
Read the slice the change belongs to before adding to it. AGENTS.md settles which directory owns a module and which way its imports run; .claude/rules/data-fetching.md settles a read or a write; .claude/rules/react.md settles where a module and a non-component value live.
A change that adds a directory, a dependency, or a boundary is a decision to state in the report, not a detail.