Files
workbuddy_skills/open-design/design-systems/cosmic/DESIGN.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

2.9 KiB
Raw Blame History

Design System Inspired by Cosmic

Category: Creative & Artistic Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.

1. Visual Theme & Atmosphere

Futuristic sci-fi aesthetic with dark themes, vibrant neon accents, and immersive spatial elements.

  • Visual style: playful, premium
  • Color stance: primary, neutral, success, warning, danger
  • Design intent: Keep outputs recognizable to this style family while preserving usability and readability.

2. Color

  • Primary: #3B82F6 — Token from style foundations.

  • Secondary: #8B5CF6 — Token from style foundations.

  • Success: #16A34A — Token from style foundations.

  • Warning: #D97706 — Token from style foundations.

  • Danger: #DC2626 — Token from style foundations.

  • Surface: #FFFFFF — Token from style foundations.

  • Text: #111827 — Token from style foundations.

  • Neutral: #FFFFFF — Derived from the surface token for official format compatibility.

  • Favor Primary (#3B82F6) for CTA emphasis.

  • Use Surface (#FFFFFF) for large backgrounds and cards.

  • Keep body copy on Text (#111827) for legibility.

3. Typography

  • Scale: 12/14/16/20/24/32
  • Families: primary=Audiowide, display=Audiowide, mono=JetBrains Mono
  • Weights: 400
  • Headings should carry the style personality; body text should optimize scanability and contrast.

4. Spacing & Grid

  • Spacing scale: 4/8/12/16/24/32
  • Keep vertical rhythm consistent across sections and components.
  • Align columns and modules to a predictable grid; avoid ad-hoc offsets.

5. Layout & Composition

  • Prefer clear content blocks with consistent internal padding.
  • Keep hierarchy obvious: headline → support text → primary action.
  • Use whitespace to separate concerns before adding borders or shadows.

6. Components

  • Buttons: primary action uses #3B82F6; secondary actions stay neutral.
  • Inputs: strong focus-visible states, clear labels, and predictable error messaging.
  • Cards/sections: use consistent radii, spacing, and elevation strategy across the page.

7. Motion & Interaction

  • Use subtle transitions that emphasize Primary (#3B82F6) as the interaction signal.
  • Default to short, purposeful transitions (150–250ms) with stable easing.
  • Ensure hover, focus-visible, active, disabled, and loading states are explicit.

8. Voice & Brand

  • Tone should reflect the visual style: concise, confident, and product-specific.
  • Keep microcopy action-oriented and avoid generic filler language.
  • Preserve the style identity in headlines while keeping UI labels literal and clear.

9. Anti-patterns

  • Do not introduce off-palette colors when an existing token can solve the problem.
  • Do not flatten hierarchy by using the same type size/weight for all text.
  • Do not add decorative effects that reduce readability or accessibility.
  • Do not mix unrelated visual metaphors in the same interface.