Files
workbuddy_skills/open-design/design-templates/AGENTS.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

design-templates

This directory holds design templates — packaged "shapes" the agent renders into a project artifact (decks, prototypes, image/video/audio templates, …). Each entry is a folder with a SKILL.md (same shape as functional skills) plus rendering side files (example.html, assets/, references/, …).

If the entry primarily does work on user input — utilities, briefs, asset packagers, fidelity audits — it belongs under ../skills/ instead. See specs/current/skills-and-design-templates.md for the full split.

Daemon plumbing

  • Listed under /api/design-templates. The shape mirrors /api/skills (same SkillSummary/SkillDetail types) so the web client can reuse a single SkillSummary[] consumer for both surfaces.
  • Asset and example routes (/api/skills/:id/example, /api/skills/:id/assets/*) intentionally span both registries — the example HTML rewrites to /api/skills/<id>/... regardless of which root owns the folder, so URLs keep resolving after the split.
  • Surfaced in the New-project panel's per-mode "Start from" rail as the rendering catalogue; the redesigned home has no top-level Templates tab.

Adding a design template

  1. Create design-templates/<my-template>/SKILL.md with name, description, triggers, and an explicit od.mode (one of prototype, deck, template, image, video, audio).
  2. Ship a baked example.html (and any side files) so the shared example and asset routes have preview content to serve.
  3. Optionally drop additional baked samples under examples/<key>.html to surface them as derived <parent>:<key> cards.

Deck preview navigation contract

Any template with od.mode: deck must make its baked example.html usable inside the gallery iframe without relying on the host app to add navigation. Use a shared deck runtime where one is available; otherwise ship a tiny local runtime with the same minimum behavior.

  • Keyboard: ArrowRight / ArrowDown / PageDown / Space move to the next slide; ArrowLeft / ArrowUp / PageUp move to the previous slide; Home and End jump to the first and last slide. Ignore events from inputs, selects, textareas, and editable regions.
  • Wheel / trackpad: accumulated deltaX + deltaY past a small threshold moves exactly one slide, then resets quickly so a single gesture does not overshoot.
  • Touch: a horizontal swipe of roughly 50px or more, greater than the vertical movement, moves previous / next.
  • Dots: render one clickable button per slide, update the active dot on every navigation path, and mark it with aria-current="true".
  • Active slide state: keep the visible slide marked with .slide.active; adding .is-active as a compatibility alias is fine. OpenDesign's preview bridge reads this state for the host slide counter, so it must stay in sync with keyboard, wheel, touch, and dot navigation.
  • Iframe safety: focus the deck on load / pointer interaction so keyboard navigation works after the gallery preview appears. Avoid scrollIntoView() because it can move the parent page instead of the deck.
  • Fallbacks: no-script and print output should still expose every slide. Hide non-active slides only after the runtime has booted.