| name | dashboard |
| description | Chinese-first internal-tool / ops dashboard template — light-mode Linear-grade layout with serif headlines, tabular Inter numerals, KPI hero, pulse bars, progress rings, team-presence grid, activity timeline, and CJK-aware typography. |
| visibility | public |
| mode | template |
| carrier | web-page |
| scenario | internal-tool |
| pattern_source | stack-dashboard-zh.html |
| source_priority | skill-first |
| triggers | ["做个运营仪表盘","内部工具看板","中文 ops dashboard","KPI hero 看板","Linear 风看板"] |
Dashboard Template
Use this template when the artifact is a Chinese-language internal tool / ops / project dashboard that needs to look designed-in-Chinese, not translated.
Use When
- The user is mocking an admin panel, operations workbench, project portfolio view, or team-status console.
- The dashboard is CJK-primary — Latin and numerals serve the Chinese hierarchy, not the other way around.
- The look should be light-mode, calm, editorial-leaning (Noto Serif SC headlines, Inter numerals), with restrained status color.
- Surfaces include: greeting + KPI hero, project cards with progress rings, multi-chart analytics row, activity timeline, team-presence grid, async standup blocks.
Avoid When
- The artifact is a marketing landing for a SaaS product — use
saas-landing/ instead.
- The artifact is a public-facing report meant to be read top-to-bottom like an article — use
Project Brief/ or blog-post/.
- The user wants a dark observability "war-room" UI — this template is light and calm; rebuild rather than dark-mode-flip.
- The artifact is mobile-first — the layout is built around a wide desktop viewport.
Required Reading
Read this SKILL.md first. Do not read stack-dashboard-zh.html by default.
Read stack-dashboard-zh.html only when you need concrete component geometry (ring sizes, pulse-bar segment widths, tab-grid spacing, status-dot sizing) or the Chinese font-stack ordering. Extract patterns; do not copy DOM, classnames, placeholder team names, or color tokens wholesale.
Design Strategy
Before placing components, decide the dashboard's job:
- daily workbench (greeting + today's focus + KPI + team)
- project portfolio (cards with status, owners, progress)
- analytics view (charts + sparklines + bottleneck breakdown)
- activity / on-call view (timeline + heatmap + presence)
A single page can blend these, but pick a hero — the first screen should answer one primary question.
Design Structure / Visual Weight
The page is a composition of zones with deliberately different visual weight — not a uniform grid of equal cards. Before placing any component, sketch the weight tiers:
- Hero (≈ 30–35% of first screen) — greeting + 3–4 large KPI tiles with tabular numerals and a thin trend line. Dominant; sets the headline.
