Engineering reference
I Treat My LLM Like a Genie (And It Fixed My Prompt Problems)
A first-person essay using a genie metaphor to discuss explicit constraints, output formats, and prompt transformation.
Methods, definitions, and examples for the topic discussed here. Check applicability against the task and operating conditions.
There is an old thought experiment about genie wishes. You make a wish. The genie grants it exactly. "I wish for a million dollars" and it lands on your doorstep, triggering an IRS investigation. "I wish for world peace" and humanity is instantly gone, which is technically peaceful. The genie gives you what you asked for. Not what you meant.
Language models work the same way. They are very literal. They give you exactly what your prompt asked for. Your prompt is written in plain language. Plain language has hidden ambiguity. The model picks one meaning, often not the one you intended.
Once I understood this, my prompts got better right away.
The Genie's Literal Mind
When I ask Claude "make the login faster", what does that mean? Faster how? Cache the session? Optimize the DB query? Remove validation steps? Return a 200 before the async work finishes? All of these make login "faster". The genie picks one.
An underspecified request can have several plausible interpretations. State the intended interpretation and track when clarification is needed instead of assigning a fixed failure rate.
The fix is to make wishes that can only be read one way. Not by being wordy. Be specific about the things that matter.
The second version is longer for a good reason. I named the metric (P95), the method (query optimization), and three hard limits (no validation changes, no schema changes, no cache). The genie now has almost no room to go wrong.
CONSTRAINTS Are Your Wish Safeguards
In genie stories, the hero learns to add safeguards. "I wish for a million dollars, obtained legally, without harm to anyone, without triggering any legal investigation, deposited in my existing bank account." Each safeguard closes one hole the genie could use against you.
In the sinc-LLM format, CONSTRAINTS states the rules and exclusions. The genie analogy illustrates why the intended limits should be explicit.
Every constraint closes one way the model can go wrong. "No schema changes" blocks the migration path. "Tests must pass" blocks the refactor-everything path. "Response under 50 lines" blocks the long-explanation path. More constraints means fewer valid answers. Fewer valid answers means the model is more likely to pick the one you want.
FORMAT Is Your Output Shape
Another classic genie failure: you wish for gold and get a gold statue of yourself. You got gold. Just not the shape you wanted. FORMAT is how you tell the model what shape the output should take.
"Code diff" means a before/after diff, not an explanation of what to change. "Bullet list" means bullets, not flowing prose. "JSON schema" means a schema, not an example of JSON that matches it. If you do not specify FORMAT, the genie picks one. It usually picks prose. It is usually too long. It is usually not what you needed for your next step.
FORMAT states the required output structure. Check it alongside the rules in CONSTRAINTS.
How the Auto-Scatter Hook Makes Wishing Easier
Writing perfect genie wishes every time is hard. In practice, when I am in the zone, I type "fix the login bug" and hit enter. I am not thinking about CONSTRAINTS and FORMAT. I am thinking about the problem.
The auto-scatter hook takes my rough wish and adds safeguards for me. It guesses the most likely constraints from context. It fills in the most likely format for the type of task. It adds persona and context from the project environment. Think of it as an interpreter who cleans up your wishes before the genie hears them.
The hook structures prompts before execution. It is open source; leave a comment for the link. Check output behavior and operating costs for your workflow.
// Production AI Engineering
Build AI systems that hold up in production.
sinc-LLM designs, audits, and stabilises production AI infrastructure: from vendor evaluation and cost accountability to incident controls and MCP architecture.
See what we do →Scope and context
sinc-LLM About Blog Services
DOI: 10.5281/zenodo.19152668 · © 2026 sinc-LLM · Mario Alexandre
sinc-LLM

