Menu
Shows local designStack usage analytics such as run counts, recent history, and success rates. Requires analytics to be enabled. Use when the user explicitly asks for usage analytics or runs '/ds-stats'.
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-stats |
| version | 0.1.0 |
| description | Shows local designStack usage analytics such as run counts, recent history, and success rates. Requires analytics to be enabled. Use when the user explicitly asks for usage analytics or runs '/ds-stats'. |
| license | MIT |
| allowed-tools | ["Bash","AskUserQuestion"] |
| compatibility | No external dependencies. Reads from ~/.dstack/analytics/skill-usage.jsonl. |
_DESIGNSTACK_VER="0.1.0"
_ANALYTICS="$HOME/.dstack/analytics/skill-usage.jsonl"
_TEL_CONFIG="$HOME/.dstack/config"
_TEL=$(grep "^telemetry=" "$_TEL_CONFIG" 2>/dev/null | cut -d= -f2 || echo "community")
_HAS_DATA="no"
[ -f "$_ANALYTICS" ] && [ -s "$_ANALYTICS" ] && _HAS_DATA="yes"
_TOTAL=$(wc -l < "$_ANALYTICS" 2>/dev/null | tr -d ' ' || echo "0")
echo "DESIGNSTACK: $_DESIGNSTACK_VER"
echo "TELEMETRY: $_TEL"
echo "HAS_DATA: $_HAS_DATA"
echo "TOTAL_RUNS: $_TOTAL"
echo "ANALYTICS_FILE: $_ANALYTICS"
Show how you've used designStack — which skills you run most, how many succeeded, and when you last used each one.
If TELEMETRY is off:
"Analytics is turned off — no data has been collected. To enable it, edit
~/.dstack/configand changetelemetry=offtotelemetry=community. Future skill runs will be tracked from that point."
Stop here if telemetry is off.
If HAS_DATA is no:
"No usage data yet — run a few designStack skills first and then come back. Analytics are stored in
~/.dstack/analytics/skill-usage.jsonl."
Stop here if no data.
Run this bash to extract usage data:
# Count per skill
awk -F'"' '/"skill":/ {for(i=1;i<=NF;i++) if($i=="skill") print $(i+2)}' "$HOME/.dstack/analytics/skill-usage.jsonl" | sort | uniq -c | sort -rn
# Count by outcome
awk -F'"' '/"outcome":/ {for(i=1;i<=NF;i++) if($i=="outcome") print $(i+2)}' "$HOME/.dstack/analytics/skill-usage.jsonl" | sort | uniq -c
# Last 5 runs (most recent)
tail -5 "$HOME/.dstack/analytics/skill-usage.jsonl"
Present a plain-English summary:
designStack usage so far
Total skill runs: [TOTAL_RUNS]
Most used skills: [For each skill in usage count order:]
/ds-[skill] — used [N] timesOutcomes:
Last 5 sessions: [For each of last 5 entries — show skill name + outcome + timestamp in plain English, e.g. "ran /ds-look · success · 2 days ago"]
Analytics stored in: ~/.dstack/analytics/skill-usage.jsonl
To turn off analytics: edit ~/.dstack/config and set telemetry=off.
Based on which skills they've used most:
/ds-look a lot but never /ds-brand: suggest running /ds-brand for a full consistency scan/ds-a11y: mention it for accessibility gradingerror outcomes on any skill: offer to troubleshoot with /ds-unstuck