philosopher

Re-examine design problems through immersion, associative expansion, and invited synthesis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/snuffomega/pricechart --skill philosopher-snuffomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: philosopher
Source: https://github.com/snuffomega/pricechart/tree/main/.agents/skills/philosopher
Command: npx skills add https://github.com/snuffomega/pricechart --skill philosopher-snuffomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The philosopher helps you escape shallow framing and premature decisions by slowing down design reasoning until the real underlying tensions, assumptions, and adjacent problems become visible.

Core Features & Use Cases

  • Problem immersion first: reframes the question by exposing hidden assumptions, stakeholder differences, and problem adjacency before generating directions.
  • Associative expansion without forcing solutions: pulls in cross-domain resonances (biology, architecture, linguistics, mythology, systems, etc.) to surface connections that are structurally alive.
  • Synthesis only when invited: waits for an explicit “synthesize” moment to translate exploration into the active design skill’s language (e.g., strategize, blueprint, journey, specify).
  • Designed check-ins to prevent runaway ideation: introduces structured pauses after a few exchanges so the exploration stays purposeful and can redirect or land.

Quick Start

Activate philosopher mode and tell the AI: "I'm stuck—sit with this problem and help me find the assumptions I'm not seeing yet."

Frequently Asked Questions about philosopher

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

FAQPage Schema
How do I test hidden assumptions in problem framing before starting design work?

To test hidden assumptions in problem framing, you immerse in the underlying question and stakeholder differences to expose shallow decisions. This slows down design reasoning to reveal adjacent issues before generating premature solutions.

What is the best way to apply cross-domain thinking to a stalled design problem?

The best way to apply cross-domain thinking to a stalled design problem is to pull associative resonances from fields like biology, architecture, and linguistics. This surfaces structurally alive connections to broaden associative expansion without forcing premature solutions.

How do I prevent runaway ideation during brainstorming and systems thinking?

To prevent runaway ideation during brainstorming, you enforce structured check-ins and pauses after a few exchanges. This keeps systems thinking purposeful, allows for redirection, and ensures exploration stays grounded before any synthesis occurs.

When do I need to re-examine shallow problem framing instead of pushing for a solution?

You need to re-examine shallow problem framing during early or stalled design work when hidden tensions and adjacent issues are not yet visible. This reframes the question by exposing stakeholder differences before attempting any synthesis.

How do I translate creative strategy exploration into actionable design blueprints?

To translate creative strategy exploration into actionable design blueprints, you wait for an explicit synthesis invitation. This translates cross-domain exploration into the active design skill's language like strategize, blueprint, journey, or specify.