菜单
[BETA] Start the dev server, open the feature in a browser, and iterate on improvements together.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Explore requirements and approaches through collaborative dialogue before writing a right-sized requirements document and planning implementation. Use for feature ideas, problem framing, when the user says 'let's brainstorm', or when they want to think through options before deciding what to build. Also use when a user describes a vague or ambitious feature request, asks 'what should we build', 'help me think through X', presents a problem with multiple valid solutions, or seems unsure about scope or direction — even if they don't explicitly ask to brainstorm.
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Also use when the user says "update the PR description", "refresh the PR description", "freshen the PR", or wants to rewrite an existing PR description. Produces PR descriptions that scale in depth with the complexity of the change, avoiding cookie-cutter templates.
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Refresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.
Document a recently solved problem to compound your team's knowledge
| name | ce-polish-beta |
| description | [BETA] Start the dev server, open the feature in a browser, and iterate on improvements together. |
| disable-model-invocation | true |
| argument-hint | [PR number, branch name, or blank for current branch] |
Start the dev server, open the feature in a browser, and iterate. You use the feature, say what feels off, and fixes happen.
.opencode/launch.jsonRun bash scripts/read-launch-json.sh. If it finds a configuration, use it — the user already told us how to start the project.
Run bash scripts/detect-project-type.sh to identify the framework.
Route by type to the matching recipe reference for start command and port defaults:
| Type | Recipe |
|---|---|
rails | references/dev-server-rails.md |
next | references/dev-server-next.md |
vite | references/dev-server-vite.md |
nuxt | references/dev-server-nuxt.md |
astro | references/dev-server-astro.md |
remix | references/dev-server-remix.md |
sveltekit | references/dev-server-sveltekit.md |
procfile | references/dev-server-procfile.md |
unknown | Ask the user how to start the project |
For framework types that need a package manager, run bash scripts/resolve-package-manager.sh and substitute the result into the start command.
Resolve the port with bash scripts/resolve-port.sh --type <type>.
Start the dev server in the background, log output to a temp file. Probe http://localhost:<port> for up to 30 seconds. If it doesn't come up, show the last 20 lines of the log and ask the user what to do.
Load references/ide-detection.md for the env-var probe table. Open the browser using the IDE's mechanism (Claude Code → open, Cursor → Cursor browser, VS Code → Simple Browser).
Tell the user:
Dev server running on http://localhost:<port>
Browse the feature and tell me what could be better.
This is the core loop. The user browses the feature and tells you what to improve. You fix it. Repeat until they're happy.
agent-browser to screenshot or inspect the pageNo checklist. No envelope. Just conversation.
Reference files (loaded on demand):
references/launch-json-schema.md — launch.json schema + per-framework stubsreferences/ide-detection.md — host IDE detection and browser-handoffreferences/dev-server-detection.md — port resolution documentationreferences/dev-server-rails.md — Rails dev-server defaultsreferences/dev-server-next.md — Next.js dev-server defaultsreferences/dev-server-vite.md — Vite dev-server defaultsreferences/dev-server-nuxt.md — Nuxt dev-server defaultsreferences/dev-server-astro.md — Astro dev-server defaultsreferences/dev-server-remix.md — Remix dev-server defaultsreferences/dev-server-sveltekit.md — SvelteKit dev-server defaultsreferences/dev-server-procfile.md — Procfile-based dev-server defaultsScripts (invoked via bash scripts/<name>):
scripts/read-launch-json.sh — launch.json readerscripts/detect-project-type.sh — project-type classifierscripts/resolve-package-manager.sh — lockfile-based package-manager resolverscripts/resolve-port.sh — port resolution cascade