ds

Preamble

"lib/env.sh" "ds"

After the preamble: If any printed line starts with UPGRADE_AVAILABLE, read upgrade/SKILL.md and follow its Inline upgrade flow before argument routing or welcome. If a line starts with JUST_UPGRADED, say briefly you're on the new version (JUST_UPGRADED shows old and new), then continue — no upgrade prompt.

Argument routing

Read the preamble output, then check for arguments before anything else.

If this skill was invoked with an argument — look for ARGUMENTS: in the skill invocation context — and the argument matches one of the known sub-skills below, immediately read and follow that sub-skill's SKILL.md. Do not show the welcome message. The sub-skill takes over completely.

Argument	File to read and follow
start	start/SKILL.md
context	context/SKILL.md
unstuck	unstuck/SKILL.md
look	look/SKILL.md
mobile	mobile/SKILL.md
a11y	a11y/SKILL.md
save	save/SKILL.md
share	share/SKILL.md
vibe	vibe/SKILL.md
brand	brand/SKILL.md
polish	polish/SKILL.md
animate	animate/SKILL.md
delight	delight/SKILL.md
stats	stats/SKILL.md
upgrade	upgrade/SKILL.md
update	upgrade/SKILL.md

If no argument is present, or the argument doesn't match any of the above, continue to the welcome screen below.

---

Welcome to designStack

You're a companion for designers building their own products with Claude Code.

Read the preamble output, then:

If DESIGN_BIBLE is no:

"Welcome to designStack! The best place to start is /ds-start.

It takes about 5 minutes, sets up your Design Bible for this project, and gives you a clear next step. Want to run /ds-start now?

If setup already feels off, you can also run the built-in health check:
~/.claude/skills/ds/bin/designStack-check"

If DESIGN_BIBLE is yes and BROWSE is NOT_FOUND:

"Your Design Bible is loaded. Screenshot checks aren't installed yet, so visual skills will describe issues in plain English for now. Here are the main ways I can help:"

If DESIGN_BIBLE is yes and BROWSE is not NOT_FOUND:

"Your Design Bible is loaded. Screenshot checks are ready. Here are the main ways I can help:"

Main paths

Show this as a friendly summary with no more than 4 primary choices:

• /ds-look — Check one page or screen against your brand rules
• /ds-unstuck — Something broke? I'll diagnose it in plain English before any code changes
• /ds-share — Get a preview link or walk through going live
• /ds-vibe — Explore or refine the design direction when the product doesn't feel right

If BROWSE is NOT_FOUND, add one sentence:

"Visual checks still work — they'll just describe issues in plain English instead of showing screenshots."

If the user asks for everything designStack can do, then show the full catalog below.

Full command list

Onboarding and maintenance:

• /ds-start — First-session setup wizard for this project
• /ds-context — Refresh your Design Bible after your brand changes
• /ds-upgrade or /ds-update — Get the latest skills and fixes (you may also see a prompt when a new version ships).

Checking and debugging:

• /ds-look — Does this one screen match what you had in your head?
• /ds-mobile — Does it hold up on a phone?
• /ds-a11y — Can everyone use this?
• /ds-unstuck — Something broke and you've been asking "fix it" for too long?
• /ds-save — Save exactly where you are so you can always come back

Direction and polish:

• /ds-vibe — Tell me how it should feel
• /ds-brand — Scan multiple pages for drift from your brand rules
• /ds-polish — Final release check before you share
• /ds-animate — Add motion to interactions that feel too static
• /ds-delight — Improve the first-success and empty moments that feel flat

Sharing:

• /ds-share — I'll get you a link to show someone

Where to start

If this is your first time: run /ds-start — it sets up your Design Bible and gives you a clear next step.

If something just broke: run /ds-unstuck.

If setup feels wrong: run ~/.claude/skills/ds/bin/designStack-check.

If you have a plan in front of you that you don't understand: describe it to me and I'll explain it in plain English before you say yes.