Every AI coding agent reads an instruction file — AGENTS.md, CLAUDE.md, or a system prompt. Most are copy-pasted and half-stale. Groundrules is a visual builder for them: drag battle-tested blocks (conventions, workflows, hard rules with verification probes) onto a canvas, compile to any target your tools read, then Test Drive against 12+ live models (Claude, GPT, Gemini, Grok…) to see whether the agent actually obeys — before you commit the file. Core builder is free.
No reviews yetBe the first to leave a review for Groundrules
Maker
📌
Hi Product Hunt 👋
I built Groundrules because I kept rewriting the same instruction files for every project — and because an agent once "fixed" my failing tests by deleting them. ✓ 0 tests failing. Technically correct. My fault, really: nobody had written the rules down.
So: a visual builder for the files agents actually read. Assemble a config from ~80 battle-tested blocks (conventions, workflows, hard rules like "never commit secrets" — with probes to verify they hold), and compile it to AGENTS.md, CLAUDE.md, a plain system prompt, or settings.json + ESLint rails. The part I'm proudest of is Test Drive: run your rules against a dozen live models and see whether the agent actually obeys them. A rule that doesn't survive contact with the model is just a wish.
The core loop — building, exporting, sharing — is free and stays that way. Pro ($6/mo) covers what costs me money: hosted test runs, version history.
Honest rough edges: the community catalog is young (submissions welcome — review is currently just me), and Team features are a waitlist.
I'd love to know: what rules does your team enforce that belong in the catalog? The best blocks so far came from other people's war stories.
Report
honestly the test drive against 12+ models thing is genuinely clever, like actually seeing whether the agent obeys before you ship the file saves so much guesswork. solid execution.
Report
Maker
@vedatmdxs Thanks Vedat! Test Drive came out of getting burned... I kept writing rules that felt airtight until a model cheerfully ignored them. Watching an agent break your rule in a sandbox costs 30 seconds; watching it break the rule in your repo costs an afternoon. Curious to know which model do you run day to day? That's the one worth test-driving against first.
Report
The test-drive-against-live-models idea is genuinely clever, turning what used to be blind faith in a prompt file into something you can actually verify before shipping it.
Report
Maker
@theshipper "Blind faith in a prompt file" is exactly the disease, well put. The uncomfortable discovery from building it: rules that survive one model sometimes die on another; same file, different obedience. That's why it's 12+ models and not a generic linter. If you take it for a spin, I'd love to know if any of your go-to rules fail somewhere surprising as those make the best catalog blocks.
honestly the test drive against 12+ models thing is genuinely clever, like actually seeing whether the agent obeys before you ship the file saves so much guesswork. solid execution.
@vedatmdxs Thanks Vedat! Test Drive came out of getting burned... I kept writing rules that felt airtight until a model cheerfully ignored them. Watching an agent break your rule in a sandbox costs 30 seconds; watching it break the rule in your repo costs an afternoon. Curious to know which model do you run day to day? That's the one worth test-driving against first.
The test-drive-against-live-models idea is genuinely clever, turning what used to be blind faith in a prompt file into something you can actually verify before shipping it.
@theshipper "Blind faith in a prompt file" is exactly the disease, well put. The uncomfortable discovery from building it: rules that survive one model sometimes die on another; same file, different obedience. That's why it's 12+ models and not a generic linter. If you take it for a spin, I'd love to know if any of your go-to rules fail somewhere surprising as those make the best catalog blocks.