product-planning(同步 26 改 65 新)
- 目录约定:docs/pm/<项目>/ ⇒ <工作区>/项目/<产品slug>/ 为产品根,下分 产品规划/ 与 产品原型/{designs,pages}
- ④段骨架六节 ⇒ 七节(新增「原型地址」;后两节改「页面导航」「原型状态取值」)
- ③段新增真机组件库;结案「源站只有暗色主题」,tokens.css(亮色)标为不可用于生产
- ③段改版规则反转为「一个产品只用一套原型、只留当前态」;②段新增 产品规划模板.md(表头唯一定义处)
- scripts:产品根定位重写(含 .registry/current-project 指针),新增 check_terms.py 与 selftest_product_root.py
session-mechanism(同步 3 改 2 新)
- references/06-技能优化规程.md 新增 §5「要求落在生成时看得见的面上」,总表 16 ⇒ 17 条;SKILL.md 同步
- scripts/collabctl.py 取回 _find_board() 候选定位(旧版写死 scripts/board.py,而看板已搬进 boards/会话看板/ ⇒ 旧版本就是坏的)
element-picker(新装)
- 按用户口径作「独立功能加入 product-planning」,非独立全局技能
- 修掉它自身三处路径漂移(技能根写法 ⇒ 同目录;README 两处旧落点;剪贴板示例文案与代码对齐)
工具归拢到技能级 assets/
- diagram-design / design-capture / element-picker / video-capture 从各段 assets/ 移到技能包 assets/
- 新增红线:本包有两处 assets/(技能级工具箱 vs 段内资产),引工具一律写「技能级 assets/<工具名>/」
- 路径口径由两类改三类(技能级工具箱 / 本段自带资产 / 同根技能)
不入库(磁盘保留)
- design-system-tiaoyue 整个目录(用户 2026-10-16 令):git rm -r --cached + .gitignore,理由=14 MB 且可 CDP 重采;
已在 ③段 SKILL.md 注明「取仓后这一层是空的属正常,用自带套需另取或重采」
- element-picker 的运行期存档 marks/(服务自己会建目录)
3.8 KiB
Terminal Window (CLI-chrome variant)
Optional full-page skin that wraps any diagram in a fake terminal window — titlebar with three dots, a $ prompt line, monospace type throughout. Use for dev-tool announcements, CLI-product posts, and technical social cards where a screenshot needs to read as "terminal," not "editorial doc."
This is a second, fixed skin — see style-guide.md § Terminal skin for the token table. It does not inherit from onboarding.md brand tokens and isn't part of the light/dark inversion rule; every terminal example uses the same nine tokens regardless of the host site's brand.
Grammar
<div class="terminal">
<div class="titlebar">
<div class="dot accent"></div>
<div class="dot"></div>
<div class="dot"></div>
<div class="titlebar-name">loop.sh — self-improving-loop</div>
</div>
<main class="frame">
<p class="prompt">
<span class="sign">$</span> diagram-design render --type loop
</p>
<h1># The self-improving loop</h1>
<svg>...</svg>
</main>
</div>
body {
background: var(--terminal-page);
}
.terminal {
background: var(--terminal-paper);
border: 1px solid var(--terminal-border);
border-radius: 12px;
}
.titlebar {
background: var(--terminal-bar);
border-bottom: 1px solid var(--terminal-border);
}
.dot {
background: var(--terminal-soft);
}
.dot.accent {
background: var(--terminal-accent);
}
Inside the SVG, swap the default light/dark tokens 1:1 for their terminal-* equivalents: paper → terminal-paper, ink → terminal-ink, muted/soft → terminal-muted/terminal-soft, accent/accent-tint → terminal-accent/terminal-accent-tint. The hub/focal-node pattern (inverted fill for the one highlighted element) still applies.
Typography
Everything is monospace — this is the one variant where that's correct. Drop Instrument Serif and Geist sans entirely; set the page title in mono, bold, prefixed with # (reads as a comment line). The eyebrow becomes a shell prompt: $ in terminal-accent, the command in terminal-muted.
Run every text role about 1–2px above the default type scale in style-guide.md (e.g. node-name 12px → 14px, sublabel/arrow-label 8–9px → 9–10px, hub label 16px → 18px). Monospace at the default sizes reads small next to the sans/serif mix it's replacing, and these cards are usually viewed at social-feed scale, not full-bleed.
Titlebar dots
Three 10px circles, macOS-style. The 1-accent rule caps the color use here too: one dot is terminal-accent, the other two are terminal-soft. Do not use a red/yellow/green traffic-light triad — that's a second and third hue, which the palette forbids.
Critical rules
- No pure black (
#000000) — useterminal-page(#0a0a0a) /terminal-paper(#141414). Same rule as the default skin, same reason: true black clips on OLED and in print. - One accent only. If a diagram needs a second focal element, use
terminal-ink(white) for emphasis via weight/size, not a second color. - Background dot-grid pattern (if used) stays
rgba(255,255,255,0.06–0.08)— barely visible texture, not a visual competitor to the titlebar chrome.
When to use
- Dev-tool / CLI-product launch posts (npm package, CLI flag, terminal-based workflow).
- Technical social cards where "this is a tool for engineers" is part of the message.
- Screenshots meant to pop in a dark-mode-heavy feed (X, Discord, dev blogs).
When not to use
- Editorial / long-form posts — pair with the default light or full-editorial variant instead.
- Brand-matched output from
onboarding.md— terminal is a fixed skin, not brand-tokenized. Don't try to reconcile the two. - Any diagram where the audience isn't developer-coded to read
$/#/titlebar-dots as chrome rather than content.