治理前端设计规则 05-26-oa-seven-day-trial-live-ops

这个提交包含在:
2026-05-27 17:12:22 +08:00
父节点 a034c5f007
当前提交 8f17d6454d
共修改 15 个文件,包含 104 行新增和 298 行删除
+4 -3
查看文件
@@ -5,9 +5,10 @@
## Overview
hyb-oa frontend work uses React, TypeScript, Vite and Tailwind under `client/`.
The project-specific frontend/design rules live in
`../hyb-oa/frontend-react-vite-design.md`; detailed visual facts remain in
`docs/产品设计规则.md`.
The project-specific frontend implementation rules live in
`../hyb-oa/frontend-react-vite-design.md`; product experience facts remain in
`docs/产品设计规则.md`. Visual and interaction design authority comes from the
installed `frontend-design` skill.
---
@@ -3,9 +3,10 @@
## Source Of Truth
Frontend visual and interaction design uses the installed `frontend-design`
skill as the primary design authority. `docs/产品设计规则.md` remains a product,
brand and historical fact source, not the final aesthetic tie-breaker. For
PC/mobile/WeCom pages, add Playwright or visual verification when reasonable.
skill as the primary design authority. `docs/产品设计规则.md` remains a product
experience and business-boundary fact source, not a visual, brand or aesthetic
rulebook. For PC/mobile/WeCom pages, add Playwright or visual verification when
reasonable.
## Rules
@@ -16,8 +17,9 @@ PC/mobile/WeCom pages, add Playwright or visual verification when reasonable.
Trellis, deployment and business data boundaries.
- PC pages should keep dense but orderly OA layouts: clear header, filters,
table/list, status, details and predictable actions.
- Mobile pages must use the unified mobile shell, card/list rows, safe-area and
sticky action patterns from the design rules.
- Mobile pages must reuse the existing unified mobile shell, card/list rows,
safe-area and sticky action patterns unless the current task intentionally
redesigns them with `frontend-design`.
- Do not add decorative landing-page styling to operational OA pages.
- Run `cd client && npm run typecheck && npm run build` for frontend changes.
@@ -33,3 +33,10 @@
- findingCount:0
- 主报告:`research/day2-oa-real-use-daily/summary.json`
- 备注:首次运行时企业微信渲染矩阵因测试 mock 未覆盖 `/api/auth/capabilities` 报错;已补 mock 并复跑完整 Day 2 巡检通过。
## 设计规则治理
- 用户确认项目旧有前端设计规则重复且噪音过大后,已将 `docs/产品设计规则.md` 从“设计规则基线”瘦身为“产品体验事实源”。
- 前端视觉、布局审美、组件观感、字体、颜色、动效、间距和交互细节统一以 `frontend-design` skill 为裁决来源。
- `docs/产品设计规则.md` 仅保留 hyb-oa 特有的目标用户、PC/移动/企业微信职责、页面分层、信息语义、OA/企微主办边界和验收边界。
- 已同步 AGENTS、Trellis frontend spec、文档索引、事实源矩阵、Agent 交付实践、试运行手册、测试规约和相关业务规约,避免后续 agent 继续引用旧的竞品/品牌/样板设计规则。