Knowledge
An agent that does what you want, every time
Consistent work from an agent does not come from a better prompt, but from fixed rules, a check and a learning loop.

An agent that does good work one day and not the next is not usable. You build consistency in, with rules, checks and a way to learn from mistakes.
Plain technical English An agent follows the rules in its context. A rule that must hold becomes an automatic check. Each mistake becomes a new rule or a new check.
Why it matters
A language model does not give the same answer every time. For a text, that is sometimes fine. For a quote, an invoice or a deploy, it is not. If you must check every step yourself, the agent saves you no time.

How it works
The agent works until the check is green; a fresh reviewer looks; every mistake becomes a rule.
The Claude Code guide gives the same building blocks: a short instruction file, procedures in skills, a check that Claude runs itself, and hooks for rules without exceptions. A hook is a piece of code that runs automatically, for example before each commit.

What you do
- Say when it is done. A test that must pass, or a screen that must look right.
- Write few rules, and keep them short. Long instructions are followed less well.
- Put ways of working in skills. We use, among others,
test-driven-development,systematic-debuggingandverification-before-completionfrom obra/superpowers (MIT). - Make hard rules automatic. At Denkbaar, a check blocks every commit that is too large.
- Let someone else check. A fresh agent that did not see the build sees more.
- Learn from every mistake. One line in a lessons file. If it happens a second time, it becomes a fixed rule or check.
What we can do with you: we set up an agent that does the same good work for your task every time, with the checks included. Book a conversation.