philosopher

Activates expansive cross-domain brainstorming and assumption-questioning for design problems.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill philosopher-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: philosopher
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/philosopher
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill philosopher-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design problems often get solved too quickly with shallow framing, leading to obvious solutions that miss the real issue. This Skill forces deeper exploration of a problem before jumping to solutions, surfacing hidden assumptions and unexpected connections. ## Core Features & Use Cases - Three-Phase Cognitive 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, blueprint, journey, specify, and more) to reframe briefs, question structural assumptions, and stress-test specs. - Structured Check-ins: Pauses every few exchanges to let you keep exploring, synthesize findings, or redirect the exploration, with adjustable intensity levels from light reframe to deep generative territory. - Use Case: When a user flow feels logical but lifeless, invoke philosopher mode to question inherited interaction patterns and explore what the design would look like if current conventions didn't exist. ## Quick Start Ask the AI 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 brainstorm design problems without jumping to solutions?

Invoke philosopher mode by saying "sit with this", "brainstorm", or "I'm stuck". The skill follows a strict protocol: it first immerses in the problem to surface hidden assumptions, then expands into cross-domain connections, and only synthesizes solutions when you explicitly ask.

What triggers expansive or philosopher mode in design work?

Triggers include phrases like "explore this problem", "go deeper", "what am I missing", or "go weird with it". It also activates when a problem is being solved too quickly, the framing feels shallow, or research findings seem too clean.

Can philosopher mode work with other design skills?

Yes, it is a cross-cutting cognitive mode designed to run alongside every Intent skill. It helps strategize reframe briefs, blueprint question structural assumptions, journey rethink interaction models, and specify stress-test specs for unexamined edge cases.

How do I control the intensity of brainstorming sessions?

Specify low, medium, or high intensity. Low gives a quick reframe with check-ins after 2 exchanges, medium is the default full protocol with check-ins every 3 exchanges, and high maximizes associative width for fundamentally misframed problems.

When should I not use expansive exploration mode?

Avoid it when you need a concrete deliverable, decision, or recommendation immediately. The mode exits instantly when you ask for a deliverable or say "land it", and it is not suited for execution-phase tasks where the problem is already well-framed.