FreddyPoly·FreddyPoly/claude-skills/polish/SKILL.md

polish

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Refine one already-built, already-qc-passed aspect of a project at a time — visual/UX details, layout, positioning, fonts, icons, animation timing, interaction feel, swapping in a finished art asset, or kicking off production of a not-yet-made one (pinning down format/dimensions/file paths/generation pipeline, then handing off to doc-to-issues for a per-variant owner:user + owner:agent issue split) — through the same relentless, multi-round interview style as the `interview` skill, but scoped to a single named aspect instead of a whole new feature. Always launches the running app first (via the `run` skill and any debug/fast-forward tools the project has) and looks at its live current state before asking anything, since visual/UX/feel decisions can't be judged from code alone. Stops at a numbered "Shared Understanding" summary and waits for explicit approval before writing anything. Once approved, updates the relevant existing SPEC.md section in place with the validated decision — no new section, no separate changelog file — then stops and points to `doc-to-issues` to sync the concrete issue; its existing rerun logic already reopens the affected done issue and flips that feature back to not-ready, so this skill never touches issues/INDEX.md or issues/FEATURES.md itself. Refuses a target that isn't an already-built, already-qc-passed aspect and redirects to `interview` instead — this skill is for refining what exists, not designing something new, and stays out of raw numeric/balance tuning (costs, growth rates, thresholds), which belongs to a separate deferred pass. Use whenever the user wants to polish, refine, nail down visual/UX/asset details for, or tune the feel of a specific already-built part of a project — "make the kill counter feel right," "let's polish the login button," "the queueing feels weird, can we fix that" — or invokes /polish explicitly. Requires an existing SPEC.md and issues/ (from doc-to-issues) — if neither exists, point to doc-to-issues (or interview first) instead.