From 42c27429904c4228351857e600aa5bba2e13fe85 Mon Sep 17 00:00:00 2001
From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
Date: Tue, 14 Oct 2025 22:29:59 -0400
Subject: [PATCH] docs: add beacon css contributor note

---
 docs/beacon/css-mapping.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/beacon/css-mapping.md b/docs/beacon/css-mapping.md
index b7c29030..28468562 100644
--- a/docs/beacon/css-mapping.md
+++ b/docs/beacon/css-mapping.md
@@ -2,6 +2,8 @@
 
 This inventory captures the selectors that mattered in `torrent/dist/beacon.vendor.css` and how they now map to design-system driven rules. The goal is to keep future tweaks aligned with shared tokens rather than re-introducing ad-hoc styles or vendor bundles.
 
+> **Contributor note:** Beacon CSS updates must follow the [“Styling & Theming Rules (token-first)” guidance in `AGENTS.md`](../../AGENTS.md#styling--theming-rules-token-first) and the [README CSS build pipeline](../../README.md#css-build-pipeline). Run the relevant scripts before committing changes—at minimum `npm run lint:css`, `npm run build:css`, `npm run check:css`, and `npm run build:beacon` to ensure the Tailwind output and bundled assets stay in sync with token rules.
+
 ## Angular UI Grid
 
 | Legacy selector(s) | Tailwind component mapping | Notes |