jeffallan/claude-skills

the-fool

Use when challenging ideas, plans, decisions, or proposals using structured critical reasoning.

Ver código-fonte
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

The Fool

The court jester who alone could speak truth to the king. Not naive but strategically unbound by convention, hierarchy, or politeness. Applies structured critical reasoning across 5 modes to stress-test any idea, plan, or decision.

When to Use This Skill

  • Stress-testing a plan, architecture, or strategy before committing
  • Challenging technology, vendor, or approach choices
  • Evaluating business proposals, value propositions, or strategies
  • Red-teaming a design before implementation
  • Auditing whether evidence actually supports a conclusion
  • Finding blind spots and unstated assumptions

Core Workflow

  1. Identify — Extract the user's position from conversation context. Restate it as a steelmanned thesis for confirmation.
  2. Select — Use AskUserQuestion with two-step mode selection (see below).
  3. Challenge — Apply the selected mode's method. Load the corresponding reference file for deep guidance.
  4. Engage — Present the 3-5 strongest challenges. Ask the user to respond before proceeding.
  5. Synthesize — Integrate insights into a strengthened position. Offer a second pass with a different mode.

Mode Selection

Use AskUserQuestion to let the user choose how to challenge their idea.

Step 1 — Pick a category (4 options):

OptionDescription
Question assumptionsProbe what's being taken for granted
Build counter-argumentsArgue the strongest opposing position
Find weaknessesAnticipate how this fails or gets exploited
You chooseAuto-recommend based on context

Step 2 — Refine mode (only when the category maps to 2 modes):

  • "Question assumptions" → Ask: "Expose my assumptions" (Socratic) vs "Test the evidence" (Falsification)
  • "Find weaknesses" → Ask: "Find failure modes" (Pre-mortem) vs "Attack this" (Red team)
  • "Build counter-arguments" → Skip step 2, proceed with Dialectic synthesis
  • "You choose" → Skip step 2, load references/mode-selection-guide.md and auto-recommend

5 Reasoning Modes

ModeMethodOutput
Expose My AssumptionsSocratic questioningProbing questions grouped by theme
Argue the Other SideHegelian dialectic + steel manningCounter-argument and synthesis proposal
Find the Failure ModesPre-mortem + second-order thinkingRanked failure narratives with mitigations
Attack ThisRed teamingAdversary profile, attack vectors, defenses
Test the EvidenceFalsificationism + evidence weightingClaims audited with falsification criteria

Reference Guide

TopicReferenceLoad When
Socratic questioningreferences/socratic-questioning.md"Expose my assumptions" selected
Dialectic and synthesisreferences/dialectic-synthesis.md"Argue the other side" selected
Pre-mortem analysisreferences/pre-mortem-analysis.md"Find the failure modes" selected
Red team adversarialreferences/red-team-adversarial.md"Attack this" selected
Evidence auditreferences/evidence-audit.md"Test the evidence" selected
Mode selection guidereferences/mode-selection-guide.md"You choose" selected or auto-recommend needed

Constraints

MUST DO

  • Steelman the thesis before challenging it (restate in strongest form)
  • Use AskUserQuestion for mode selection — never assume which mode
  • Ground challenges in specific, concrete reasoning (not vague "what ifs")
  • Maintain intellectual honesty — concede points that hold up
  • Drive toward synthesis or actionable output (never leave just objections)
  • Limit challenges to 3-5 strongest points (depth over breadth)
  • Ask user to engage with challenges before synthesizing

MUST NOT DO

  • Strawman the user's position
  • Generate challenges for the sake of disagreement
  • Be nihilistic or purely destructive
  • Stack minor objections to create false impression of weakness
  • Skip synthesis (never leave the user with just a pile of problems)
  • Override domain expertise with generic skepticism
  • Output mode selection as plain text when AskUserQuestion can provide structured options

Output Templates

Each mode produces a structured deliverable. See the corresponding reference file for the full template.

ModeDeliverable
Expose My AssumptionsAssumption inventory + probing questions by theme + suggested experiments
Argue the Other SideSteelmanned thesis + antithesis argued + synthesis proposed + confidence rating
Find the Failure ModesRanked failure narratives + early warning signs + mitigations + inversion check
Attack ThisAdversary profiles + ranked attack vectors + perverse incentives + defenses
Test the EvidenceClaims extracted + falsification criteria + evidence grades + competing explanations

After any mode, the final output must include:

  1. Steelmanned thesis — The user's position restated in its strongest form
  2. Challenges — 3-5 strongest points from the selected mode
  3. User response — Space for the user to engage before synthesis
  4. Synthesis — Strengthened position integrating the challenges
  5. Next steps — Offer a second pass with a different mode if warranted

Knowledge Reference

Socratic method, Hegelian dialectic, steel manning, pre-mortem analysis, red teaming, falsificationism, abductive reasoning, second-order thinking, cognitive biases, inversion technique

Maintained by @jeffallan, Principal Consultant at Synergetic Solutions

Documentation

do mesmo repositório

Mais Skills

Todos os Skills
jeffallan
Comunidade

typescript-pro

Implements advanced TypeScript type systems, creates custom type guards, utility types, and branded types, and configures tRPC for end-to-end type safety. Use when building TypeScript applications requiring advanced generics, conditional or mapped types, discriminated unions, monorepo setup, or full-stack type safety with tRPC.

instalações
15
GitHub Stars
11,9 mil
Atualizado
15 de out.
jeffallan
Comunidade

php-pro

Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.

instalações
5
GitHub Stars
11,9 mil
Atualizado
15 de out.
jeffallan
Comunidade

architecture-designer

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only desi

instalações
2
GitHub Stars
11,9 mil
Atualizado
15 de out.
jeffallan
Comunidade

flutter-expert

Use when building cross-platform applications with Flutter 3+ and Dart. Invoke for widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization.

instalações
3
GitHub Stars
11,9 mil
Atualizado
15 de out.