メニュー
Browser-based companion for showing mockups, diagrams, wireframes, and visual comparisons during design conversations. Uses chrome MCP tools. Falls back to text-only if unavailable. Use during brainstorming or any visual design work.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Post-implementation business assessment by Prometeo (PM). Verifies success metrics achievement, scope compliance, acceptance criteria business interpretation, risk materialization, and product decision closure. Outputs structured report with verdict and confidence score.
Analyzes checklist effectiveness by tracking hit rates, identifying stale items, and finding coverage gaps. Generates evolution suggestions following Boorman's principles. Use periodically to keep checklists field-tested and relevant.
Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Use periodically or before releases to maintain code hygiene.
Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.
Generates test cases for a module or function following FIRST principles and Arrange-Act-Assert pattern. Detects test framework from project config. Use to bootstrap test coverage for existing code or as the Red phase of TDD.
Create and manage git worktrees for isolated feature work. Use when starting implementation that should not touch the main workspace, or for parallel development. Handles creation, baseline verification, and cleanup.
| name | visual-companion |
| description | Browser-based companion for showing mockups, diagrams, wireframes, and visual comparisons during design conversations. Uses chrome MCP tools. Falls back to text-only if unavailable. Use during brainstorming or any visual design work. |
A browser-based tool for visual design work during: $ARGUMENTS
Before offering the companion, check if browser tools are available:
mcp__claude-in-chrome__* tools are accessible: companion is availableOffer once per session, in its own message (no other content):
Some of what we're working on might be easier to explain if I can show it to you in a web browser. I can put together mockups, diagrams, comparisons, and other visuals as we go. Want to try it?
Wait for response. If declined, proceed text-only.
Even after acceptance, decide FOR EACH QUESTION whether to use browser or terminal:
Use the browser when the user would understand better by SEEING it:
Use the terminal when the content is fundamentally TEXT:
A question about a UI topic is not automatically visual. "What does personality mean here?" is terminal. "Which layout works better?" is browser.
When rendering in the browser:
mcp__claude-in-chrome__tabs_create_mcpmcp__claude-in-chrome__navigate to load an HTML data URI or local file