Files
workbuddy_skills/open-design/design-templates/live-dashboard/references/layouts.md
T
admin 5afeb6b78a ④段整套同步(六节 + P/S/F/J + 模板)+ open-design 移到技能根
一、④段整套同步(用户选候选 A)
- 新增 `references/stage-proto-doc/assets/产品文档模板.html`(16 KB/247 行,从备份拷、转 LF)。
- ④段 SKILL.md 换成备份 15:28 那版,并按模板口径改齐:
  · 「产品文档框架」从「四块+一附录」改成**六节** —— 页面结构/功能清单/使用场景/操作流程/
    跨页与界面状态/待确认与偏离;与模板同构,⛔ 不从空白页重写结构。
  · 编号从 R/S/F 改成 **P 页面/S 场景/F 功能/J 二级功能**,各自唯一、按展示顺序通排。
  · 保留旧版有价值的要求:每项功能补齐 做什么/入口在哪/输入边界/异常与恢复;重点功能三处标红;
    横向流程图每步写清页面/功能/操作/完成判据。
  · 完成标准「七节」→「六节」,自查清单同步换掉「需求」那批条目,补模板与配图两条。
  · 路径 `designs/<项目>/` → `docs/pm/<项目>/ui/`(2 处)。
  · 补回本机那条「每份产出文档开头都要有一张图」的引用(指向主 skill,段内不复述)。
- 主 skill 同步:四段结构表④行、④段沿革、画图小节(④段画页面结构图 + 用户路径)。

二、open-design 移到技能根(用户选候选 A)
- `git mv product-planning/references/stage-delivery/assets/open-design → open-design/`(4178 文件)。
- `.gitignore` 白名单加 `!/open-design/` —— 否则移出去就不再纳入版本控制。
- 引用改 11 处:路径形态 `assets/open-design/...` → `<技能根>/open-design/...`;
  「随段携带的自带件」改称「同根技能」;「路径怎么找」那条改成自带件(段内相对路径)与
  同根技能(`<技能根>/<技能名>/`)两类分开写。
- open-design 自己的 ATTRIBUTION.md 两处同步(它现在与 oil-ui-pro 同层)。
- 副作用(有益):命名闸门读数由 2063 降到 225 —— 此前它把 open-design 里 919 个第三方 md
  当成规则一起扫了;现在只扫本包 23 个 md。已确认④段的 H1 与 4a/4b/4c 子步仍在检查范围内。

三、验收
- check_naming.py --ws E:/ProgramData/AIProject/contentm_agent = 通过 225 / 失败 0 / 提示 27。
- 活文件里 `assets/open-design` 残留 0;工作区 CRLF 文件 0。
2026-10-15 21:17:28 +08:00

3.2 KiB
Raw Blame History

Layouts

Pick exactly one layout. State your choice in your reply before emitting index.html.

All three share the same shell from assets/template.html: grid-template-columns: 240px 1fr (sidebar + main), a 44px topbar, a 56px page top padding, and a max-width of 1100px on the page column.


A · Classic dashboard (default)

Vertical stack inside the page column, in this order:

  1. Page header (emoji + title + meta row)
  2. Live-Artifact callout
  3. KPI grid — 1 row × N (where N = inputs.kpi_count), 1px hairline grid
  4. Two-column block — 1.1fr 1fr:
    • left: Tasks created · last 7 days sparkline card
    • right: Recent activity feed card
  5. Linked database — Tasks · Active sprint
  6. Footer

Use this when:

  • The user said "team dashboard" / "ops dashboard" without further qualifier.
  • The user wants a generalist Notion-like landing page for a team workspace.

This is what example.html ships.


B · Kanban-flavored

Same shell, but replace the linked database (step 5) with a 3-column kanban board:

┌── To do ───────┐ ┌── In progress ─┐ ┌── In review ───┐
│ card           │ │ card           │ │ card           │
│ card           │ │ card (changed) │ │ card           │
│ + add          │ │ card           │ │ card           │
└────────────────┘ └────────────────┘ └────────────────┘

Cards are 1px-bordered, 12px padding, with: emoji row + title (medium weight) + assignee chip + due date.

Use this when:

  • The user explicitly said "kanban", "sprint board", "backlog view".
  • inputs.include_task_table is true and the user mentioned drag / swimlane / column.

The Live behavior stays the same: cards animate from one column to the next on refresh (250ms ease-out translate, plus a 600ms accent left-border on the moved card).


C · KPI-only hero

Drop the database entirely. The page is just:

  1. Page header
  2. Callout (slightly taller — explain the data range)
  3. Hero KPI grid: 2 × 2 with 32px → 56px font-size on the numbers (use display_scale parameter)
  4. The sparkline spans full width (no two-column split)
  5. Activity feed becomes a single horizontal ticker (3 visible rows max, auto-scrolls every 8s)
  6. Footer

Use this when:

  • inputs.include_task_table === false.
  • The user said "exec summary", "morning standup", "weekly snapshot".
  • The user wants something to throw on a TV in the office.

Density & responsive notes (apply to all three)

  • The density parameter controls the gap between blocks (callout → KPIs → two-column → DB) — 8px low, 36px high. Default 18.
  • Below 980px viewport, sidebar hides, the page padding drops to 20px, KPI grid becomes 2-up, and the two-column block stacks.
  • Below 640px, the linked database hides due and priority columns and the kanban becomes a 1-column vertical scroll.
  • Honor prefers-reduced-motion: reduce everywhere — disable tweens, pulses, kanban-card translate, ticker auto-scroll, and the live-pill pulse.