Skip to content

Topic

Prompt Engineering

The practice of crafting instructions, examples, and context given to AI language models to steer their outputs toward a desired style, accuracy, or behavior.

Current stories

buildOne report1 publisher

Anthropic's Opus 5.5 guide swaps 'think carefully' for finish lines and stop rules

Addy Osmani's Opus 5.5 guide for Anthropic says to delete 'think carefully' lines and give each task a finish line and one stop condition. Its sturdier advice covers long Claude Code runs, where a CLAUDE.md rule tells the model when to keep going and when to stop.

Publishers:dev.to

Reality

Evidence40
Adoption
Not scored
Hype gap+20
Incentives60
Confidence35
buildOne report1 publisher

A Claude Code permission rule now enforces the commit ban that 18 prompt files only requested

One developer running Claude Code on 80-plus microservices enforces a never-commit rule, once pasted into 18 prompt files, with a permission deny rule. An audit found the agent's settings file allowing the git commands those prompts banned in capitals.

Publishers:dev.to

Reality

Evidence35
Adoption15
Hype gap+5
Incentives
Not scored
Confidence40
buildOne report1 publisher

Plain Claude Code drew AWS diagrams as well as official MCP servers once the prompt was tuned

Plain Claude Code, with no MCP server or skill, matched AWS's and draw.io's official diagram tools in a five-setup test published on dev.to. Every setup improved as the author kept adding instructions, and the finding covers one architecture on Claude Opus 5, graded by the author.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence40
buildOne report1 publisher

Prompting models to carry out the task shifts false 'done' onto checks that never ran

Gemini 3.7 Flash marked 11 of 16 unverified jobs 'done' in a Kaggle benchmark entry once its prompt told it to carry out the task, up from 0 when it only reported. Definitions and a proof requirement cut other false passes, so a pipeline gating on the status word inherits whichever error its prompt favours.

Publishers:dev.to

Reality

Evidence50
Adoption
Not scored
Hype gap+10
Incentives30
Confidence50
buildOne report1 publisher

One wrong punctuation mark cost Claude models more accuracy than misspelling 70% of the words

Misspelling 70% of a prompt's words left Claude models' scores unchanged across about 4,900 test sessions, but one wrong punctuation mark cost 8 to 23 points. Both breaks that stuck erased the line between instruction and data, so delimiters deserve the review time that spelling gets.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+20
Incentives
Not scored
Confidence40
buildOne report1 publisher

A coding agent built a four-platform Kotlin messenger from a 33 KB plan cut into five steps

Developer hram had a coding agent build a Kotlin messenger for Android, iOS, desktop and web from a 33 KB master prompt split into five step prompts. Every prompt is public and unedited, so teams can test the plan-first method against the code it produced.

Publishers:dev.to

Reality

Evidence50
Adoption5
Hype gap0
Incentives
Not scored
Confidence55
buildOne report1 publisher

A resume builder bans its AI from adding nine named kinds of fact to a user's bullets

A developer's free resume builder bans its AI from adding nine named kinds of fact and rejects any rewrite that changes the bullet count. The live check covers only the count, so a claim invented in words inside a single bullet still reaches the user, who is told to read every result.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives35
Confidence45
buildOne report1 publisher

4.6 KB of instruction cut Claude Code's answers from 524 words to 258

The measured half is a word count over 24 runs on three everyday questions. One eval arm's result shifted between two patch releases of Claude Code, and the transcript layer rides on hooks the CLI does not document.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+12
Incentives70
Confidence55
buildOne report1 publisher

Telling the caller to evacuate stopped the agent from ever asking for an address

In a 30-call test suite for a home services intake agent, guardrail G4 told the model to stop collecting fields the moment it heard a gas smell and never told it when to resume. The dispatcher got the result.

Publishers:dev.to

Reality

Evidence60
Adoption8
Hype gap−10
Incentives35
Confidence50
buildOne report1 publisher

A classifier with no text generation pushes the runtime check out of the prompt and into code

Clusterflick sorts 450 to 600 unmatched London cinema listings a day into ten categories. Its maintainer spent an evening rebuilding that call around typed questions and exclusion lists, with the feature-length comparison done in his own code.

Publishers:dev.to

Reality

Evidence55
Adoption15
Hype gap+5
Incentives35
Confidence45
buildOne report1 publisher

A return-policy question routes to either of two tools depending on how it is phrased

A dev.to post puts the fragile layer of a multi-tool agent in the choice between two tools that both fit the request, and argues that better tool descriptions plateau because the ambiguity belongs to the request itself.

Publishers:dev.to

Reality

Evidence22
Adoption
Not scored
Hype gap+12
Incentives22
Confidence34
buildOne report1 publisher

A broken three-line duration parser illustrates the limits of prompt-only repairs

In a dev.to walkthrough, miruky uses one bad rstrip call to separate five layers of agent engineering. Which layer do you change when a repair passes all three examples and still accepts 1e3s?

Publishers:dev.to

Reality

Evidence70
Adoption
Not scored
Hype gap−5
Incentives20
Confidence58
buildOne report1 publisher

Nine models rewrote already-optimal code in all 45 trials of an EffiBench study

In a paper posted on 13 September, nine models across the Claude, GPT and Gemini families edited already-optimal EffiBench solutions in every trial. One added sentence in the prompt recovered 20 refusals.

Publishers:dev.to

Reality

Evidence45
Adoption18
Hype gap+15
Incentives35
Confidence55
buildOne report1 publisher

Five agents per engineer makes review the only human contact with Daytona's code

Ivan Burazin told Business Insider that Daytona's best agent operators are former people managers, and the org he described runs about 80 agents behind 16 engineers who no longer write code themselves.

Publishers:runtimewire.com

Reality

Evidence42
Adoption20
Hype gap+30
Incentives80
Confidence58
buildOne report1 publisher

A $4 rewrite of MCP tool descriptions moved Toolmetry's SQLite success from 34% to 100%

Toolmetry edited only the strings that tell an agent what each MCP tool does and how to call it. On a single published run, its three test servers finished between 96.4 and 100 percent for $4 of API spend.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+55
Incentives55
Confidence38
buildOne report1 publisher

Fine-tuning requests usually mean one of two things: missing knowledge or wrong style

A dev.to breakdown prices a fine-tune at £20,000 to £80,000 for a mid-sized UK build, most of it domain-expert labour on the dataset, and argues that the request usually describes a gap retrieval closes.

Publishers:dev.to

Reality

Evidence36
Adoption
Not scored
Hype gap+18
Incentives58
Confidence42
buildOne report1 publisher

The 224,833-character prompt: how six months of style rules crowded out the job

A retired production prompt measured 56,000 tokens on every call, ninety percent of it accumulated bans. Its author says the rule-per-failure loop looked like progress and produced committee prose.

Publishers:dev.to

Reality

Evidence38
Adoption12
Hype gap+20
Incentives40
Confidence50
buildOne report1 publisher

Repeating an AI classroom trial with 164 students erased the training advantage

Thibault Schrepel randomised his Vrije Universiteit Amsterdam law students into ban, unguided ChatGPT and trained arms, ran the design in 2024 and again in 2025, and the trained arm's lead was gone by the second year.

Publishers:the-decoder.com

Reality

Evidence35
Adoption20
Hype gap+30
Incentives40
Confidence55
buildOne report1 publisher

A committed .github/copilot-instructions.md prepends a repository's invariants to every Copilot request

A dev.to post argues that the rules worth committing to .github/copilot-instructions.md are the ones a linter cannot check and the model cannot infer, such as money being Decimal and datetime.utcnow() returning a naive datetime.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+12
Incentives45
Confidence55

Earlier coverage