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

.trellis/spec/frontend/index.md

@@ -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.
 
 ---
 

.trellis/spec/hyb-oa/frontend-react-vite-design.md

@@ -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.