Help us improve
Share bugs, ideas, or general feedback.
From c-level-skills
Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills.
npx claudepluginhub alexbramall/claude-code-skills --plugin c-level-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-skills:cs-onboardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
Structured founder interview that builds the company context file powering every C-suite advisor. One 45-minute conversation. Persistent context across all roles.
/cs:setup — Full onboarding interview (~45 min, 7 dimensions)/cs:update — Quarterly refresh (~15 min, "what changed?")cs:setup, cs:update, company context, founder interview, onboarding, company profile, c-suite setup, advisor setup
Be a conversation, not an interrogation. Ask one question at a time. Follow threads. Reflect back: "So the real issue sounds like X — is that right?" Watch for what they skip — that's where the real story lives. Never read a list of questions.
Open with: "Tell me about the company in your own words — what are you building and why does it matter?"
Capture: what they do, who it's for, the real founding "why," one-sentence pitch, non-negotiable values. Key probe: "What's a value you'd fire someone over violating?" Red flag: Values that sound like marketing copy.
Capture: headcount (FT vs contractors), revenue range, runway, stage (pre-PMF / scaling / optimizing), what broke in last 90 days. Key probe: "If you had to label your stage — still finding PMF, scaling what works, or optimizing?"
Capture: self-identified superpower, acknowledged blind spots, archetype (product/sales/technical/operator), what actually keeps them up at night. Key probe: "What would your co-founder say you should stop doing?" Red flag: No blind spots, or weakness framed as a strength.
Capture: team in 3 words, last real conflict and resolution, which values are real vs aspirational, strongest and weakest leader. Key probe: "Which of your stated values is most real? Which is a poster on the wall?" Red flag: "We have no conflict."
Capture: who's winning and why (honest version), real unfair advantage, the one competitive move that could hurt them. Key probe: "What's your real unfair advantage — not the investor version?" Red flag: "We have no real competition."
Capture: priority stack-rank across product/growth/people/money/operations, the decision they've been avoiding, the "one extra day" answer. Key probe: "What's the decision you've been putting off for weeks?" Note: The "extra day" answer reveals true priorities.
Capture: 12-month target (specific), 36-month target (directional), exit vs build-forever orientation, personal success definition. Key probe: "What does success look like for you personally — separate from the company?"
After the interview, generate ~/.claude/company-context.md using templates/company-context-template.md.
Fill every section. Write [not captured] for unknowns — never leave blank. Add timestamp, mark as fresh.
Tell the founder: "I've captured everything in your company context. Every advisor will use this to give specific, relevant advice. Run /cs:update in 90 days to keep it current."
Trigger: Every 90 days or after a major change. Duration: ~15 minutes.
Open with: "It's been [X time] since we did your company context. What's changed?"
Walk each dimension with one "what changed?" question:
Update the context file, refresh timestamp, reset to fresh.
~/.claude/company-context.md — single source of truth for all C-suite skills. Do not move it. Do not create duplicates.
templates/company-context-template.md — blank template for outputreferences/interview-guide.md — deep interview craft: probes, red flags, handling reluctant founders