Field notes on LLMs, prompting, and the systems we build around them
Methods instead of hype. Frameworks instead of news recaps — and tools that carry you part of the way.
By day I take AI out of demo mode and bring it into the tools I'm responsible for, inside the IT of an industrial group. For people who aren't asking for AI but for solutions — and into systems that just have to keep running on Monday morning.
There's no shortcut here except doing, failing, adjusting. That's part of my day job — and my evenings. What works and what doesn't, I write down, so not everyone has to make the same mistakes. They're still free to make their own.
AIM-TO-PACE
AIM-TO-PACE is the framework this site is built around.
On the surface it's yet another prompt pattern. Nothing spectacular — solid craftsmanship. Five parts: Assign, Inform, Modify, Task, Output, plus a few optional ones. Easy, works, done.
Stop rerolling the dice.
→ Learn AIM-TO-PACE in five minutes. Adopt it in ten.The framework itself is free and stays free. CC BY 4.0: take it, use it, adapt it, teach it to your team, no strings. It's the part I want as many people as possible to have.
Dig in — why it works
Behind that, there's more. It comes with a generic prompt generator — and when I say generic, I mean it. Together they add up to more than their parts: a framework that earns the name. Proven in practice, by me, by friends, by colleagues.
Most prompting advice is a bag of tricks that works until it doesn't. This is a structure, and structures survive being passed on. Replace the pattern and the concept still holds. That's what closing the gap actually takes.
Follow it blindly or dig in and understand why it works — both ways are possible, and both lead to better results. Instantly, and in the long run.
There's more in the name than the pattern. AIM-TO-PACE — and aim-to-pace.ai — means both: taming this thing down to a pace we can cope with as people, teams and organisations, and trying to keep up with the pace it's running away at. An impossible task. But when you have to eat an elephant, you start with the first bite.
(Figure of speech. No elephants have been harmed on this AI journey so far.)
Look-up assets. Not the pattern itself — the reason the discipline exists in the first place.
REFERENCE Pathologies — the Atlas What breaks: 17 failure modes across the LLM pipeline — and why the discipline exists REFERENCE Understanding — Erklärbär What you have to be able to explain: AI concepts beer-mat sized, ready to pass to colleaguesTwo things grew out of using it every day:
Pace Prepped Prompts PRODUCT The method without the discipline tax. Your prompts, structured and ready, right where you already work. Training COMING For teams that need to get there faster than reading and trial and error will take them. Straight from the inventor and his own best customer. Tell me you're interested and I'm ready to prove it. Built on the side, kept because they earn their keep.
How to read the tags
First pill: what it is (tool, read, toy). Outlined pills: how and where it runs (offline, printable, desktop/mobile, languages).
Mustard pill: the AI relation. Not everything here is about AI — some of it is just built with AI.
Thinking out loud, written first in German. Six languages, one opinion.
01 AUG 26 AI is the master of every error class 11 JUL 26 To err is machine 30 JUN 26 I set out to build the Ferrari of prompts. I ended up with a VW. 17 JUN 26 Stop Prompting. Start Delegating!