spec-polish ​

启动 dev server，在浏览器中查看功能，用截图和交互证据迭代 UI polish。

ASCII 链路图 ​

text
Codebase -> Spec -> Plan -> Tasks -> Code -> Review -> Knowledge
  |
  v
  spec-polish
  entry: spec-polish
  type: workflow command

基本信息 ​

字段内容
Skillspec-polish
类型workflow command
研发链路位置Code
当前入口spec-polish
兼容别名/spec:polish、$spec-polish
Sourceskills/spec-polish/SKILL.md
Governancesrc/cli/contracts/dual-host-governance/skills-governance.json（supported-host skills governance）

描述 ​

Start the dev server, inspect the feature in browser, and iterate on polish.

Source 契约摘要 ​

When To Use ​

Use when a feature or branch is ready for hands-on browser polish: start its dev server, inspect the feature in browser, and make iterative UI/UX fixes from direct feedback.

When Not To Use ​

Do not use for initial requirements, implementation planning, non-browser backend work, static code review, broad visual audits, or MCP setup/repair beyond the browser helper handoff.

Inputs ​

A PR number, branch name, or current branch; project dev-server conventions; feature URL/route when known; user feedback from browser inspection.

Outputs ​

Running local dev server URL, browser handoff, authorized scoped polish edits, verification notes, and an explicit commit status.

Artifacts ​

Authorized source edits in the user's project, dev-server log in temp space, optional browser screenshots/inspection notes, and a final commit only when separately authorized.

Failure Modes ​

Wrong branch, main/master branch, missing branch-mutation authority, missing dev-server command, unresolved port, server startup failure, browser helper unavailable, or user feedback requiring upstream product/design decisions.

Workflow ​

Select the branch, start the dev server, resolve the browser handoff, iterate on user-reported polish issues, and stop when the user says the loop is complete.

Downstream Consumers ​

The user reviewing the browser result, spec-work for deeper implementation follow-up, and release/review workflows that consume the final branch changes.

何时使用 ​

  • 页面可运行但视觉、布局或交互需要打磨。
  • 需要桌面和移动视口验证。
  • 用户明确要浏览器可见 UI polish。

工作步骤 ​

  • 读取 plan、task pack、bug report 或明确实现目标。
  • 建立小步任务列表，按现有代码模式做最小必要修改。
  • 运行聚焦验证、测试、构建、浏览器或平台检查。
  • 把 diff、验证结果和剩余风险交给 review 或 knowledge 阶段。

输出 ​

  • 实现 diff、测试结果、构建输出、浏览器截图或运行证据。
  • 必要时输出 blocked 原因，而不是扩大 scope。

Agent 调度 ​

  • 小任务通常 inline；大任务可按文件边界使用 serial 或 parallel workers。
  • 调试、优化、UI、平台专项可引入对应 specialist agents，但 orchestrator 负责最终集成。

本 skill 当前没有 skill-local references/agents 或 references/personas 文件；默认由 orchestrator 直接完成，或按阶段需要临时调用其他 skill 的专家。

边界 ​

  • 不能只凭代码判断视觉质量，必须看浏览器证据。
  • 聚焦 UI 打磨，不承担实现规划或代码 review。

源码校准 ​

  • 本页由 website/scripts/generate-skill-detail-pages.js 从上游 source skill 生成。
  • 当前入口、兼容别名与宿主投递 metadata 来自 src/cli/contracts/dual-host-governance/skills-governance.json。
  • 当 source skill 或 governance contract 变化后，应重新运行 npm run reference:pages 并执行 npm run content:audit。