I realised recently that I was approving code I couldn’t have written myself. Whenever something didn’t quite make sense, I’d tell myself I’d figure it out later. But with an agent ready to build the next thing, later never came. I recognised the same pattern from needing to block apps that scattered my attention. Knowing they were distracting me wasn’t enough. The impulse to keep going was too strong, so I needed something that added friction rather than relying on willpower. So I built learning-guardrails , an opt-in skill for Claude Code, with an optional mod. Run /learning-guardrails and it adds a bit of friction to your workflow: Every change gets triaged When something needs a closer look, it asks a question about the actual code. Predict what happens or explain a trade-off. Get it wrong and it breaks the question down rather than giving you the answer. It tracks what you’ve already demonstrated you understand, so it doesn’t keep reteaching the basics. The optional mod blocks file edits while a question is open, keeps the question visible above the prompt, and stops Claude loading the skill unless you’ve explicitly asked for it. The idea isn’t to slow down AI coding for the sake of it. It’s to make understanding part of the process, rather than something I keep promising myself I’ll get around to later. It’s early days, so I’d genuinely love feedback, especially on whether the friction feels useful or just annoying. https://github.com/2Steaks/skills submitted by /u/BoredHedgehog
Originally posted by u/BoredHedgehog on r/ClaudeCode