ds-polish

Preamble

"../lib/env.sh" "polish"

What this skill does

Think of this as the final check before you hit publish. I'll look at your site through 11 different lenses — from "does it look good?" to "can everyone use it?" — and tell you exactly what to fix before sharing with the world.

This is the release gate. If the user only wants one-screen visual QA, route them to /ds-look. If they want cross-page brand consistency, route them to /ds-brand.

Takes about 3–5 minutes.

"Checking 11 areas before you share this. Takes 3–5 minutes. I'll tell you what needs fixing and what's already great."

Step 1 — Get the URL

Ask:

"What's the main page you want to polish before sharing? (e.g. http://localhost:3000 or your live site)."

If the user asks for multiple pages, tell them:

"Let's do the most important page first. /ds-polish is the final release gate for one page at a time. If you want a multi-page consistency scan, use /ds-brand."

Step 2 — Load context

If DESIGN_BIBLE is yes, read it for brand rules. Note from Memory Log any recent confirmed intentional changes.

Step 3 — Run all 11 checks

For each check, take a screenshot and extract what you need. Describe findings in plain English. Read references/checklist.md and run all 11 checks in order, following its commands, thresholds, and plain-English result patterns.

Step 4 — Write the polished report

Follow the jargon rules in lib/plain-language.md when writing this report — no technical terms.

---

Pre-launch check for [URL]

Overall: [Ready to share / A few things to fix / Needs work before launch]

Score: [X]/11 checks passed

---

✓ Already great: [List checks that passed — give credit for what's working]

---

⚠️ Fix before sharing:

[For each failed check:] [Check name] — [Plain English description of the issue] How to fix: [Specific plain-English fix] How long: [Quick (1 min) / Short (5-10 min) / Takes a while]

---

My top 3 fixes (do these now):

1. [Most visible or impactful issue]
2. [Second most important]
3. [Third]