Skip to content

Instantly share code, notes, and snippets.

@ScottKirvan
Created July 23, 2026 23:11
Show Gist options
  • Select an option

  • Save ScottKirvan/d9e60b30047a225f4d1ba8958a85c1ae to your computer and use it in GitHub Desktop.

Select an option

Save ScottKirvan/d9e60b30047a225f4d1ba8958a85c1ae to your computer and use it in GitHub Desktop.
Claude Code - stop it taking shortcuts and being lazy

Lesson learned:

When you specify a coding task for Claude, especially when it's implementing from a design spec rather than explicit code directives, watch out for it coming back and saying something like, "Just calling out that feature X was implemented as Y, this is not a bug" or "isn't part of v1," or "will be implemented as part of [some other task or adr]," -- this is a red flag that Claude may have taken some shortcut and the architecture is probably broken or incomplete at some level.

When it does so, just call it out and tell Claude that the implementation (or PR) won't be accepted until the implementation is truly complete - and don't be surprised if this leads to some rearchitecting of core systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment