← ClaudeAtlas

dxkit-onboardlisted

Walk a customer through setting up dxkit on a repo from scratch — checks state, installs, scaffolds, configures hooks, runs doctor, fixes any gaps, captures the first baseline, sets up branch protection + Codespaces prebuild. Also drives a DETERMINISTIC deep-configuration pass — it runs `vyuh-dxkit configure --plan`, which COMPUTES the config each capability should take from observable repo facts (not the agent's judgment, so the same repo yields the same plan every run), shows it, gets confirmation, then `configure --apply` merge-writes it into policy.json without clobbering existing settings. The plan is registry-driven, so new capabilities join it automatically as dxkit grows. Use when the user asks "set me up", "install dxkit on this repo", "I want to use dxkit", "walk me through dxkit setup", "help me get started with dxkit", "configure dxkit for this repo", "what should I set up", or anything about onboarding or fully configuring a repo. Asks for confirmation at each step with sensible defaults; hands o
vyuh-labs/dxkit · ★ 10 · Code & Development · score 72
Install: claude install-skill vyuh-labs/dxkit
# dxkit-onboard This skill drives the FULL new-customer journey end-to-end. It's the "I have nothing — set me up" surface (complement to `dxkit-update` for existing-install upgrades and `dxkit-fix` for repairs). Unlike the other dxkit-* skills which are each scoped to a single domain (install / config / hooks / etc.), dxkit-onboard orchestrates across them. It dispatches into `dxkit-init` for flag choices, `dxkit-fix` for gap closure, `dxkit-hooks` for hook deep-dives — composing a single coherent customer conversation. ## When to use this skill Use when: - "Set me up" - "Install dxkit on this repo" - "I want to use dxkit" - "Walk me through dxkit setup" - "Help me get started with dxkit" - "First time using dxkit" Don't use when: - Customer already has `.vyuh-dxkit.json` AND is asking about a specific task (use the focused skill — dxkit-reports, dxkit-action, etc.) - Customer wants to UPGRADE an existing install (use `dxkit-update`) - Something is broken (use `dxkit-fix`) ## The onboarding journey ``` [1] State check → is dxkit installed? scaffold present? baseline captured? hooks active? [2] Install if needed → npm init @vyuhlabs/dxkit OR npx vyuh-dxkit init --full --yes (init auto-offers the UI→API integration gate when it detects client calls + routes — pick a posture then) [3] Doctor → npx vyuh-dxkit doctor (parse summary.fixable[]) [4] Fix gaps → dispatch through dxkit-fix for each fixab