@mstar-harness/opencode 0.6.13 → 0.6.15

package/harness-skills/mstar-design-md/templates/DESIGN.md.template

@@ -0,0 +1,273 @@
+<!-- COMPLETENESS_LEVEL: 1 — last audited [DATE] -->
+
+# [Design System Name]
+
+## Overview
+
+[Design System Name] is a [adjective, e.g., minimal, playful, bold] design system for [project/product name].
+[Aesthetic principles — one sentence describing the visual identity: e.g., "Prioritize readability and clarity with plenty of whitespace and restrained color."]
+
+This is the Light theme.
+<!-- LEVEL2_PLACEHOLDER: When ready for dark theme, create DESIGN.dark.md with same token names and different values. See references/completeness-checklist.md § Level 3. -->
+<!-- Uncomment when dark theme exists: The Dark theme uses the same token names with different values and lives at /DESIGN.dark.md. -->
+
+## Colors
+
+### Background
+
+<!-- Level 1 — Fill in at least background-100. Level 2 adds background-200 and background-300. -->
+
+| Token | Value |
+|-------|-------|
+| background-100 | #[primary page/card surface] |
+
+<!-- LEVEL2_PLACEHOLDER: Add background-200 and background-300 for subtle surface separation. See references/completeness-checklist.md § Level 2/Colors. -->
+<!--
+| background-200 | #[secondary surface] |
+| background-300 | #[active surface] |
+-->
+
+### Gray (text and fills)
+
+<!-- Level 1 — Fill in at least gray-1000 (primary text) and gray-900 (secondary text). -->
+
+| Token | Value |
+|-------|-------|
+| gray-1000 | #[primary text] |
+| gray-900 | #[secondary text] |
+
+<!-- LEVEL2_PLACEHOLDER: Complete the full 10-step scale (gray-100 through gray-1000). See references/design-md-spec.md § Colors. -->
+<!--
+| gray-100 | #[lightest fill] |
+| gray-200 | #[hover fill] |
+| gray-300 | #[active fill] |
+| gray-400 | #[border] |
+| gray-500 | #[hover border] |
+| gray-600 | #[active border] |
+| gray-700 | #[solid fill / disabled text] |
+| gray-800 | #[solid hover] |
+| gray-900 | #[secondary text] |
+| gray-1000 | #[primary text] |
+-->
+
+<!-- LEVEL2_PLACEHOLDER: Add gray-alpha scale for translucent borders, overlays, and hover states. See references/design-md-spec.md § Colors. -->
+<!--
+### Gray Alpha (translucent overlays)
+
+| Token | Value |
+|-------|-------|
+| gray-alpha-100 | rgba(0, 0, 0, 0.04) |
+| gray-alpha-200 | rgba(0, 0, 0, 0.06) |
+| gray-alpha-300 | rgba(0, 0, 0, 0.08) |
+| gray-alpha-400 | rgba(0, 0, 0, 0.12) |
+| gray-alpha-500 | rgba(0, 0, 0, 0.16) |
+| gray-alpha-600 | rgba(0, 0, 0, 0.24) |
+-->
+
+### Accent
+
+<!-- Level 1 — Fill in at least one accent (blue or brand color) for links/actions, plus red for errors and amber for warnings. -->
+
+| Token | Value | Usage |
+|-------|-------|-------|
+| blue-700 | #[links, focus, primary actions] | Interactive elements |
+| red-700 | #[errors, destructive actions] | Errors, delete buttons |
+| amber-700 | #[warnings, alerts] | Warning states |
+
+<!-- LEVEL2_PLACEHOLDER: Complete all accent scales (blue, red, amber, green, teal, purple, pink). Add at minimum 700/800/900/1000 steps per scale. See references/completeness-checklist.md § Level 2/Colors. -->
+<!--
+| green | Success states |
+| teal | Info, secondary brand |
+| purple | Special emphasis |
+| pink | Highlights, badges |
+-->
+
+## Typography
+
+<!-- Level 1 — Fill in at least one body token (copy-*) and one heading token (heading-*). -->
+<!-- Token naming: {role}-{size}. Roles: heading, label, copy, button. Size: approximate font size in px. -->
+
+### Body text
+
+| Token | Font Family | Size | Weight | Line Height | Letter Spacing |
+|-------|------------|------|--------|-------------|----------------|
+| copy-16 | [font-family] | 16px | 400 | 1.6 | 0 |
+
+### Headings
+
+| Token | Font Family | Size | Weight | Line Height | Letter Spacing |
+|-------|------------|------|--------|-------------|----------------|
+| heading-32 | [font-family] | 32px | 600 | 1.2 | -0.02em |
+
+<!-- LEVEL2_PLACEHOLDER: Complete the typography scale. Add at least 3 heading levels, 1 label token, and 1 button typography token. See references/completeness-checklist.md § Level 2/Typography. -->
+<!--
+### Labels (single-line, scannable)
+
+| Token | Font Family | Size | Weight | Line Height | Letter Spacing |
+|-------|------------|------|--------|-------------|----------------|
+| label-14 | [font-family] | 14px | 500 | 1.3 | 0 |
+
+### Buttons
+
+| Token | Font Family | Size | Weight | Line Height | Letter Spacing |
+|-------|------------|------|--------|-------------|----------------|
+| button-14 | [font-family] | 14px | 500 | 1.3 | 0 |
+
+### Additional headings
+| heading-24 | [font-family] | 24px | 600 | 1.3 | -0.01em |
+| heading-20 | [font-family] | 20px | 600 | 1.3 | 0 |
+-->
+
+## Spacing & Layout
+
+### Spacing scale
+
+<!-- Level 1 — Declare base unit and at least 5 scale steps. Base unit is typically 4px or 8px. -->
+
+Base unit: [4px or 8px]
+
+| Step | Value |
+|------|-------|
+| 1x | [base × 1] |
+| 2x | [base × 2] |
+| 3x | [base × 3] |
+| 4x | [base × 4] |
+| 6x | [base × 6] |
+
+<!-- LEVEL2_PLACEHOLDER: Complete the full 9-step scale and add three-step rhythm rules. See references/design-md-spec.md § Spacing & Layout. -->
+<!--
+| 8x | [base × 8] |
+| 10x | [base × 10] |
+| 16x | [base × 16] |
+| 24x | [base × 24] |
+
+### Rhythm
+
+- [small]: inside a group (label + input, icon + text)
+- [medium]: between related groups
+- [large]: between sections
+-->
+
+### Breakpoints
+
+<!-- Level 1 — At least 2 breakpoints for responsive layout. -->
+
+| Name | Min Width | Target |
+|------|-----------|--------|
+| sm | 401px | Mobile landscape |
+| lg | 961px | Desktop |
+
+<!-- LEVEL2_PLACEHOLDER: Add intermediate breakpoints (md, xl, 2xl). See references/completeness-checklist.md § Level 2/Breakpoints. -->
+<!--
+| md | 601px | Tablet |
+| xl | 1200px | Large desktop |
+| 2xl | 1400px | Ultra-wide |
+-->
+
+<!-- LEVEL2_PLACEHOLDER: Add Components section — at minimum Button (primary, secondary) and Input tokens with size variants and all states. See references/design-md-spec.md § Components. -->
+<!--
+## Components
+
+### Button
+
+| Variant | Background | Text | Border | Radius | Height |
+|---------|-----------|------|--------|--------|--------|
+| primary | gray-1000 | background-100 | — | 6px | 40px |
+| secondary | background-100 | gray-1000 | gray-alpha-400 | 6px | 40px |
+
+**Size variants:**
+| Size | Height | Typography |
+|------|--------|------------|
+| small | 32px | button-12 |
+| default | 40px | button-14 |
+| large | 48px | button-16 |
+
+**States:** Fill steps up: 100→200 (hover), 100→300 (active). Border steps up: 400→500→600. Disabled: gray-100 fill, gray-700 text, not-allowed cursor. Focus: 0 0 0 2px background-100, 0 0 0 4px blue-700.
+
+### Input
+
+| Variant | Background | Text | Border | Radius | Height |
+|---------|-----------|------|--------|--------|--------|
+| default | background-100 | gray-1000 | gray-alpha-400 | 6px | 40px |
+
+**Size variants:** Same as Button (32px/40px/48px).
+
+**States:** Same state progression as Button. Error: border red-700, add error message below.
+-->
+
+<!-- LEVEL3_PLACEHOLDER: Add Elevation & Depth, Motion, Shapes, Voice & Content, and full Component library. See references/completeness-checklist.md § Level 3. -->
+<!--
+## Elevation & Depth
+
+Hierarchy comes from tonal surfaces and borders first; shadows stay subtle.
+
+### Shadows (light theme)
+
+| Element | Value |
+|---------|-------|
+| Card | 0 2px 2px rgba(0, 0, 0, 0.04) |
+| Popover | 0 1px 1px rgba(0, 0, 0, 0.02), 0 4px 8px -4px rgba(0, 0, 0, 0.04), 0 16px 24px -8px rgba(0, 0, 0, 0.06) |
+| Modal | 0 1px 1px rgba(0, 0, 0, 0.02), 0 8px 16px -4px rgba(0, 0, 0, 0.04), 0 24px 32px -8px rgba(0, 0, 0, 0.06) |
+
+Pair each elevation with the matching radius below.
+
+## Motion
+
+Motion clarifies change, never decorates. Default 0ms is often the best choice.
+
+### Easing
+
+Default: cubic-bezier(0.175, 0.885, 0.32, 1.1)
+
+### Durations
+
+| Context | Duration |
+|---------|----------|
+| State change | 150ms |
+| Popover/Tooltip | 200ms |
+| Modal/Overlay | 300ms |
+
+Honor prefers-reduced-motion: drop nonessential motion.
+
+## Shapes
+
+### Border Radius
+
+| Context | Value |
+|---------|-------|
+| Surface, Input, Button | 6px |
+| Menu, Modal, Popover | 12px |
+| Fullscreen | 16px |
+| Pill, Avatar | 9999px |
+
+Keep one radius family per view; never mix rounded and sharp corners.
+
+## Components — Extended
+
+Add Card, Modal, Tooltip, Menu/Dropdown, Badge tokens following the same pattern as Button/Input.
+
+## Voice & Content
+
+- Use Title Case for labels, buttons, titles, and tabs
+- Sentence case for body, helper text, and toasts
+- Name actions with a verb and a noun: [Create Project], [Delete Item]
+- Write errors as what happened + what to do: [Error description. Suggested fix.]
+- Toasts name the specific thing, no trailing period, no "successfully": [Item deleted]
+- Empty states point to the first action: [No items yet. Create one to get started.]
+- In-progress states: present participle + ellipsis: [Saving…], [Loading…]
+- Use numerals, curly quotes, the ellipsis character
+- Skip "please" and marketing superlatives
+-->
+
+## Do's and Don'ts
+
+<!-- Fill in with rules specific to this design system. Examples to customize: -->
+
+- Use [gray-1000] for primary text, [gray-900] for secondary.
+- Keep accent color for state and the single most important action on a view.
+- Hold WCAG AA contrast (4.5:1 for body text).
+- Show focus ring on every interactive element at :focus-visible.
+- Apply typography tokens instead of setting font properties by hand.
+- Don't signal state with color alone; pair it with an icon or text label.
+- Don't use more than two font weights in one view.
+- Don't mix rounded and sharp corners in one view.

package/harness-skills/mstar-harness-core/SKILL.md

@@ -31,8 +31,8 @@ description: Morning Star (启明星) harness **强制全局入口** —— 信
 | 角色 | 始终 | 按任务追加（典型） |
 |------|------|-------------------|
 | **全部** | 本 skill | — |
-| **`@project-manager`** | 本 skill | `mstar-dispatch-gates`、`mstar-phase-gates`、`mstar-plan-conventions`、`mstar-superpowers-align`、`mstar-roles`；派 QC 前 `mstar-review-qc`；并行/审查 `mstar-branch-worktree`；plan/status/reports `mstar-plan-artifacts`。**不**读 `mstar-coding-behavior` |
-| **实现/审查/QA/运维** | 本 skill + `mstar-coding-behavior` + 角色 ref | 有 git 写：`mstar-branch-worktree`；有 plan 路径：`mstar-plan-conventions`（路径符号节）；QC/QA：`mstar-review-qc`；改 status/residual：`mstar-plan-artifacts` |
+| **`@project-manager`** | 本 skill | `mstar-dispatch-gates`、`mstar-phase-gates`、`mstar-plan-conventions`、`mstar-superpowers-align`、`mstar-roles`；派 QC 前 `mstar-review-qc`；并行/审查 `mstar-branch-worktree`；plan/status/reports `mstar-plan-artifacts`；UI 类 plan Prepare 阶段 `mstar-design-md`（DESIGN.md 门禁）。**不**读 `mstar-coding-behavior` |
+| **实现/审查/QA/运维** | 本 skill + `mstar-coding-behavior` + 角色 ref | 有 git 写：`mstar-branch-worktree`；有 plan 路径：`mstar-plan-conventions`（路径符号节）；QC/QA：`mstar-review-qc`；改 status/residual：`mstar-plan-artifacts`；UI 任务：`mstar-design-md`（读取 DESIGN.md tokens） |
 | **leaf 承接方** | 上栏 + **`mstar-dispatch-gates`**（反递归节） | — |
 
 Routing eval（Cursor 维护）→ `.cursor/skills/mstar-routing-eval/`，**非**运行时必读。
@@ -83,6 +83,7 @@ PM 在 Assignment 写 **`Task category`**（主类 + 可选 `secondary`）：
 | `mstar-branch-worktree` | 功能分支、worktree、QC/QA 检出对齐 |
 | `mstar-plan-conventions` | `{HARNESS_DIR}` 发现、初始化、Spec 分支模型摘要 |
 | `mstar-plan-artifacts` | 主 plan、reports、`status.json`、residual、knowledge、Done 归档 |
+| `mstar-design-md` | DESIGN.md 设计系统规范 —— 创建/审计/维护 design tokens，三级检查清单，light/dark 双主题 |
 | `mstar-review-qc` | QC 工作流、模板、verdict、residual 留档 |
 | `mstar-coding-behavior` | Think / Simplicity / Surgical / Goal-Driven |
 | `mstar-superpowers-align` | Superpowers × harness 优先级与短语 |

package/harness-skills/mstar-phase-gates/SKILL.md

@@ -111,11 +111,12 @@ description: Morning Star (启明星) Spec-Driven 双阶段门禁 —— Prepare
 2. `clarify` 是否完成（高影响歧义是否收敛）？
 3. 意图门禁是否满足（真实目标 / 成功判据 / 非目标已写明）？
 4. `plan` 是否完成并可引用？
-5. 若分批/暂缓/临时绕行，roadmap 是否落在 plan/status 中，而不是只在对话里？
-6. `tasks` 是否完成？
-7. Assignment 是否含 **`Task category`**（实现类任务）并与 Owner 一致？
-8. 若中途出现 plan drift，是否先回写再继续？
-9. 实现说明中是否体现"最小耐久切片 + 手术式改动 + 可验证检查"？
+5. 若 plan 涉及 UI 工作：`DESIGN.md` 是否存在且满足声明的 completeness level（见 `mstar-design-md`）？
+6. 若分批/暂缓/临时绕行，roadmap 是否落在 plan/status 中，而不是只在对话里？
+7. `tasks` 是否完成？
+8. Assignment 是否含 **`Task category`**（实现类任务）并与 Owner 一致？
+9. 若中途出现 plan drift，是否先回写再继续？
+10. 实现说明中是否体现"最小耐久切片 + 手术式改动 + 可验证检查"？
 
 任一项为「否」时，`Gate decision` 必须是 `blocked`。
 

package/harness-skills/mstar-roles/SKILL.md

@@ -45,6 +45,7 @@ Treat these as baseline dependencies **where the role touches implementation, re
 | `mstar-branch-worktree` | Git write, parallel worktrees, QC/QA checkout fields |
 | `mstar-plan-conventions` | `{HARNESS_DIR}` discovery, init, Spec branch naming, `writing-plans` path |
 | `mstar-plan-artifacts` | Main plan, `reports/`, `status.json`, residual, knowledge/iteration, Done compaction |
+| `mstar-design-md` | DESIGN.md design system spec — create/audit/maintain tokens, completeness checklist, light/dark dual-theme |
 | `mstar-review-qc` | QC workflow, template, verdict, high-risk checks |
 | `mstar-coding-behavior` | Implementation/debug/refactor (**not** PM orchestration-only) |
 | `mstar-superpowers-align` | Superpowers plugin on; Assignment `Superpowers` lines |
@@ -55,10 +56,10 @@ Treat these as baseline dependencies **where the role touches implementation, re
 | Role | Typical adds |
 | --- | --- |
 | `project-manager` | `mstar-dispatch-gates`, `mstar-phase-gates`, `mstar-plan-conventions`, `mstar-superpowers-align`, `mstar-roles` ref; + `mstar-review-qc` before QC; + `mstar-branch-worktree` / `mstar-plan-artifacts` as the round requires |
-| `fullstack-dev*`, `frontend-dev` | `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (if repo writes); plan path symbols from `mstar-plan-conventions` (minimal) |
-| `qc-specialist*` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (report paths) |
-| `qa-engineer` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (closing R#) |
-| `architect`, `product-manager` | `mstar-phase-gates` (Prepare), `mstar-plan-artifacts` (knowledge/specs) |
+| `fullstack-dev*`, `frontend-dev` | `mstar-coding-behavior`, `mstar-dispatch-gates`, `mstar-branch-worktree` (if repo writes); plan path symbols from `mstar-plan-conventions` (minimal); `mstar-design-md` when implementing styled UI |
+| `qc-specialist*` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (report paths); `mstar-design-md` when reviewing UI |
+| `qa-engineer` | `mstar-review-qc`, `mstar-branch-worktree`, `mstar-plan-artifacts` (closing R#); `mstar-design-md` when verifying visual output |
+| `architect`, `product-manager` | `mstar-phase-gates` (Prepare), `mstar-plan-artifacts` (knowledge/specs); `mstar-design-md` (creator + design intent) |
 | `ops-engineer` | `mstar-coding-behavior`, `mstar-branch-worktree` |
 | `prompt-engineer` | All topic skills when editing harness text |
 

package/harness-skills/mstar-roles/references/architect.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare: specify/clarify/plan), `mstar-plan-conventions` (`{PLAN_DIR}`, `writing-plans` path).
 
-**Typically:** `mstar-plan-artifacts` (knowledge/specs/ADR placement); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-artifacts` (knowledge/specs/ADR placement); `mstar-design-md` (DESIGN.md design system spec — architect is primary creator); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
 
 **On demand:** `mstar-branch-worktree` (when committing architecture docs to the business repo).
 
@@ -52,7 +52,8 @@ Use as applicable:
 2. Module boundaries and interface contracts
 3. Technical decision records (ADR-style)
 4. Risk/rollback strategy and validation plan
-5. Architecture-spec documentation in repository paths assigned by PM
+5. DESIGN.md creation and maintenance — design token selection, naming, completeness level decisions (see `mstar-design-md`)
+6. Architecture-spec documentation in repository paths assigned by PM
 
 ## Scope Boundaries
 

package/harness-skills/mstar-roles/references/frontend-dev.md

@@ -6,7 +6,7 @@
 
 **Typically:** `mstar-plan-conventions` (paths + spec metadata); `mstar-superpowers-align` (when plugin on).
 
-**On demand:** `mstar-branch-worktree` (repo writes); `mstar-phase-gates` (Execute / hotfix when referenced in assignment).
+**On demand:** `mstar-branch-worktree` (repo writes); `mstar-phase-gates` (Execute / hotfix when referenced in assignment); `mstar-design-md` (when implementing styled UI — read DESIGN.md for tokens before writing components).
 
 **Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 
@@ -35,7 +35,7 @@ If any item below matches, **stop** and return `Blocked` to `project-manager` in
 ## Core Responsibilities
 
 1. Implement pages/components/interactions with maintainable frontend architecture
-2. Maintain component consistency and design-system alignment
+2. Maintain component consistency and DESIGN.md alignment — read design tokens before writing styled components
 3. Ensure accessibility and frontend performance quality
 4. Add or update frontend tests where assigned
 

package/harness-skills/mstar-roles/references/fullstack-dev-shared.md

@@ -16,7 +16,7 @@ Behavior is shared; track identity is parameterized.
 
 **Typically:** `mstar-plan-conventions` (path symbols + `metadata.primary_spec` / `spec_refs`); `mstar-superpowers-align` (when plugin on).
 
-**On demand:** `mstar-branch-worktree` (repo writes, `Working branch`); `mstar-phase-gates` (Execute / hotfix sections when gate fields are in the assignment).
+**On demand:** `mstar-branch-worktree` (repo writes, `Working branch`); `mstar-phase-gates` (Execute / hotfix sections when gate fields are in the assignment); `mstar-design-md` (when task includes UI implementation — read DESIGN.md for design tokens).
 
 **Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 

package/harness-skills/mstar-roles/references/product-manager.md

@@ -4,7 +4,7 @@
 
 **Always:** `mstar-harness-core`, `mstar-dispatch-gates`, `mstar-phase-gates` (Prepare / clarify), `mstar-plan-conventions` (`{PLAN_DIR}`, `writing-plans` path).
 
-**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
+**Typically:** `mstar-plan-artifacts` (specs, knowledge index); `mstar-design-md` (DESIGN.md design intent and requirements for UI planning); `mstar-coding-behavior` (surgical doc edits); `mstar-superpowers-align` (when plugin on).
 
 **On demand:** `mstar-branch-worktree` (when committing product docs to the business repo).
 

package/harness-skills/mstar-roles/references/qa-engineer.md

@@ -6,7 +6,7 @@
 
 **Typically:** `mstar-plan-conventions` (paths); `mstar-superpowers-align` (when plugin on).
 
-**On demand:** `mstar-plan-artifacts` (closing R# after verified fix); `mstar-phase-gates` (gate checklist when assignment references verification phase).
+**On demand:** `mstar-plan-artifacts` (closing R# after verified fix); `mstar-phase-gates` (gate checklist when assignment references verification phase); `mstar-design-md` (when verifying UI — check visual output against DESIGN.md).
 
 **Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 

package/harness-skills/mstar-roles/references/qc-specialist-shared.md

@@ -18,7 +18,7 @@ Behavior is shared; reviewer identity is parameterized.
 
 **Typically:** `mstar-plan-conventions` (path symbols only).
 
-**On demand:** `mstar-plan-artifacts` (when PM asks you to cite severity enum for residual registration — QC does not own `status.json` writes).
+**On demand:** `mstar-plan-artifacts` (when PM asks you to cite severity enum for residual registration — QC does not own `status.json` writes); `mstar-design-md` (when reviewing UI — verify implementation aligns with DESIGN.md tokens).
 
 **Host:** `mstar-host` (detect; `references/opencode.md` | `cursor.md` | `codex.md`).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mstar-harness/opencode",
-  "version": "0.6.13",
+  "version": "0.6.15",
   "description": "Morning Star harness OpenCode plugin (skills bootstrap and agent loading).",
   "license": "MIT",
   "repository": {
@@ -14,6 +14,7 @@
     "dist",
     "harness-skills",
     "harness-agents",
+    "harness-commands",
     "AGENTS.md",
     "INSTALL.md"
   ],