DEV Community

Vildanden
Vildanden

Posted on

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 missing a style tip. Put the stop-rules first:

  1. Never invent secrets, API hosts, or “temporary” credentials.
  2. Never push, force-push, or open a PR unless the human asked in this turn.
  3. Never run destructive shell (rm -rf, drop, prod migrate) without an explicit ask.
  4. Prefer read → plan → small patch over rewriting half the repo.
  5. 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:

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.

Top comments (0)