devlisted

# Development Implement: $ARGUMENTS ## Before anything Read `.claude/project-profile.md`. It holds the stack, layout, conventions, and the list of files that must never be hand-edited. **If it does not exist, stop and say so:** "No project profile found. Run `/project-setup` first, or tell me the stack and I will work from that for this one task." Do not infer a stack from a couple of file extensions and start writing: guessed conventions produce code that looks plausible, passes review, and is wrong for this codebase. ## The loop ### 1. Read before writing Find the closest existing thing to what you are about to build and read it. Not one file: the pattern. If you are adding a hook, read three hooks. If you are adding a route, read how routes are registered and how the neighbouring ones handle loading and errors. The goal is that your diff is indistinguishable from code the team wrote. Matching the surrounding style is not cosmetic, it is what makes the change reviewable. ### 2. Plan, proportionally For a one-line fix, skip this. For anything touching three or more files, or any schema change, write the checklist first: files, data changes, migrations, tests. If the plan turns out to be wrong halfway through, stop and re-plan rather than pushing through with an approach you have already stopped believing in. ### 3. Implement - Minimum code that satisfies the requirement. No speculative abstraction, no options nobody asked for. - Follow the profile's conventions