nightdreamzshop-web

Codepolish — Design skill for Claude Code

Design community

Turn vibe-coded projects into clean, polished, production-ready code and UI.

How to install Codepolish

This entry records only its repository, not the path inside it, so there is no exact command to give. Open nightdreamzshop-web/codepolish and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Codepolish does

Turn vibe-coded projects into clean, polished, production-ready code and UI. An Agent Skill for Claude Code.

Alternatives in Design

Frontend Design — Create distinctive, production-grade frontend interfaces with high design quality 94.1k ★
Figma Implement Design — Translate Figma designs into production-ready code with pixel-perfect accuracy 14.6k ★
Pack — Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts 3.6k ★

README

CodePolish

**Turn vibe-coded projects into clean, polished, production-ready code and UI.**

CodePolish is an [Agent Skill](https://docs.claude.com/en/docs/claude-code/skills) for coding agents such as Claude Code. It audits an existing codebase, fixes the low-risk problems, and reports the risky ones, without rewriting code that already works.

Preserve what works. Fix what doesn't. Polish what feels unfinished.

Projects built quickly with AI help often *work* but carry a long tail of small problems: five versions of the same button, components left over from earlier iterations, `console.log("here")`, magic numbers, spacing that's almost consistent, layouts that break at 375px, and missing focus states. CodePolish finds those problems, fixes the safe ones, and hands you a short report.

What it checks

Code quality: dead code, unused imports, debug leftovers, duplication, god components, deep nesting, swallowed errors, type escape hatches, fragile state, and obvious security or performance issues.
Vibe-code patterns: parallel implementations of one thing, leftover old versions, files that only ever grew by appending, duplicate utilities, convention drift between sessions, narrating comments, pointless abstraction, magic numbers, and patch-on-patch fixes.
Frontend polish: responsive overflow, spacing, radius and typography consistency, hover, active, focus and disabled states, loading, empty and error states, layout shift, touch targets, accessibility basics, and animation quality.
Responsive testing: checks at 375, 430, 768, 1024 and 1440 px when a browser tool is available. Otherwise it reviews the code statically.

It judges the actual code. Code isn't flagged just because an AI might have written it.

Modes

Mode	What happens
`audit`	Analyzes and reports. Changes nothing. This is the default when the request is ambiguous.
`safe`	Fixes low-risk issues automatically, such as unused imp