AI Blocks › Set up AI to work for you
AI coding agent rules writer
Describe your project. Get a plan file and agent rules for working one test at a time.
AI coding agent rules writer is a free AI skill for the job "Set up AI to work for you". Give the instructions to an AI assistant that supports the required files and tools, then review its output.
Free · No account · Made by AI Blocks · Level: advanced
What it does
An AI coding agent left alone tends to build far more than you asked for. It may write many features at once, skip or delete tests that get in its way, and loop on a problem it cannot solve. You then have a large change that no one understands. This skill gives the agent a short, fixed way of working. The plan file holds the ordered test list. A one-word command makes the agent take the next unmarked test and nothing else. Standing rules say to write the simplest failing test, add the least code and tidy only when tests pass. Structure and behaviour changes go in separate commits. The skill also lists the warning signs that tell you the agent has drifted, and when to take the design back yourself.
You give it
- A description of the project and the language or tools
- Your test list or plan, if you have one
- Rules your team already has for commits and checks (optional)
You get
- A plan file with the ordered tests and what is done
- A one-word command and what it must do
- Standing rules for the agent that you can check from the commit history
- Warning signs and when to take the design back
Use it when
- You are starting a project with an AI coding agent and want it kept on a short lead.
- An agent keeps adding things you did not ask for.
- You found it disabled or deleted a test to make a run pass.
How to use it
- Start a chat with the skill. Open it if you added it to your AI, or copy it and paste it in.
- Describe the project and paste the test list or plan from the step before.
- Save the plan file and the rules in your project, in the place your agent reads rules from.
- Start the agent with the one-word command and watch the first run closely.
- After a few tests, check the commit history against the rules and tighten any that were missed.