oa-email-code-login 实现邮箱验证码登录
这个提交包含在:
@@ -2,14 +2,18 @@
|
||||
|
||||
## Source Of Truth
|
||||
|
||||
UI work must read `docs/产品设计规则.md` first and align with the Hyinda brand
|
||||
style. For PC/mobile/WeCom pages, add Playwright or visual verification when
|
||||
reasonable.
|
||||
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.
|
||||
|
||||
## Rules
|
||||
|
||||
- Use existing React/Vite/Tailwind patterns and shared components before adding
|
||||
page-local UI systems.
|
||||
- When `frontend-design` and older project visual rules conflict, follow
|
||||
`frontend-design` for visual direction while preserving security, privacy,
|
||||
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
|
||||
|
||||
在新工单中引用
屏蔽一个用户