From 0e8b7bc7afc11564f6c0c8239a0cd139622e6877 Mon Sep 17 00:00:00 2001 From: xiaomai Date: Thu, 30 Apr 2026 14:24:16 +0800 Subject: [PATCH] docs(agents): require reading DesignGuidelines.html for UI tasks Update the agent workflow to include reading DesignGuidelines.html Add a new section detailing rules for component reuse and UI modifications --- AGENTS.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 4493099..e5799c8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -14,15 +14,26 @@ For any non-trivial task: 1. **Read `DESIGN.md`** -2. **Produce a short plan (no code)** -3. Wait for approval -4. Implement in small steps -5. Run lightweight validation when practical (lint/typecheck). Do not run tests in WSL. +2. For UI, component, layout, or styling tasks, **also read `DesignGuidelines.html`** +3. **Produce a short plan (no code)** +4. Wait for approval +5. Implement in small steps +6. Run lightweight validation when practical (lint/typecheck). Do not run tests in WSL. Do NOT skip planning. --- +## UI Design Guidelines + +* Use `DesignGuidelines.html` as the reference for UI design, visual style, and component behavior. +* Prefer reusing existing components that already match the guidelines. +* If a needed component does not exist, create the smallest necessary component based on `DesignGuidelines.html`. +* Existing components may be upgraded to match `DesignGuidelines.html`, but only when directly related to the task. +* Do not introduce broad UI rewrites, new design systems, or extra abstraction layers unless explicitly required. + +--- + ## Scope Control (Prevent Code Bloat) * Only modify files directly related to the task.