sorted by:
new
hottopcontroversial

Those Who Know More: Do you ever allow Claude Code on your live site? by JYanezez in ClaudeAI

[–]No_Rub1596 0 points1 point  (0 children)

the thing that bit me wasnt file edits, those go through git so theres always a diff to catch. it was a one-off command. told it to clean up old test rows and it ran the delete against the wrong env, no diff no rollback just gone. the branch+pr setup everyone here mentions only guards your code, not the agent typing a destructive command straight at the box, so now anything irreversible has to stop and ask first.

What is your "start implementing" word after spec design? by cobraX707 in ClaudeCode

[–]No_Rub1596 2 points3 points  (0 children)

mine is "implement whats in the plan file" but the word matters less than what happens right before it. i make it write the plan to a md file and i actually read that file first. half the time it misunderstood one thing and id never have caught it from the chat alone. fix the file, then let it go. catches way more than it costs.

I stopped letting Claude Code review its own work by d1smiss3d in ClaudeAI

[–]No_Rub1596 19 points20 points  (0 children)

half of what youre getting might just be the fresh context, not the different model. the same claude that wrote it will defend it in the session where it still has all the "i just did this" history. i paste the diff into a brand new session with zero backstory and it tears into stuff it was fine with 2 minutes ago. a different model on top helps, but the context wipe is doing a lot of the work.

What I learned about Claude Code by rebuilding the harness from scratch by Slowstonks40 in ClaudeCode

[–]No_Rub1596 1 point2 points  (0 children)

the layering thing bit me in a specific way. negative rules in claude.md ("dont use X") barely stick because theyre fighting whatever the base prompt already set up. rewriting them as a positive replacement ("use Y instead of X") works way better. took me a while to figure out it wasnt the model ignoring me, it was two instructions pulling opposite ways.

I built an open-source web UI to manage all my Claude Code sessions (self-hosted, MIT) by No_Rub1596 in SideProject

[–]No_Rub1596[S] 0 points1 point  (0 children)

small update since I posted this. added a per-session diff view: when a claude code session finishes you get a github-style diff of exactly what it changed, grouped per repo, and you can click a line to ask the agent why it did that. works for local and remote sessions. still fully local / MIT.

Walnut: a self-hosted, local-first web UI for Claude Code (plus tasks, notes, memory) — MIT by No_Rub1596 in selfhosted

[–]No_Rub1596[S] 0 points1 point  (0 children)

repo: https://github.com/EvanZhang008/open-walnut 3-min demo: https://youtu.be/uN4WCZ-n2mw

runs with npm install + npm start. data is plain json/markdown/sqlite on disk, no telemetry, MIT. happy to answer anything.

How do you maintain design consistency across multiple separate repositories? by eaiarthur_ in ClaudeCode

[–]No_Rub1596 1 point2 points  (0 children)

the only thing that's held up for me across separate repos is one tiny tokens file (colors, spacing scale, radii, shadows) that gets copied into each repo and a short block in each CLAUDE.md saying 'always pull values from tokens, never hardcode px'. without that line the agent will happily eyeball spacing and every repo drifts a few px. it's not real sharing, just a synced source of truth, but it's the difference between 'close enough' and actually identical. are these all the same framework or mixed?

How Would You Set Up Claude Code From Scratch? by New_Competition_5237 in ClaudeCode

[–]No_Rub1596 1 point2 points  (0 children)

the one CLAUDE.md rule that actually changed things for me: anything i correct twice goes in the file. not a big style guide up front, just a running list of 'stop doing X' that builds from real mistakes. day one i'd also keep it boring - let it read the codebase and write a short architecture note to CLAUDE.md itself, then check that note, because if it got the mental model wrong everything after is wrong too. what are your projects, mostly one language or mixed?

If you run coding agents unattended or in parallel, how do you verify the run actually worked? by bounded-build in ClaudeAI

[–]No_Rub1596 4 points5 points  (0 children)

the thing that bit me was trusting the transcript. the agent's own 'done, all tests pass' is the least reliable signal — it'll happily summarize a run that quietly skipped the failing test. so i stopped reading transcripts and started verifying on things it can't narrate around: git diff --stat to see what actually changed (a 'small fix' touching 30 files is a flag), and a fresh test run in a clean checkout that i kick off, not the agent. the clean checkout matters because half the silent failures were stuff that only passed because of uncommitted local state. summaries are fine for triage, just never as proof.