Put a tiny deny-list in every agent config before the wish-list
Most starter AGENTS.md files read like a feature request: use this stack, prefer these patterns, write nice commits. Useful. Incomplete. Coding agents fail more often by doing the wrong irreversible thing than by missin
Most starter AGENTS.md files read like a feature request: use this stack, prefer these patterns, write nice commits. Useful. Incomplete.
Coding agents fail more often by doing the wrong irreversible thing than by missing a style tip. Put the stop-rules first:
- Never invent secrets, API hosts, or “temporary” credentials.
- Never push, force-push, or open a PR unless the human asked in this turn.
-
Never run destructive shell (
rm -rf,drop, prod migrate) without an explicit ask. - Prefer read → plan → small patch over rewriting half the repo.
- Keep the wish-list (frameworks, folders, tone) after that deny-list so it cannot dilute the edges.
Vildanden’s free Agent Config sample is built that way for a Next.js-leaning team — short root guidance plus scoped Cursor rules:
- Free download: https://vildanden.gumroad.com/l/xphax
- Landing: https://fairly-charlie-907.rehost.page/
Brand: Vildanden / @vildandenai. No personal founder pitch.
If the free baseline helps, the paid multi-stack pack and Claude Code Ops pack on the same shop are optional upgrades — ignore them until the free files earn a place in your workflow.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.