philosopher

Applies expansive cross-domain reasoning to reframe design problems before solving them.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill philosopher-ishfuseini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: philosopher
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/philosopher
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill philosopher-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often rushes from a shallow problem statement straight to solutions, baking in unexamined assumptions. This Skill provides a structured cognitive mode that forces deeper problem immersion, cross-domain association, and assumption-challenging before any solutioning begins. ## Core Features & Use Cases - Three-Phase Reasoning Protocol: Moves through problem immersion, associative expansion, and synthesis in strict order, never entering solution space until invited. - Cross-Skill Integration: Works alongside every Intent design skill (strategize, investigate, blueprint, journey, organize, articulate, evaluate, fortify, include, specify, measure, transpose, localize) to reframe briefs, question structures, and stress-test specs. - Intensity Levels and Check-ins: Supports low, medium, and high intensity modes with structured check-ins every few exchanges and clean exit sequences that translate insights back into the active design skill. - Use Case: A designer stuck on a user flow says "sit with this" — the Skill reframes the problem, pulls structural analogies from library wayfinding and physical spaces, then hands back reframed interaction assumptions to the journey skill. ## Quick Start Ask the assistant to enter philosopher mode and sit with your design problem before proposing any solutions.

Frequently Asked Questions about philosopher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use philosopher mode for design brainstorming?

Invoke it by saying "sit with this", "brainstorm", "explore this problem", or "philosopher mode". The Skill then immerses in the problem, expands into cross-domain associations, and only synthesizes when you explicitly ask it to land the exploration.

What is the difference between philosopher mode and a design persona?

Philosopher mode is a reasoning protocol, not a persona. The voice stays grounded while the cognitive process changes: broader association, suppressed idea-dismissal, and forced re-examination of assumptions before any solutioning.

Can philosopher mode work with other design skills like strategize or journey?

Yes, it is cross-cutting by design. It pairs with strategize to reframe briefs, blueprint to question structural assumptions, journey to rethink interaction models, and specify to surface undocumented edge cases.

When should I not use expansive reasoning mode?

Avoid it when the user needs a concrete deliverable, decision, or recommendation immediately. The protocol explicitly exits when users ask for deliverables, seem frustrated, or request returning to the brief, blueprint, journey, or spec.

How do check-ins work during a philosopher mode session?

After every 3 exchanges at medium intensity (2 at low, 4-5 at high), the Skill pauses and offers three options: keep exploring, synthesize findings, or redirect to a specific thread. Exits summarize insights and translate them back to the active design skill.