admin
5afeb6b78a
一、④段整套同步（用户选候选 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。
96 lines
4.2 KiB
Markdown
96 lines
4.2 KiB
Markdown
---
|
||
name: wireframe-mobile-flow
|
||
description: |
|
||
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 流程".
|
||
triggers:
|
||
- "mobile wireframe"
|
||
- "app flow"
|
||
- "user flow"
|
||
- "lo-fi mobile"
|
||
- "wireframe"
|
||
- "low fidelity"
|
||
- "移动端线框"
|
||
- "App 流程图"
|
||
od:
|
||
mode: prototype
|
||
platform: auto
|
||
scenario: design
|
||
fidelity: wireframe
|
||
preview:
|
||
type: html
|
||
entry: index.html
|
||
design_system:
|
||
requires: false
|
||
sections: [color, typography, layout, components]
|
||
example_prompt: "Wireframe a lo-fi mobile flow v0.1 — three phone frames in a row (Onboarding → Home feed → Item detail), grey-box screens, dashed step arrows between them, and two annotation callouts."
|
||
---
|
||
|
||
# Wireframe Mobile Flow Skill
|
||
|
||
Produce a single board showing a mobile app's user flow as a row of lo-fi
|
||
phone frames. The point is the *flow* — how a user moves screen to screen —
|
||
not the polish of any one screen. Keep the screens clean grey-boxes (not
|
||
scribbly) but keep the connectors and annotations loose and informal.
|
||
|
||
## Workflow
|
||
|
||
1. **Skip the DESIGN.md** if it pushes for finished UI. This skill is
|
||
deliberately low-fidelity: greyboxes, placeholder rects, and bars stand in
|
||
for real content. Honor type tokens only loosely (system sans for the
|
||
board, mono for labels and datelines).
|
||
2. **Pick the flow steps** from the brief — typically 3–4 connected screens
|
||
like Onboarding → Home feed → Item detail → Confirm. Name each step so the
|
||
connector arrows can carry a numbered, verb-first label ("① tap Start",
|
||
"② open item", "③ add to cart").
|
||
3. **Lay out the board**, in order:
|
||
- **Board header** — bold sans title with a pinned "WIREFRAME v0.1 ·
|
||
MOBILE" tag (dashed border, slight rotation) and a mono dateline on the
|
||
right (date / device / fidelity).
|
||
- **Phone row** — 3–4 rounded device frames (~240–280px wide) in a
|
||
horizontal row, each with a notch / status bar. Inside each frame put
|
||
the greybox content for its step: hero image-placeholder (rect + X),
|
||
title/price bars, list cards (thumbnail X + 2 text bars), category
|
||
chips, a bottom tab bar, sticky CTA bars, a confirm checkmark — match the
|
||
screen's role.
|
||
- **Connectors** — dashed arrows between consecutive phones, each carrying
|
||
a small mono step label describing the tap that advances the flow.
|
||
- **Annotations** — 1–2 small sticky / callout notes pinned near a screen
|
||
to flag intent ("hero must sell value in 3s", "checkout = 1 screen").
|
||
4. **Write** a single HTML document:
|
||
- `<!doctype html>` through `</html>`, CSS inline, no external JS, no
|
||
external images (CSS/SVG placeholders only).
|
||
- Use Inter / system-ui for the board and IBM Plex Mono for labels via
|
||
Google Fonts; a light marker font is allowed for annotations only.
|
||
- Defined dark device-frame borders, medium-grey content blocks on white
|
||
screens, and a single accent color for arrows and annotations so the
|
||
board reads clearly even as a small thumbnail.
|
||
- `data-od-id` on the header, each phone screen, the connectors, and the
|
||
annotations.
|
||
5. **Self-check**:
|
||
- The three main phones are visible in a ~1280px viewport; the flow reads
|
||
left-to-right.
|
||
- Screens are clean greyboxes (not scribbly); connectors and stickies are
|
||
the loose, informal parts.
|
||
- No near-white-on-white regions — every block has a visible grey fill or
|
||
border. If a screen renders blank as a thumbnail, raise the contrast.
|
||
|
||
## Output contract
|
||
|
||
Emit between `<artifact>` tags:
|
||
|
||
```
|
||
<artifact identifier="wireframe-slug" type="text/html" title="Wireframe — Title">
|
||
<!doctype html>
|
||
<html>...</html>
|
||
</artifact>
|
||
```
|
||
|
||
One sentence before the artifact, nothing after.
|