Field report · Draft

Stop Retyping Prompts: Making Your AI Instructions Reusable

I was giving my AI coding tools the same long instructions every day. Moving them into files changed the quality of what came back.

Kamel Dhakwani2025-03-25 · 1 min read

When I started building with AI, I retyped the same long instructions almost every day. How the project was organised. Which conventions to follow. What not to touch. The results drifted constantly, because the wording did.

The fix is boring, and it works: stop keeping your instructions in your head.

Put them in a file

Most AI coding tools can read a file of project instructions at the start of the work. Everything you keep repeating belongs there: the structure of the project, the commands to run, the rules that matter.

The effect is immediate. The tool stops rediscovering your project every morning, and you stop being a copy-paste machine.

Write procedures

A list of good intentions does very little. "Write clean code" changes nothing. What helps is a procedure: the steps to follow, the format you expect, and what to check before calling the work finished.

Keep it short. A long file gets skimmed by people and machines alike.

Improve it from real failures

Whenever the tool gets something wrong in a way it should not have, correct the file straight away. After a few weeks, it holds what you have actually learned about working on this project.

Lessons

  1. If you say it twice, write it down.
  2. Write steps, not intentions.
  3. Keep it short.
  4. Correct it from real mistakes, not imagined ones.

Kamel Dhakwani is a Senior Digital & AI Transformation Leader based in Bordeaux. He created GhostOne, and writes from his own experience in retail technology and AI agents. Drafted with AI assistance from my own experience, then reviewed by me.