Where are the human prompts

src/routes/posts/where_are_the_promptss_to_stop_humans_going_of_the_rails.mdx

@@ -0,0 +1,35 @@
+---
+meta:
+  title: Where are the prompts to stop humans going off the rails? 
+  description: Humans are just as finicky as AI
+  dateCreated: 2026-07-03
+
+tags: 
+  - "ai"
+
+---
+
+import { TextHighlight } from "@blacksheepcode/react-text-highlight";
+
+
+The place I work at has a miserly AI budget, and so last month I had been very disciplined in using my AI judiciously, and making use of just the Haiku model. 
+
+Come to the end of the month, I still had more than half my budget, so I spent two hours with Opus, doing a test driven development approach to creating some custom linting rules. 
+
+It worked really well. I copy pasted a design principles document in, and it one by one came up with example code that should fail and what the lint error should be. Tight human in the loop stuff. 
+
+Then, I asked it to implement the lint rules, and it goes off and does. Brilliant, great job. 
+
+Fast forward to yesterday, I think 'well Opus did a great job the other day, I've got a new task for you'. But this time I didn't do the TDD, I gave it more vague prompts and it created _something_ that mostly worked, but I wasn't nearly as confident in it. And then I looked at my token usage to see that I'd already used half my budget in two days. 
+
+When we're using AI it seems that if we're not careful it starts becoming very hacky, hard coding things, copy pasting things, adding `@ts-ignores` etc, so we update our system prompts to keep it on track - "Don't do X", "if you encounter this situation, do Y" etc. 
+
+But humans can be just as temperamental, if not more. Sometimes we're under pressure, or we're just tired, and can think <TextHighlight comment={<><p>To be clear, jumping straight to implementation is often warranted, IMO. </p><p>Particularly if you're not sure if a thing is going to work, you want a quick session to prove the concept generally, but once you start refining the details, you're going to have a much better time driving things with clear tests.</p></>}>'TDD will take too long, let me just get this thing working first'</TextHighlight>
+
+Maybe we can include in our system prompts not only guard rails to stop the AI going off track, but also instructions _to guide the human_. For example if the AI receives a prompt 'we need a CLI tool to do X' instructions to have the AI come back with 'OK, are you sure you want me to just go off and do this? In the past we've established that creating a decision tree and doing TDD is most effective'. Or - 'I see that you just `git commit -am "fix" --no-verify` more than 100 files, do you think maybe we should take a break?'
+
+Maybe I shouldn't design chatbots, because both of those sound super annoying, but that's the idea.
+
+There are equivalent tools in other industries - vigilance control devices on trains come to mind - the device will make an annoying sound and the driver must press a button to prove they are still awake, otherwise the train comes to a stop. 
+
+