everyinc/compound-engineering-plugin

ce-polish

Polish a working feature through user-directed live browser feedback.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill ce-polish

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Polish

Put a working feature in front of the user and turn their live observations into focused UX fixes on the running page.

Done: the user ends the polish loop, every requested fix is reflected in the live feature or reported as blocked, and the in-scope changes are saved in local commit(s). A server or checkout blocker also ends the run when it is reported with the evidence needed to resume.

Boundaries: the user drives what to inspect and change; do not invent an autonomous checklist or expand into general QA. Never work on the repository's default branch. This workflow may edit and locally commit the requested polish, but it never pushes or opens a PR.

Run

  1. Get the live page ready. Read references/run.md before resolving the requested ref or starting anything. It owns existing-worktree safety, dev-server discovery, the bundled-script calls, reachability, and the browser handoff.
  2. Wait for observations. Tell the user where the server is running and ask what could be better. Do not start a review pass while they browse.
  3. Iterate. For each requested change, inspect only as needed, edit the in-scope surface, and let hot reload update the page. When the user asks you to inspect the result, use a browser capability available in the active harness; if none exists, ask them to describe what they see.
  4. Close locally. When the user says they are done, invoke ce-commit for the polish changes, then report the commit(s), the still-running server URL, and any residual blocker.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
everyinc
コミュニティ

ce-compound

Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-plan

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-setup

Check Compound Engineering's tools and repo config and fix what it finds, scaffold a Compound Pack with pack: , or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing Compound Engineering, or when creating or updating CODINGSTANDARDS.md or REVIEW.md, including on a schedule.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日
everyinc
コミュニティ

ce-simplify-code

Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.

1時間の導入数
1
GitHub Stars
2.6万
更新日
11月18日