Skip to content
E. AguilarKeel Skillsdocs
Menu · Policy packs

Configure

Policy packs

Starter AGENT_POLICY.md files for common stacks. Copy the closest one to your project root, then cut it down to what's actually true for you.

A policy pack is just a pre-filled AGENT_POLICY.md with the hot zones a given stack usually has — deploy surfaces, the database, the published site. It saves you the blank-page problem. They live in the policies/ directory of the repo.

Available packs#

web-app-deploy

A generic web app with a deploy step and a published front end.

nextjs-vercel

Next.js on Vercel — build, preview, and production deploy surfaces.

supabase

Supabase — schema, migrations, RLS, and the live database as hot zones.

How to use one#

  1. Open the pack closest to your stack and copy its contents.
  2. Save it as AGENT_POLICY.md at your project root.
  3. Trim and correct it. Delete what doesn't apply, and replace the placeholder paths with your real ones — a hot zone that points at a path you don't have is noise.
  4. Fill in section 3 (where decisions and state get recorded) — that one is project-specific and the packs can only guess.

Key idea

A pack is a head start, not a finished policy. The value is in section 1 being concrete and true for your repo.

Contribute a pack#

Policy packs for new stacks are very welcome. See CONTRIBUTING.md in the repo for how to add one.