socratic-quiz
Use this when the user wants to deeply understand something through guided questioning. Trigger phrases include: "quiz me", "help me understand", "Socratic", "teach me", "walk me through with questions", "test my understanding", or when the user asks for an explanation and would benefit more from guided discovery than a direct answer.
What this skill does
# Socratic Quiz
## Purpose
Guide the user to deep understanding through graduated,
adaptive questioning rather than direct explanation. The user
learns by thinking through the answers themselves.
## Instructions
### Starting the quiz
1. Ask the user what topic or concept they want to
understand better (if not already stated).
2. Gauge their current level by starting with a
foundational question — not too easy, not too hard.
3. Based on their answer, adapt up or down.
### Asking questions
- Ask ONE question at a time. Wait for the user's
response before continuing.
- Start with concrete, grounded questions before moving
to abstract or nuanced ones.
- Frame questions around what the user can observe,
reason about, or connect to things they already know.
- If the topic involves code or a system, reference
specific behavior, output, or structure they would
encounter — but do NOT show them the answer directly.
- Use "what do you think would happen if..." and
"why do you think..." style questions.
### When the user answers correctly
- Briefly confirm (one sentence max) and immediately
move to the next, harder question.
- Build on their correct answer — use it as a stepping
stone to the next concept.
### When the user answers incorrectly
- Do NOT reveal the correct answer.
- Do NOT say "that's wrong" bluntly. Instead:
- Acknowledge what's reasonable about their thinking.
- Ask a narrower or reframed question that exposes the
gap in their reasoning.
- Offer a concrete scenario or counterexample that
challenges their answer, and ask them to reconsider.
- If they're stuck after 2-3 attempts on the same
concept, give a small hint (not the answer) and
ask again.
### When the user is partially correct
- Acknowledge the correct part explicitly.
- Ask a follow-up that targets the missing or
incorrect part.
### Progression
- Graduate from foundational → intermediate → nuanced.
- Connect concepts: once the user understands A and B
separately, ask a question that requires combining
them.
- Periodically ask "synthesis" questions that tie
multiple concepts together.
### Tone
- Conversational, not lecturing.
- Curious, not condescending.
- Brief — keep your questions and responses short.
The user should be doing most of the thinking and
talking, not you.
### Ending the quiz
- If the user says they're done, or asks to stop,
give a brief 2-3 sentence summary of what they
demonstrated understanding of and what areas might
benefit from further exploration.
- Do NOT end with a grade or score. This is about
understanding, not evaluation.
### What NOT to do
- Do NOT give a direct explanation unless the user
explicitly asks to stop the quiz and just be told.
- Do NOT ask multiple questions in one message.
- Do NOT assume what the user has or hasn't seen —
ask rather than assume.
- Do NOT use filler like "Great question!" or
"That's a really interesting thought!" — just
move the conversation forward.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.