od-field-notes-editorial
制作调研笔记或观察日志风格的编辑页面。当用户提出相关页面或原型设计需求时使用本技能。先读取 read_skill open-design 获取总控流程,再按本技能模板与清单执行。
- License 许可
- AGPL-3.0
- 最近更新
- 2026-09-07
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- od-field-notes-editorial
- description
- 制作调研笔记或观察日志风格的编辑页面。当用户提出相关页面或原型设计需求时使用本技能。先读取 read_skill open-design 获取总控流程,再按本技能模板与清单执行。
02 资源文件 2
- 资产文件assets/template.html10.0 KB
- 参考文档references/checklist.md1.4 KB
03 SKILL.md 正文
od-field-notes-editorial
这是 Open Design 迁移后的瘦表面技能。
使用方式
- 先调用 ead_skill 读取 open-design,遵循总控流程(问卷、方向、品牌、五维自评)。
- 若 ssets/template.html 存在,先复制到工作文件再填充内容。
- 若 eferences/checklist.md 存在,交付前必须逐条自检。
资源来源
- 上游技能:OpenDesign/skills/field-notes-editorial-template
- 本技能仅保留可复用模板与清单,风格决策由 open-design 总控技能统一。
04 同仓库更多 Skills
wireframe-mobile-flow
A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames laid out in a row on a board, showing a connected user flow (Onboarding → Home feed → Item detail → Confirm). Grey-box content inside each device, dashed connector arrows + numbered step labels between screens, and a couple of annotation callouts. Reads like an app flow pinned to a whiteboard before any pixels are committed. Use when the brief asks for "mobile wireframe", "app flow", "user flow wireframe", "lo-fi mobile", "low fidelity", "线框图", "移动端线框", or "App 流程".
web-prototype
General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.
waitlist-page
Minimal pre-launch landing with email capture, brand logo, and optional decorative layer. Reads DESIGN.md for colors, typography, and layout rules. Best for: product launches, beta signups, early access programs, indie projects.
team-okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
pricing-page
A standalone pricing page — header, plan tiers, feature comparison table, and an FAQ. Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.
pm-spec
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".