Menu
Runs a final pre-launch release gate across 11 UI checks and produces a prioritized fix list before sharing. Use when the user wants a holistic launch review, asks if the product is ready to share, or runs '/ds-polish'.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Designer-first skill bundle for non-technical founders and designers building their own products. Helps capture a Design Bible, review screens, and ship changes in plain English. Use when the user says "/ds", "designStack", "what skills do I have", "help me get started with my design", or runs with no argument for an overview.
Captures or refreshes a project's Design Bible by reading local design tokens, asking a short brand interview, and writing rules that other designStack skills can reuse. Use when starting a project, capturing brand rules, refreshing a Design Bible after brand changes, or running '/ds-context'.
Commits the current project state to git with a plain-English description of what changed, creating a restore point before risky changes. Use when the user wants to save progress, create an undo point, checkpoint work, or runs '/ds-save'.
Creates a shareable preview link or walks a user through going live in plain English, including first-time deployment setup. Use when the user wants a preview link, wants to deploy for real, wants to go live, or runs '/ds-share'.
First-session onboarding wizard that gets a new project oriented, asks three quick questions, and runs the Design Bible setup flow inline. Use when the user is new to designStack, wants first-run setup, or runs '/ds-start'.
Upgrade designStack to the latest version. Detects the standard install path, runs the update script, shows what's new. Use when asked to "upgrade designStack", "update designStack", "/ds-upgrade", or "/ds-update". Triggers: /ds-upgrade, /ds-update, update designStack.
| name | ds-polish |
| version | 0.2.0 |
| description | Runs a final pre-launch release gate across 11 UI checks and produces a prioritized fix list before sharing. Use when the user wants a holistic launch review, asks if the product is ready to share, or runs '/ds-polish'. |
| license | MIT |
| allowed-tools | ["Bash","Read","AskUserQuestion"] |
| compatibility | Requires browse binary for visual checks and axe-core injection. Falls back to code-only audit without it. |
"../lib/env.sh" "polish"
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."
Ask:
"What's the main page you want to polish before sharing? (e.g.
http://localhost:3000or your live site)."
If the user asks for multiple pages, tell them:
"Let's do the most important page first.
/ds-polishis the final release gate for one page at a time. If you want a multi-page consistency scan, use/ds-brand."
If DESIGN_BIBLE is yes, read it for brand rules.
Note from Memory Log any recent confirmed intentional changes.
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.
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):
If you fix just these 3: [what the result will be]
"Want me to fix any of these? Pick the number (1, 2, or 3 from the list above), say 'fix them all', or tell me which specific thing to tackle first."
Show before and after at desktop:
$B goto <URL>
$B screenshot /tmp/dstack-polish-after.png
"Before and after:" [show /tmp/dstack-polish-before (taken in Step 3)] [show /tmp/dstack-polish-after]
If any issues were fixed that establish new rules, append to Memory Log:
[date]: /ds-polish ran on [URL]. Score: [X]/11. Issues fixed: [list]. Rules confirmed: [any new rules].
Always run this bash before ending, regardless of outcome. Replace OUTCOME with: success, error, or abort.
"../lib/telemetry-end.sh" "polish" "OUTCOME"
Report completion status: DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT