The make-it-designed skill: polish the page, don't rebuild it

You built something, it works, and it looks like a form. The instinct now is to add: another color, another section, a row of icons, a hero video. That instinct is what made it look cheap in the first place.

The make-it-designed skill runs the opposite pass. It reads the page you already have, finds at least three things to delete, and only then adds one deliberate detail. Your words, your structure, and your links all stay exactly where they are. It's only changing how the thing looks, and it says that out loud before it touches anything.

That one added detail is the part people notice. The skill picks whichever of three fits your page: a hand-drawn underline that draws itself once under three or four words of your headline, an editorial headline treatment with a small kicker line above it, or a single row of real numbers with labels. One of those, once, in your accent color. The skill is one of the free ones in our public freeskills repo.

Clone the repo, then copy this folder into your Claude Code skills directory.

Open a new Claude Code session and the skill is live. Nothing to configure, no API keys.

Type /make-it-designed. It asks for the file path of the page, reads the whole file, then tells you the rule it's working under: refine, not rebuild. It also reminds you that /rewind puts everything back, so you can't break this. If you've already run the design-taste skill from the same repo, it reads your saved design file and uses your palette and fonts instead of picking new ones.

First it shows you the list of what it cut and why, one line each. Then it makes the changes in place at your original path, adds the one signature touch, and writes a change log to ~/design-notes/<page-name>-polish.md. A good first result is a page that looks emptier and reads clearer, with one thing on it that surprises you. Open it, then give it one reaction in plain English. It makes one round of edits from that and stops.

The straight run. Tell it what the page is for and what you want people to do on it, because that decides what stays loudest.

After you open the page, describe the feeling, not the code. One word is enough to redirect the whole thing.

The change log is what stops your next build from looking unrelated to this one. Ask it to hand you the reusable version.

The out-loud version of what this skill does and why the fix is removal, not more stuff. About 60 seconds.

1. 1Hook: there's a brand new free Claude skill that takes you from a page that looks like a default template to a page that looks like somebody designed it, without rebuilding anything.
2. 2Mechanism: you point it at a page that already works, and it deletes three things before it adds one, the extra colors, the shadows doing nothing, the second button competing with the first. Then it fixes the four that decide how a page reads, the two fonts, the spacing scale, the palette, and what's loudest on the screen. Last it adds exactly one signature touch so the page has a point of view.
3. 3Transformation: you stop being the person whose stuff obviously came out of a generator. Your page has a look, and you've got the change log to reuse it on the next one.
4. 4Close: the skill is free, like the other 54 in the repo. Making everything you build look like it came from the same person is the longer job, and we run that inside Claude Code Club. $9 a month, link's below.

Tonight: run it on the last page you built, open the result, and give it one honest sentence about what still feels wrong.