④段整套同步（六节＋ 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
1 parent fa0a9026c8
commit 5afeb6b78a
@@ -0,0 +1,124 @@
+---
+name: saas-landing
+description: |
+  Single-page SaaS landing with hero, features, social proof, pricing, and CTA.
+  Respects the active DESIGN.md color/typography/layout tokens.
+  Trigger keywords: "saas landing", "marketing page", "product landing".
+triggers:
+  - "saas landing"
+  - "marketing page"
+  - "product landing"
+od:
+  mode: prototype
+  platform: desktop
+  scenario: marketing
+  preview:
+    type: html
+    entry: index.html
+    reload: debounce-100
+  design_system:
+    requires: true
+    sections: [color, typography, layout, components]
+  craft:
+    requires: [typography, color, anti-ai-slop, laws-of-ux]
+  inputs:
+    - name: product_name
+      type: string
+      required: true
+    - name: tagline
+      type: string
+      required: true
+    - name: has_pricing
+      type: boolean
+      default: true
+    - name: proof_count
+      type: integer
+      default: 3
+      min: 0
+      max: 6
+  parameters:
+    - name: hero_density
+      type: spacing
+      default: 96
+      range: [48, 200]
+    - name: accent_strength
+      type: opacity
+      default: 1.0
+      range: [0.5, 1.0]
+  outputs:
+    primary: index.html
+  capabilities_required:
+    - file_write
+---
+
+# SaaS Landing Skill
+
+Produce a single-page SaaS landing. Agent, follow this workflow exactly.
+
+## 1. Read context
+
+Before writing anything:
+- Read `DESIGN.md` in the current working directory. If missing, stop and ask for one.
+- Identify the color palette, typography tokens, and layout principles.
+- Note the "Agent Prompt Guide" section — it overrides any instruction here if they conflict.
+
+## 2. Plan sections
+
+Required sections, in order:
+1. **Hero** — logo-or-wordmark, headline (tagline input), subhead (1–2 sentences), primary CTA, secondary CTA. Use the hero_density parameter as vertical padding in px.
+2. **Features** — 3–6 feature tiles. Each: icon, short title, 1–2 sentence body.
+3. **Social proof** — `proof_count` logos or testimonials. If 0, skip this section.
+4. **Pricing** — 2–3 tiers. Include only if `has_pricing` is true.
+5. **Footer CTA** — large accent-colored band with one-button call to action.
+6. **Footer** — minimal: links + copyright.
+
+## 3. Apply design system
+
+- All colors must come from DESIGN.md tokens. Do not invent hex values.
+- Typography: use the declared display font for headlines, body font for everything else.
+- Layout: respect the grid, max-width, and section spacing rules.
+- Components: use declared button/card/input patterns. Do not add shadows if DESIGN.md's Depth & Elevation says minimal.
+- Accent: use the accent color only once in the hero, once in the footer CTA, and for all links. Do not flood the page.
+
+## 4. Write the file
+
+Output a single self-contained `index.html` with:
+- All CSS inlined in a `<style>` block in `<head>`.
+- System font fallbacks if DESIGN.md fonts aren't loadable from Google Fonts etc.
+- No external JS.
+- Semantic HTML (`<header>`, `<main>`, `<section>`, `<footer>`).
+- Each editable element tagged with `data-od-id="<unique-slug>"` so the host app's comment mode can target it.
+
+## 5. Self-check
+
+Before finishing, verify:
+- [ ] All text is content-meaningful, not lorem ipsum (use product_name and tagline inputs; generate plausible specific copy for the rest).
+- [ ] No broken color references (every CSS color value is in DESIGN.md's palette or a valid alpha/fallback variant).
+- [ ] Responsive breakpoints match DESIGN.md's Responsive Behavior section.
+- [ ] The page looks good at 1440w, 768w, and 375w (mentally simulate).
+- [ ] Accent used no more than twice total.
+
+## 6. Done
+
+Write only `index.html`. Do not generate a separate CSS file, JS file, or README.
+
+---
+
+## For skill authors reading this as a reference
+
+This is a minimal but complete skill. Structure:
+
+```
+saas-landing-skill/
+├── SKILL.md    ← you are here
+└── assets/
+    └── base.html    (optional starter template; this skill doesn't use one)
+```
+
+Things to notice:
+- The `od:` front-matter block is optional for Claude-Code-only compatibility, but adding it lights up OD's typed inputs, sliders, preview metadata, and capability gating.
+- The workflow below the front-matter is plain Markdown that the agent reads as its system prompt.
+- DESIGN.md is treated as a collaborator, not an override. The skill gives the agent authority to override when the brief conflicts, but never to invent new tokens.
+- `data-od-id` tagging is how we wire elements to comment mode. Skills that want comment-mode compatibility must annotate their output.
+
+See [`../../docs/skills-protocol.md`](../../docs/skills-protocol.md) for the full protocol.