Commits and Conflicts

Paul’s Hint of the Week · #3

Write a Rules File Your Assistant Actually Follows

· 3 min read

Inspired by Episode 4: The Infinite Apology Loop

Stop repeating yourself every session. A short project rules file sets boundaries, verification habits and conventions once.

What’s inside

  1. The goal
  2. Before you start
  3. Step by step
  4. Step 1: Start with protected paths
  5. Step 2: Add the verification commands
  6. Step 3: Add only the conventions it can’t infer
  7. Step 4: Say when to stop and ask
  8. Step 5: Keep it short and commit it
  9. Step 6: Add a rule after every incident
  10. Prompts to steal
  11. Checklist
  12. Common mistakes

Subscribers only

This hint is for subscribers.

Paul’s Hint of the Week is for subscribers. Subscribe free to read this hint, every hint before it, and get a new one in your inbox each week.

  • All 9 episodes, from Episode 1 on
  • Paul’s Hint of the Week: a step-by-step guide to better AI coding, every week
  • All three Conflict Resolution tips for every episode
  • The Weekly Commit: the new episode and a fix in your inbox each week