Files
workbuddy_skills/open-design/design-templates/wireframe-greybox/SKILL.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

90 lines
3.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
name: wireframe-greybox
description: |
A crisp greybox / blueprint lo-fi wireframe — neutral grey blocks on a
pale page, image placeholders drawn as a rectangle with a diagonal X,
text shown as solid "lorem bars" of varying widths, sharp 1.5–2px
borders, and a single monospace redline accent for annotations. Reads
like a structural blueprint before any visual design is applied. Use
when the brief asks for "greybox", "blueprint wireframe", "lo-fi
dashboard", "low fidelity", "线框图", or "灰盒原型".
triggers:
- "greybox"
- "grey box wireframe"
- "blueprint wireframe"
- "lo-fi dashboard"
- "low fidelity"
- "wireframe"
- "线框图"
- "灰盒"
od:
mode: prototype
platform: desktop
scenario: design
fidelity: wireframe
preview:
type: html
entry: index.html
design_system:
requires: false
sections: [color, typography, layout, components]
example_prompt: "Greybox a lo-fi blueprint wireframe for a desktop SaaS dashboard — app bar, sidebar nav, a 4-up KPI row, a schematic chart panel, and a list/table with image-placeholder thumbnails, all in neutral grey with monospace redline annotations."
---
# Wireframe Greybox Skill
Produce a single crisp greybox wireframe page. The whole point is
*structure, not skin* — communicate hierarchy and layout with neutral
grey blocks, never with real color, copy, or imagery. Everything is a
placeholder: text is grey "lorem bars", images are rectangles with a
diagonal cross, numbers are big solid blocks. The only color on the page
is the single redline accent reserved for monospace annotations.
## Workflow
1. **Stay structural.** Ignore any DESIGN.md that pushes finished UI —
this is deliberately low fidelity. Use a clean system sans (Inter /
system-ui) for shape and a mono (IBM Plex Mono / JetBrains Mono) for
the redline annotations only. No hand-drawn fonts, no brand color.
2. **Set the greybox palette.** Page is a pale neutral (`#f7f7f8`),
blocks are medium grey (`#e3e3e6`), borders are crisp and defined
(`#c9c9cf` for soft edges, `#1c1b1a` for emphasis), and exactly one
accent (a blue or coral redline) carries every monospace annotation.
Keep contrast high enough to read as a small thumbnail — never
near-white-on-white.
3. **Lay out the dashboard**, in order, each on its own `data-od-id`:
- **App bar** — a logo greybox, a row of nav lorem-bars, and an
avatar circle on the right.
- **Sidebar nav** — icon squares + lorem-bar labels; mark one item
active with a filled/inverted block.
- **KPI row** — four greyboxes, each a small label bar above a big
solid "number" bar.
- **Chart panel** — an inline SVG greybox: axes plus a few
hatched/grey bars or a schematic line. No real data.
- **List / table panel** — a header row plus ~5 rows of lorem bars,
with one column of image-placeholders drawn as a box with a
diagonal X.
- **Annotations** — one or two small monospace redlines pinned to the
canvas (e.g. `01 · 12-col grid`, `max-width 1280`).
4. **Write** one self-contained HTML document — `<!doctype html>`
through `</html>`, CSS inline, no external JS or images. SVG and CSS
draw every placeholder. A `max-width` container plus a media query
collapses columns under ~1000px.
5. **Self-check.** It should read as a blueprint at thumbnail size: grey
blocks, X-crossed image boxes, lorem bars, and exactly one accent
color on the monospace redlines. If any greybox is missing, the page
looks colored, or it disappears as a blank thumbnail, fix it.
## 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.