Doctor

Name: Doctor
Author: bluzir

bluzir/claude-code-design

42 installs
98 repo stars
Updated April 20, 2026
bluzir/claude-code-design

Doctor is a Claude Code skill that runs a cold-start health check for the claude-code-design toolkit and optionally installs its missing dependencies.

About

Doctor is a first-run setup and health-check command for the claude-code-design toolkit. It inventories dependencies (Chrome DevTools MCP, Node, gh, monolith), reports what is missing, and offers a consented install and a smoke test. A developer runs it on a fresh clone or when the toolkit feels broken.

Verifies Chrome DevTools MCP, Node, gh CLI, monolith, and working dirs in one health check
Offers consented auto-install of optional deps (monolith, pptxgenjs, puppeteer)
Runs a smoke-test deck and prints a hint sheet of all toolkit commands

Doctor by the numbers

42 all-time installs (skills.sh)
Ranked #331 of 550 CLI & Terminal skills by installs in the Skillselion catalog
Data as of Aug 1, 2026 (Skillselion catalog sync)

At a glance

doctor capabilities & compatibility

Free; installs optional CLI deps locally

Capabilities: ingest figma · make deck · export pptx
Use cases: devops
Pricing: Free

From the docs

What doctor says it does

First-run setup + health check. Verifies Chrome DevTools MCP, installs optional deps (monolith, pptxgenjs, puppeteer), creates working dirs, runs smoke test.

SKILL.md

Cold-start health check + optional auto-install. Safe to run multiple times.

SKILL.md

npx skills add https://github.com/bluzir/claude-code-design --skill doctor

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/bluzir/claude-code-design/doctor.svg)](https://skillselion.com/skills/bluzir/claude-code-design/doctor)

Installs	42
repo stars	★ 98
Last updated	April 20, 2026
Repository	bluzir/claude-code-design ↗

What it does

Run on a fresh clone to confirm Chrome DevTools MCP, Node, and export deps are present before building decks or prototypes.

When should I use this skill?

on a fresh clone of the toolkit or when commands feel broken

What you get

A structured green/red readiness report plus optional installs so the design skills run.

dependency report
working directories
smoke-test deck

By the numbers

5-phase health-check flow
8-item dependency inventory

Files

SKILL.mdMarkdownGitHub ↗

Doctor

Cold-start health check + optional auto-install. Safe to run multiple times.

Phase 1 — Inventory

Run in parallel where possible:

1. Bash(claude mcp list) — parse output, look for chrome-devtools: ✓ Connected 2. Bash(which monolith) — existence check 3. Bash(which node) — required 4. Bash(which gh) — for /ingest-github 5. Bash(test -f package.json && echo yes || echo no) 6. Bash(test -d starters && echo yes || echo no) — expect yes 7. Bash(test -d artifacts && echo yes || echo no) 8. Bash(test -d .claude/skills && echo yes || echo no) — expect yes

Phase 2 — Report

Print structured report:

Chrome DevTools MCP: ✓ / ✗ (if ✗, show install command)
monolith CLI:        ✓ / ✗ (optional; needed for /export-standalone)
Node:                ✓ / ✗ (required)
gh CLI:              ✓ / ✗ (needed for /ingest-github)
package.json:        exists / missing
starters/ dir:       exists / missing
artifacts/ dir:      will create
.claude/skills/:     N skills found
FIGMA_TOKEN env:     set / not set (only needed for /ingest-figma)

Phase 3 — Repair (with user consent)

For each missing item, ask the user with AskUserQuestion: "Install X now?" (yes/skip/all).

Repair commands (only on yes):

Chrome DevTools MCP: Bash(claude mcp add chrome-devtools -s user -- npx chrome-devtools-mcp@latest) — note: requires Claude Code restart to take effect
monolith: Bash(brew install monolith) (macOS) or tell user for linux
pptxgenjs + puppeteer:

  Bash(test -f package.json || npm init -y)
  Bash(npm install -D pptxgenjs puppeteer)

artifacts/ dir: Bash(mkdir -p artifacts assets/thumbs test)

Phase 4 — Smoke test

If everything is green (and user didn't just run install → restart): 1. Write test/smoke-deck.html:

   <!doctype html>
   <html><head><meta charset="utf-8"/><title>Smoke</title>
   <script src="../starters/deck_stage.js"></script></head>
   <body><deck-stage width="1920" height="1080">
     <section style="padding:60px;font:48px/1.2 Georgia"><h1>One</h1></section>
     <section style="padding:60px;font:48px/1.2 Georgia;background:#f4e4d7"><h1>Two</h1></section>
     <section style="padding:60px;font:48px/1.2 Georgia;background:#4a5d2e;color:#fff"><h1>Three</h1></section>
   </deck-stage></body></html>

2. Run /done test/smoke-deck.html 3. If Chrome DevTools MCP is connected — check screenshot at .claude/last-preview.png exists and console is clean 4. Report pass/fail

Phase 5 — Hint sheet

Print one-liner hints:

Available commands & skills:
  /make-deck <brief>            — build a slide deck
  /interactive-prototype <brief> — clickable React prototype
  /wireframe <thing>            — low-fi variants
  /create-design-system <src>   — extract style guide
  /ingest-github <url>          — pull tokens from repo
  /ingest-screenshot <path>     — extract tokens from image
  /ingest-figma <url>           — pull from Figma (needs FIGMA_TOKEN)
  /make-tweakable <html>        — add live tweak panel
  /apply-tweaks <html>          — persist panel changes
  /register-asset <html>        — add to assets.html overview
  /verify-artifact <html>       — vision-based QA
  /export-pdf  /export-pptx  /export-standalone  /handoff
  /preview /done /screenshot    — operational atomics