Add agent/contributor guide pointing to docs guidelines

Adds AGENTS.md (with CLAUDE.md importing it) so agents and new
contributors are made aware that documented contribution guidelines
exist, and to follow them. The file deliberately holds no rules itself —
the live Notion guide is the single source of truth so it can't go stale.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: SimonWallner

AGENTS.md

@@ -0,0 +1,33 @@
+# LocalStack Docs — Agent Guide
+
+This repo has documented contribution guidelines. They can change over time, so the
+**single source of truth is the live Notion page — never a copy.** This file
+deliberately contains none of the actual rules; it only points you to them.
+
+**Guidelines:** Guide: LocalStack Docs Workflows & Management
+https://www.notion.so/localstack/Guide-LocalStack-Docs-Workflows-Management-1d1fc2a234318044b044fc6554fcc9e4
+
+## What the agent should do
+
+1. **Load the guidelines.** When a session will create or change docs, fetch the
+   Notion page above and follow it throughout the work.
+
+2. **Tell the user, lightly.** Once per session, let them know the guidelines exist
+   — don't recite them:
+
+   > 📌 Heads up: contributing to these docs follows LocalStack's guidelines. I'll
+   > read them and follow them for you. Full guide: <Notion link>
+
+   Non-blocking, once per session. If the user says they know the process, drop it.
+
+3. **At wrap-up, apply them.** Before the work is finalized (e.g. opening a PR),
+   re-check the guidelines and make sure the change complies.
+
+## If you can't access Notion
+
+If you can't fetch the page in this session, don't guess. Tell the user and offer
+two paths — preferred first:
+
+- **Preferred:** ask them to give you Notion access so you can read and follow it.
+- **Fallback:** give them the link and ask them to read it and own compliance.
+  At that point your part is done.

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md