Kingsmai/pokopiawiki.tootaio.com
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(agents): require reading DesignGuidelines.html for UI tasks

Browse Source 
Update the agent workflow to include reading DesignGuidelines.html
Add a new section detailing rules for component reuse and UI modifications
This commit is contained in:
xiaomai
2026-04-30 14:24:16 +08:00
parent dabbf0ec70
commit 0e8b7bc7af
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
AGENTS.md
View File

@@ -14,15 +14,26 @@
For any non-trivial task: For any non-trivial task:
1. **Read `DESIGN.md`** 1. **Read `DESIGN.md`**
2. **Produce a short plan (no code)** 2. For UI, component, layout, or styling tasks, **also read `DesignGuidelines.html`**
3. Wait for approval 3. **Produce a short plan (no code)**
4. Implement in small steps 4. Wait for approval
5. Run lightweight validation when practical (lint/typecheck). Do not run tests in WSL. 5. Implement in small steps
6. Run lightweight validation when practical (lint/typecheck). Do not run tests in WSL.
Do NOT skip planning. 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) ## Scope Control (Prevent Code Bloat)
* Only modify files directly related to the task. * Only modify files directly related to the task.