skills/2389-research/worldview-synthesis/SKILL.md
This skill should be used when someone wants to articulate, explore, or document their personal worldview, values, or philosophy. Triggers on "articulate my values", "figure out what I believe", "document my philosophy", "write a manifesto", "define my leadership philosophy", "explore my beliefs". Surfaces beliefs through systematic interrogation, identifies tensions, and generates narrative outputs.
npx skillsauth add aiskillstore/marketplace worldview-synthesisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Core principle: A worldview isn't a list of opinions—it's a graph of beliefs with tensions. The goal is to surface what someone already believes, name the contradictions, and synthesize into something they can share.
Create project structure:
worldview/
├── data/
│ ├── schema.yaml # Structure definitions
│ ├── ideas.yaml # Belief nodes
│ ├── sources.yaml # Influences (books, people, experiences)
│ └── tensions.yaml # Productive paradoxes
├── narrative/
│ ├── mission.md # One-liner + principles
│ ├── thesis.md # One page
│ ├── synopsis.md # Three sections
│ └── full-narrative.md
└── README.md
Ask: "What books, articles, people, or experiences shaped how you see the world?"
For each source, extract 3-5 key ideas. This gives you initial nodes to build from.
Run 4-6 rounds of questions. Each round covers 3-4 domains.
Question Design Rules:
multiSelect: true when beliefs can coexistDomains to Cover:
| Domain | Example Questions | |--------|-------------------| | Mortality | How does knowing you'll die shape how you live? | | Metaphysics | What's your relationship with spirituality/religion? | | Relationships | How do you think about romantic partnership? | | Parenting | Philosophy on having/raising children? | | Body | How do you relate to physical health and aging? | | Vices | Relationship with alcohol, drugs, pleasure? | | Money | Beyond spending—freedom, obligation, suspicion? | | Competition | Collaboration vs ruthlessness? | | Trust | Default open or earned? | | Learning | Autodidact, mentorship, formal education? | | Nature | Essential or nice to visit? | | Leadership | Natural, reluctant, servant, example? | | Emotion | Relationship with anger? | | Recognition | Need fame? Already had it? | | Rest | Protect sleep or run on fumes? | | Conflict | Clear air fast or avoid? | | Work | Philosophy on effort, failure, shipping? | | Ethics | Hard lines vs softer truths? | | Society | Diagnosis of what's broken? | | Future | Optimism, pessimism, preparation? |
When beliefs contradict, DON'T resolve—NAME:
- id: collaboration-vs-ruthlessness
ideas: [collaboration-over-competition, strategic-ruthlessness]
description: "Default to positive-sum, but crush when necessary"
resolution: |
Different contexts call for different modes. Collaboration is default.
Ruthlessness is available when needed. The key is knowing when to switch.
status: embraced # or: unresolved, resolved
Tensions are often the most interesting part of a worldview.
From data, generate at ascending scales:
A worldview is living. Add new beliefs, update old ones, regenerate narratives.
- id: kebab-case-unique-id
title: "Human Readable Title"
domain: personal | ethics | society | technology | metaphysics
claim: "The actual belief in one clear sentence"
confidence: 0.0-1.0 # how sure?
importance: 0.0-1.0 # how central to worldview?
tags: [relevant, keywords]
sources: [source-ids-if-any]
supports: [ideas-this-reinforces]
tensions: [ideas-this-contradicts]
notes: "Context, caveats, origins"
Round 3: Money, Competition, Trust
Q1: How do you think about money beyond 'spend it'?
- Tool for freedom: Money buys optionality and autonomy
- Obligation to share: If you have more, redistribute
- Wealth is suspect: Getting rich usually means exploitation
- Generational thinking: Think about what to leave behind
[multiSelect: true]
Q2: What's your orientation toward competition?
- Compete hard, play fair: Want to win but not by cheating
- Collaboration over competition: Prefer positive-sum games
- Against yourself mostly: Real competition is self-improvement
- Strategic ruthlessness: Sometimes you have to crush opponents
[multiSelect: true]
Q3: How do you approach trust with new people?
- Trust until betrayed: Default open, pull back if needed
- Trust is earned: Start cautious, let people prove themselves
- Read the situation: Neither default—assess individually
- Trust systems not people: Rely on structures over character
[multiSelect: false]
# Mission Statement
**Put people first. Prepare for what's coming. Fight anyway.
Find the cracks. Leave no trace.**
---
We operate with systemic pessimism and local optimism.
We hold strong opinions weakly.
We embrace productive paradoxes.
We draw hard lines on human rights.
We extend grace for pain, never for harm.
People first. Always.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.