Skip to content

Add agent/contributor guide pointing to docs guidelines#771

Closed
SimonWallner wants to merge 2 commits into
mainfrom
add-agent-guidelines
Closed

Add agent/contributor guide pointing to docs guidelines#771
SimonWallner wants to merge 2 commits into
mainfrom
add-agent-guidelines

Conversation

@SimonWallner

@SimonWallner SimonWallner commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Linear: DOC-347

What

Makes the repo's documented contribution guidelines discoverable for both agents and humans:

  • AGENTS.md (and a CLAUDE.md that imports it) — agents load the guide, follow it, tell the user lightly that guidelines exist, and re-check compliance at PR time.
  • README.md — a short Contributing pointer so people browsing the repo on GitHub see the guidelines too.

Why

New contributors (human or agent) currently have no in-repo signal that a docs contribution workflow exists in Notion. This surfaces it in the two places each audience actually looks.

Design notes

  • No rules are copied into any file. The live Notion page is the single source of truth, so nothing here goes stale when the ticket/branch/release workflow changes. The only concrete detail is the Notion link itself.
  • AGENTS.md includes a fallback: if the agent can't reach Notion in a session, it asks the user to grant access (preferred) or to read the guide and own compliance.
  • This PR targets main because it's process/meta only — no docs content — so the monthly feature-branch rule doesn't apply.

🤖 Generated with Claude Code

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>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 8, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: dde1f03
Status: ✅  Deploy successful!
Preview URL: https://fb469f0b.localstack-docs.pages.dev
Branch Preview URL: https://add-agent-guidelines.localstack-docs.pages.dev

View logs

Surfaces the docs contribution guidelines for humans browsing the repo,
mirroring AGENTS.md. No rules copied — links to the Notion source of truth.

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

This is just the Starlight starter for now. We can begin moving existing content into `/content/docs`.

## Contributing

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is an internal LocalStack employee notion guide, this is not for a public repo readme

this readme in this public docs repo is for oss contributors, who cannot access internal LS employee information

@quetzalliwrites

quetzalliwrites commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

Hi Simon,

I’m going to go ahead and close this PR for two main reasons:

  1. Superseded by Active MVP Work: I am currently in active production for the AWS Docs MVP agent. We are closing this in favor of the tracking ticket and work happening directly via the docs team.
  2. Internal vs. Public Scope: The guide linked here is an internal LocalStack employee Notion guide, which shouldn't be surfaced in a public repository's README.md or agent instructions. This public docs repo readme is meant for open-source (OSS) contributors, who won't have the necessary access permissions to view internal employee information anyway.

Appreciate the initiative on setting up the agent guidelines, and we'll make sure the learnings here are carried over to the main MVP tracking work!

@SimonWallner SimonWallner deleted the add-agent-guidelines branch July 8, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants