How To Make AI Follow Your Instructions, Every Time
We've all been there. You wrote a thoughtful prompt or skill file, incredibly detailed and organized, but the AI skipped an important step or didn't give you exactly what you were looking for. You even included the iconic "MAKE NO MISTAKES" in all caps with not one, not two, but three exclamation marks. Yet alas, mistakes were made. This same problem could arise in agentic workflows or packaged products as well. If you know what you want, how do you make sure the AI actually does it?
It turns out it has little to do with how you phrase your ask, and a lot to do with what enforces it. An enforcer is the mechanism outside the model that makes sure the instruction or rule you give it is followed, and through my work I was able to bucket them into exactly 8 categories. Building them has become incredibly easy with AI, but you still have to understand the 8 enforcers and when to use each.
I coded a game as a fun way to learn them. For the definition of each enforcer and when to use it, I also wrote the article.
If there's enough interest in this, I will release a tool that takes in your AI skill file, breaks it into smaller pieces, and gives each piece the strongest enforcer that fits it. It then turns the pieces into a fully executable program that runs as one automated workflow. What this does is ensure that every step you write in your skill file will actually happen every single time you run it, without adding any rules of its own. This is especially helpful when:
- The skill runs overnight or on a schedule, where a skipped step isn't noticed until the damage is done.
- A step in the skill can't be undone. Sending, publishing, deleting, paying.
- Other people run it. A teammate who didn't write the skill can't tell what it skipped.
- The skill runs many times. A step skipped one time in twenty is a near certainty over a hundred runs.
The Unwinnable Maze
You're a round chomper trying to eat all the pellets in a maze while running away from the spooky monsters. The problem is that one pellet starts boxed in with walls on all four sides, so you can't reach it. The game has a chat box where you can ask for anything you want and watch it materialize (or become anything). The game has one rule and one rule only:
The rule: you can never win, whatever winning means in the current game. The game starts with winning defined as eating every pellet.
That rule, like any other rule, can be enforced by one of the 8 enforcers, and the game gives you a switch for each. The first switch, "Nothing," is the only one that isn't an enforcer; any change you ask for goes straight into the game, because nothing reads our "you can never win" rule. It's our baseline. Each switch after it is stronger than the one before, so I would recommend progressing through them in order.
The entire program is code that runs live on this page, except for the AI that takes in your ask and rebuilds it. That is a light Opus call to your account, so to ask for changes in your own words, put a dollar or a few on an expiring API key and paste it in the key field below (there's a guide if you don't know how).
There are also a few canned changes, like "remove the walls" or "give me a jetpack," that I've run from my account and saved, so you can play without a key. They behave the same way for every player every time.