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 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

모든 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일