client-onboardlisted

One command bootstraps a per-client repo so Claude Code starts pre-loaded. Detects project type (WP theme / React-Next / static / n8n / video) from files present → generates a tight CLAUDE.md (<200 lines: stack, architecture rationale, conventions + build/deploy commands) with the RIGHT deploy gotcha baked in automatically (Hostinger Node app = manual ZIP NOT GitHub; React = Vercel; video = NVENC-broken→libx264). Scaffolds .claude/, suggests relevant MCP (GHL/Hostinger), adds CLAUDE.local.md to .gitignore, enforces the CLAUDE.md-vs-Skill rule, and warns on lowercase claude.md dups. Fixes the gap: many client repos (travel, agency site, jewelry, fashion, car dealer, health clinic) ship with no CLAUDE.md, so Claude re-learns context every session. Trigger when user says: "onboard this client", "onboard repo", "bootstrap CLAUDE.md", "set up CLAUDE.md", "init client repo", "/client-onboard", or opens a client repo with no CLAUDE.md and asks Claude to start work on it. Auto-trigger heuristic: cwd is a client proje
waseemnasir2k26/skynetlabs-all-claude-code · ★ 0 · AI & Automation · score 68

Install: claude install-skill waseemnasir2k26/skynetlabs-all-claude-code

# client-onboard ## When to use USE when: - Opening a client repo that has NO `CLAUDE.md` at root - Spinning up a new client project (travel site, agency site, jewelry, fashion, car dealer, health clinic, etc.) - An existing repo's CLAUDE.md is stale/bloated (>200 lines) and needs a rebuild SKIP when: - Repo already has a tight, current CLAUDE.md (just edit it, don't regenerate) - Not a code repo (use `/daily` or brain notes instead) ## Core rule (from claude-code-mastery) > **CLAUDE.md = facts always true. Skill = procedures you'd re-paste.** If a step is a repeatable PROCEDURE (deploy dance, audit format, content batch), do NOT bloat CLAUDE.md with it — note it and **suggest building a Skill**. CLAUDE.md only holds: the _what_ (stack), the _why_ (architecture rationale), the _how_ (conventions + the exact build/deploy commands for THIS repo). Hard limits: - CLAUDE.md **< 200 lines**. Over = bloat → cut to facts. - Casing is **ALWAYS `CLAUDE.md`** (uppercase). Never `claude.md` / `Claude.md`. ## Inputs required 1. **Repo path** — defaults to cwd 2. **Client name / slug** — e.g. `your-site`, `travel-client` (infer from dir name, confirm) 3. **Live URL** (optional) — for deploy context + MCP wiring 4. **Is it a video repo?** — only then bake NVENC gotcha (auto-detected, confirm) If client/stack ambiguous → ASK before writing. Never invent a deploy target. ## The 7-step recipe ### 1. Pre-flight + casing guard ```bash cd <repo> git rev-parse --is-inside-work-tree