Skip to content

🪢 Open source agent evals & observability: Trace, evaluate, and improve LLM applications with one open platform.

chore(web): Incude design-system component directive in AGENTS.md (#17700)

Ben Bachem4d7fbcb3cb18
diff --git a/.agents/AGENTS.md b/.agents/AGENTS.md
index b9f9ebaff6..2b4abbbec3 100644
--- a/.agents/AGENTS.md
+++ b/.agents/AGENTS.md
@@ -17,6 +17,11 @@ and a concrete next step when handed a link. Keep answers short. Handbook:
- Read the minimal local context required for the task.
- Keep changes scoped and avoid unrelated refactors.
+- Before creating a new component or reusing one from elsewhere in
+ `web/src/components`, first check `web/src/components/design-system` for an
+ existing component that satisfies the use case. Prefer the design-system
+ component and extend it when appropriate; use another component only when
+ the design system has no suitable option.
- Delegate exploratory or noisy work — broad code search, multi-file
investigation, log or test-output trawls — to a subagent so the
intermediate tool output stays out of the main context.
diff --git a/web/AGENTS.md b/web/AGENTS.md
index cf35104dd9..e671a44ddb 100644
--- a/web/AGENTS.md
+++ b/web/AGENTS.md
@@ -91,6 +91,11 @@ Sentry instrumentation skill first and decide whether it should capture at all
## Web Conventions
+- Before creating a new component or reusing one from elsewhere in
+ `src/components`, first check `src/components/design-system` for an existing
+ component that satisfies the use case. Prefer the design-system component
+ and extend it when appropriate; use another component only when the design
+ system has no suitable option.
- **Before adding or modifying a chart, dashboard, or chart formatter, read
`src/features/widgets/chart-library/ARCHITECTURE.md` first** — the charts
manifesto. It owns the data → preparer → visualiser contract: presentation