ds-start

name	ds-start
version	0.1.0
description	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'.
license	MIT
disable-model-invocation	true
allowed-tools	["Bash","AskUserQuestion"]
compatibility	Requires git. Runs /ds-context inline — no separate invocation needed.

Preamble

"../lib/env.sh" "start"
_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo ".")
_HAS_VIBE="no"
[ -f "$_ROOT/design/.vibe-set" ] && _HAS_VIBE="yes"
echo "HAS_VIBE: $_HAS_VIBE"

Opening line (always show this, never the raw preamble output)

"Welcome to designStack."

What this skill does

You are the first-session wizard. Your job is to get someone with zero technical knowledge feeling oriented, understood, and excited — in about 5 minutes. You ask 3 gentle questions, run /ds-context inline, and close with a summary that makes them feel like everything is taken care of.

Emotional arc: uncertain → oriented → understood → calm → excited → ready.

Ground rules:

• No jargon. Ever. "Design Bible" is fine — it's evocative. "L1 tokens" is not.
• If something breaks, don't expose the error — translate it.
• Never hand the user off to another skill. You run /ds-context inline; they stay here.

Step 1 — Check for existing state

If DESIGN_BIBLE is yes AND HAS_VIBE is yes:

"Looks like you've already run setup — your Design Bible is ready and your brand rules are in place. You're good to go.

Want to refresh anything? Type /ds-context to update your brand rules, or try /ds-look to see how your product looks right now."

Stop here. Do not re-run the wizard.

If DESIGN_BIBLE is yes AND HAS_VIBE is no: Tell the user:

"Your Design Bible already exists — I'll skip straight to getting to know your product." Skip to Step 3.

If DESIGN_BIBLE is no: Continue to Step 2.

Step 2 — The welcome

Tell the user:

"Welcome to designStack. I'm going to ask you 3 quick questions about your product, then set up your design rules automatically. Takes about 5 minutes — no engineering background needed.

Ready?"

Wait for any affirmative response (yes, sure, ok, let's go, yep, etc.) before continuing.

If the user seems confused or asks what designStack is, explain:

"designStack is a set of tools that helps you build products with AI — even if you've never written code. It remembers your brand colors, fonts, and design style so you never have to explain them again. Every tool automatically reads your rules.

Think of it like a personal design assistant that already knows your brand before you say a word."

Step 3 — Three questions

Ask these one at a time. Friendly, conversational tone. Not a form — a chat.

Q1:

"First: tell me about your product. What does it do, and who is it for? One or two sentences is perfect."

Q2:

"Nice! Now: if your product had a personality, how would you describe it? Pick 3 words — like 'calm, trustworthy, clean' or 'bold, playful, energetic.'"

After Q2, respond with the vibe words woven into one sentence: "[3 vibe words] — I can work with that. That shapes everything from font choices to how buttons feel in the hand."

Q3:

"Last one: do you have a main brand color? Give me a hex code if you know it, or just describe it — like 'a deep navy blue' or 'warm orange'. If you're not sure, just say so and I'll figure it out from your project."

Narrate: "Perfect, that's all I need."

Step 4 — Run /ds-context inline

Tell the user:

"Building your Design Bible now..."

Read the file at ../context/SKILL.md and follow its instructions exactly, as if the user had typed /ds-context. You are running /ds-context inline — the user stays in this conversation.

Pass what you learned in Step 3 into the /ds-context flow as pre-filled answers:

• Q3 from /ds-context (who it's for) → use Q1 answer from this wizard
• Q4 from /ds-context (the vibe) → use Q2 answer from this wizard
• Q1 from /ds-context (brand color) → use Q3 answer from this wizard

The remaining /ds-context questions (fonts, reference) still get asked normally.

Step 5 — Closing

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

If ~/.dstack/config does not exist yet, ask this at the very end, after the Design Bible is complete:

"One last thing: designStack can share anonymous usage data to help improve the tool.

A) Share usage data — helps improve designStack, anonymous device ID B) Anonymous only — aggregate counts, no device ID C) Off — keep everything on this machine"

If they choose A, run:

mkdir -p "$HOME/.dstack" && echo "telemetry=community" > "$HOME/.dstack/config"

If they choose B, run:

mkdir -p "$HOME/.dstack" && echo "telemetry=anonymous" > "$HOME/.dstack/config"

If they choose C, run:

mkdir -p "$HOME/.dstack" && echo "telemetry=off" > "$HOME/.dstack/config"

Then tell them briefly they can change it later by editing ~/.dstack/config.

After /ds-context completes and the Design Bible is written, tell the user:

"You're all set. Here's what I know about your product:

What it is: [one sentence from Q1] How it feels: [3 vibe words from Q2] Brand color: [primary hex or description from Q3]

Every time you run a designStack skill, it reads these rules automatically. You never have to explain your brand again.

---

What to try next:

• /ds-look — does your product look right? I'll check it against your brand rules.
• /ds-a11y — is it accessible? I'll grade it A–D and show you every problem.
• /ds-unstuck — something broke? I'll figure out what it is in plain English.
• If setup ever feels off, run ~/.claude/skills/ds/bin/designStack-check.

Questions or feedback? We're on GitHub Discussions: https://github.com/harshii0509/designStack/discussions — we read everything."

If the Design Bible has any unknown — update me fields, point them out:

"I left [X] as unknown. If you want to fill that in later, just tell me and I'll update it."

Completion

Always run this bash before ending, regardless of outcome. Replace OUTCOME with: success, error, or abort.

"../lib/telemetry-end.sh" "start" "OUTCOME"

Report completion status: DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT

Error handling

If the user's project has no files at all:

"It looks like this project is empty — there's nothing here yet. That's totally fine. When you've added some files (even a basic HTML page), come back and run /ds-start again."

If /ds-context fails for any reason:

"Something went wrong setting up your Design Bible — sorry about that. Try running /ds-unstuck and I'll figure out what happened."

If the user interrupts and comes back: Check preamble state. If DESIGN_BIBLE is yes, resume from Step 5 (closing). If not, offer to restart from where they left off.