cynic-wisdom

Synthesize 19 philosophical traditions into provisional technical decision guidance.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/zeyxx/CYNIC-legacy --skill cynic-wisdom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cynic-wisdom
Source: https://github.com/zeyxx/CYNIC-legacy/tree/main/.crush/skills/cynic-wisdom
Command: npx skills add https://github.com/zeyxx/CYNIC-legacy --skill cynic-wisdom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides philosophical grounding for technical decisions, helping users question assumptions, navigate dilemmas, and seek deeper wisdom beyond purely technical considerations.

Core Features & Use Cases

  • Cross-Tradition Synthesis: Draws on 19 philosophical traditions to inform decision-making.
  • φ-Bounded Confidence: Ensures all conclusions are provisional and acknowledge uncertainty (max 61.8% confidence).
  • Axiomatic Framework: Maps insights to CYNIC's five core axioms (FIDELITY, PHI, VERIFY, CULTURE, BURN).
  • Use Case: When deciding whether to refactor a legacy system, this Skill can help weigh the technical debt against the potential disruption and long-term maintenance costs by consulting relevant philosophical perspectives on action, ethics, and pragmatism.

Quick Start

Use the cynic-wisdom skill to explore the philosophical implications of rewriting a legacy system.

Frequently Asked Questions about cynic-wisdom

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

FAQPage Schema
How do I evaluate the ethical implications of a technical decision?

To evaluate the ethical implications of a technical decision, synthesize insights from 19 philosophical traditions to challenge assumptions and weigh dilemmas. This maps perspectives to core axioms, yielding a provisional stance capped at 61.8% confidence to acknowledge uncertainty.

What is the best way to decide whether to refactor a legacy system?

The best way to decide whether to refactor a legacy system is to weigh technical debt against potential disruption and long-term maintenance costs by consulting relevant philosophical perspectives on action, ethics, and pragmatism to seek applied wisdom.

How does philosophical pragmatism apply to software engineering dilemmas?

Philosophical pragmatism applies to software engineering dilemmas by providing a structured framework that questions purely technical considerations. It synthesizes cross-tradition insights to navigate tensions and seek deeper wisdom for builders facing complex technical choices.

Can I get a definitive answer on technical debt trade-offs?

No, you cannot get a definitive answer on technical debt trade-offs using this approach. All conclusions are provisional and explicitly bounded to a maximum of 61.8% confidence, ensuring that the applied wisdom acknowledges inherent uncertainty rather than providing absolute certainty.

When do I need philosophical grounding for technical architecture choices?

You need philosophical grounding for technical architecture choices when purely technical considerations fail to resolve dilemmas. It helps navigate complex trade-offs, question underlying assumptions, and seek deeper wisdom regarding the long-term impact and ethics of your decisions.