菜单
Invoke explicitly with `$ui-flow` for UI changes under `/hyperopen/src/hyperopen/views/**`, `/hyperopen/src/styles/**`, or interaction flows that need governed browser QA, design validation, and implementation review. Do not use for backend-only work or non-visual refactors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when acting as `acceptance_test_writer` to propose happy-path acceptance and integration coverage from an approved spec or ExecPlan. Do not use to materialize tests directly or to edit production code.
Invoke explicitly with `$bug-flow` for unclear bugs, regressions, or failure investigations that need structured diagnosis, regression tests, the smallest fix, and findings-first review. Do not use for obvious one-line fixes or planned feature work.
Use when acting as `edge_case_test_writer` to propose adversarial, boundary, and invariant coverage that complements acceptance coverage. Do not use to materialize tests or edit production code.
Invoke explicitly with `$feature-flow` for complex features, significant refactors, or multi-file behavior changes that need an ExecPlan, proposed test coverage, RED-phase failing tests, implementation, and review. Do not use for tiny fixes, doc-only work, or purely local cleanup.
Use when acting as `spec_writer` to create or refresh the active ExecPlan, clarify scope, and record acceptance criteria for a multi-agent ticket. Do not use for production-code edits or standalone prose cleanup.
Use Browser MCP for exploratory browser debugging, live-session inspection, parity compare, design review, and selector or flow discovery before converting stable paths into Playwright.
| name | ui-flow |
| description | Invoke explicitly with `$ui-flow` for UI changes under `/hyperopen/src/hyperopen/views/**`, `/hyperopen/src/styles/**`, or interaction flows that need governed browser QA, design validation, and implementation review. Do not use for backend-only work or non-visual refactors. |
Use this skill explicitly for UI-facing tasks where design evidence and browser QA are part of completion.
/hyperopen/AGENTS.md/hyperopen/docs/FRONTEND.md/hyperopen/docs/agent-guides/browser-qa.md/hyperopen/docs/agent-guides/ui-foundations.md/hyperopen/docs/agent-guides/trading-ui-policy.md/hyperopen/docs/MULTI_AGENT.mdbrowser_debugger when the current live behavior, screenshots, DOM state, or browser-only issues need to be established.ui_designer before implementation and capture the chosen approach in the active ExecPlan when the work is complex.tdd_test_writer for the RED phase before implementation. If not, carry a precise manual validation plan forward.worker to implement the approved UI change while preserving the established runtime and interaction rules.ui_visual_validator and reviewer before signoff. Use browser_debugger for the governed PASS / FAIL / BLOCKED browser-QA record.375, 768, 1280, and 1440, plus changed files, commands run, validation results, and residual risks or blind spots.name values.