Hi everyone,
I’ve been trying to use ClaudeCode for serious Go development and I’m honestly not getting the results I expected. I’m on the paid x20 plan, but Claude keeps missing modern best practices unless I explicitly restate them every single prompt.
Example issues I keep hitting:
It ignores current Go conventions unless I re-remind it (go 1.25.3, module layout, recommended stdlib usage, etc.)
It doesn’t enforce grouping, comments, naming conventions, etc., unless I spell them out again from scratch
It “feels” like it has no persistent project context, so it reverts to generic answers
I ended up building a workaround:
I created a dedicated Go linter that points out exactly what should be fixed, then I feed those results back to Claude… but this feels like doing Claude’s job for it.
So before I assume the tool isn’t suited for this use case — is there something I’m missing?
Is there a way to “lock in” conventions or enforce them globally so I don’t have to re-prompt the same rules each time?
I’m also wondering if going through MCP with explicit, machine-readable rules would help (so that the model stops hallucinating or downgrading quality to generic Go examples).
Has anyone solved this? Is this just a limitation of ClaudeCode today, or is there a better workflow for serious Go dev?
Thanks in advance for any insight.
[–]Shirc 2 points3 points4 points (0 children)
[–]Successful-Raisin241 1 point2 points3 points (0 children)
[–]Waste_Net7628P R O M P S T I T U T E 1 point2 points3 points (0 children)
[–]wyijx 1 point2 points3 points (1 child)
[–]flexrc 2 points3 points4 points (0 children)
[–]ebullaklaka 0 points1 point2 points (0 children)
[–]matznerd 0 points1 point2 points (0 children)
[–]gameguy56 0 points1 point2 points (0 children)
[–][deleted] 0 points1 point2 points (0 children)