Skip to main content

3 posts tagged with "prompt engineering"

View All Tags

Matt Pocock vs. Addy Osmani: Two Approaches to Better AI Coding with Agent Skills

· 6 min read
Stephan Janssen
Creator of DevoxxGenie

The frustrating thing about AI coding agents is not always that they cannot write code. It is that they can write plenty of code before discovering what you actually wanted.

They assume requirements, introduce unnecessary abstractions, and sometimes treat a successful build as proof that the problem is solved.

Agent skills offer one way to address this: package engineering practices into reusable instructions that an agent can follow. Two collections worth examining are:

Both aim to make AI-assisted development more disciplined, but they put different emphasis on how to get there.

Tell the Agent How to Work: Editable Tool Descriptions

· 5 min read
Stephan Janssen
Creator of DevoxxGenie

An agent decides which tool to call almost entirely from one thing: the tool's description. Not its name, not its parameters — the sentence or two that says "Read the contents of a file in the project" is what the model weighs when it picks read_file over run_command.

Until now those descriptions were string literals compiled into the plugin. You could switch a tool off, but you couldn't tell the model anything about the tools that remained. So "use ./gradlew, never a global gradle" or "prefer semantic search over grep in this repo" meant repeating yourself in every prompt, or editing the plugin.

You can now rewrite any built-in tool's description from Settings.

Personas: Switch the System Prompt Without Rewriting It

· 5 min read
Stephan Janssen
Creator of DevoxxGenie

The system prompt is the most powerful setting in DevoxxGenie and the one nobody touches twice. You write a good one, it works, and then it quietly becomes wrong for half of what you do. The prompt that makes a model a great pair programmer — write the code, be concrete, show me the diff — is exactly the prompt that makes it a mediocre reviewer, because a reviewer that starts rewriting your method has stopped reviewing it.

The usual workaround is to argue with the model in the prompt itself: "don't implement anything, just review". It works about as often as it doesn't.

Personas, new in DevoxxGenie 1.12.0, fix this the boring way: give each role its own system prompt, name it, and put the names in a dropdown.