metabolic-cultures
Design cultures for closed-loop life support systems in space. Use when worldbuilding stations, ships, or habitats where recycled matter creates novel social structures, beliefs, and conflicts.
What this skill does
# Metabolic Cultures: Closed-Loop Society Skill You help writers develop distinct cultures for closed-loop life support systems in space. The framework explores how the physical reality of recycled air, water, and biomass creates novel social structures, beliefs, and conflicts that diverge from planetary norms. ## Core Principle: Matter as Identity **In closed-loop systems, the distinction between self and community dissolves at the molecular level.** Within months, individuals literally become their community through metabolic exchange. This creates **metabolic kinship**—a form of belonging more fundamental than genetics. ## The Five Axes of Cultural Development ### 1. Integration Philosophy How does the culture interpret metabolic mixing? **Spectrum Positions**: | Position | Description | |----------|-------------| | **Purist** | Tracking every molecule, multi-generational natives hold power, minimal external contact | | **Synthesis** | Deliberate mixing from multiple sources, diversity as strength, open borders | | **Pragmatic** | Managed exchange based on necessity, professional boundaries, modular systems | | **Amnesiac** | Deliberately forgotten tracking, discomfort with metabolic identity, focus on other markers | **Design Questions**: - Does the culture see foreign matter as contamination or enrichment? - How precisely do they track metabolic exchange? - What percentage of foreign matter makes someone "other"? - Can synthetic matter ever become "real" through integration? ### 2. Temporal Dynamics How does the culture handle metabolic change over time? **Key Timeframes**: | Timeframe | Scope | |-----------|-------| | **Immediate** (hours-days) | Air exchange, breathing protocols | | **Short-term** (weeks-months) | Food/water integration, visitor policies | | **Medium-term** (years) | Cellular replacement, citizenship thresholds | | **Long-term** (decades) | Full metabolic turnover, generational changes | | **Eternal** (post-death) | Matter recycling, legacy concepts | **Design Questions**: - How long before someone is considered integrated? - What rights come with different levels of integration? - How does the culture mark metabolic milestones? - What happens to those who leave and return? ### 3. Boundary Management How does the culture handle interfaces with others? **Interface Types**: | Type | Examples | |------|----------| | **Physical** | Airlocks, quarantine zones, neutral territories | | **Social** | Interaction protocols, breathing etiquette, touch taboos | | **Economic** | Trade regulations, labor stratification, service provisions | | **Political** | Treaties, ambassadorial exchange, war implications | **Design Questions**: - Where and how do different metabolic groups interact? - What technologies mediate these interactions? - How does commerce override or reinforce boundaries? - What happens at mixed-metabolism gatherings? ### 4. Death and Continuity How does the culture understand mortality and legacy? **Death Concepts**: | Concept | Meaning | |---------|---------| | **Return Obligation** | Death as repayment of borrowed matter | | **Distribution Rights** | Who has claim to the deceased's matter? | | **Distance Complications** | Dying away from home loop | | **Preservation Taboos** | Keeping matter from the cycle | **Design Questions**: - Is death seen as individual ending or communal transaction? - How are the absent-dead handled? - What constitutes proper vs improper body handling? - How does distance from home affect death rights? ### 5. Power Structures Who controls metabolic decisions and why? **Authority Sources**: | Source | Basis | |--------|-------| | **Generational Depth** | Time in-loop as political capital | | **Technical Control** | Life support system operators | | **Economic Leverage** | Those who manage external interfaces | | **Religious/Philosophical** | Interpreters of metabolic meaning | | **Practical Necessity** | Those keeping systems functional | **Design Questions**: - Who decides integration policies? - How is metabolic deviance punished? - What creates metabolic class distinctions? - How do power structures resist or embrace change? ## Culture Generation Process ### Step 1: Choose Position on Each Axis Rate each axis on a 1-5 scale: 1. Integration Philosophy (Purist 1 ← → 5 Synthesis) 2. Temporal Rigidity (Strict 1 ← → 5 Fluid) 3. Boundary Permeability (Closed 1 ← → 5 Open) 4. Death Orthodoxy (Traditional 1 ← → 5 Innovative) 5. Power Concentration (Centralized 1 ← → 5 Distributed) ### Step 2: Identify Tension Points Where do positions create internal contradictions? - Open boundaries but strict integration timelines? - Synthesis philosophy but concentrated power? - Fluid boundaries but orthodox death practices? These tensions generate your most interesting conflicts and story opportunities. ### Step 3: Develop Practical Expressions **Daily Life Manifestations**: - Breathing protocols (conscious, unconscious, ritualized) - Eating customs (communal, isolated, timed) - Sleep arrangements (shared air, private chambers) - Work segregation (by integration level, by origin) **Milestone Markers**: - Birth practices (debt acknowledgment, matter blessing) - Coming of age (first full breath, integration ceremony) - Partnership forms (metabolic mingling, maintained separation) - Professional advancement (tied to integration, independent) **Crisis Responses**: - Contamination events (panic, acceptance, investigation) - Resource shortages (rationing by integration, equal distribution) - External threats (unity response, fragment by origin) - System failures (technical fix, social reorganization) ### Step 4: Create Unique Innovations **Language Elements**: - Terms for different integration levels - Metaphors based on metabolic reality - Insults and compliments unique to the culture - Untranslatable concepts **Technology Adaptations**: - Integration tracking methods - Boundary management tools - Death handling systems - Communication protocols **Social Structures**: - Family forms beyond genetics - Professional hierarchies - Educational systems - Conflict resolution methods ### Step 5: Project Historical Development Consider how the culture reached its current state: - Founding principles and how they evolved - Crisis points that shaped current practices - Schisms and reunifications - External influences and rejections ## Interaction Modeling When cultures meet, compare positions on each axis: **Harmony Points** (similar positions): - Potential for alliance or merger - Shared understanding despite other differences - Trade opportunities **Friction Points** (opposite positions): - Source of conflicts and misunderstandings - Barriers to cooperation - Potential for exploitation **Translation Needs** (different but not opposite): - Require cultural interpreters - Create specialist roles - Generate innovation through synthesis ## Story Seed Generator **Character Types × Cultural Positions × Transition States**: - The orthodox purist visiting a synthesis station - The merchant child choosing a permanent home - The death-returner racing against metabolic change - The translator who belongs nowhere fully **Conflict Categories**: | Category | Type | |----------|------| | **Personal** | Individual desire vs cultural mandate | | **Generational** | Youth rebellion against metabolic traditions | | **Inter-cultural** | Incompatible worldviews forced to interact | | **Existential** | Challenges to the culture's survival | | **Philosophical** | New ideas challenging old certainties | ## Quick Culture Templates ### The Orthodox Loop - Integration: 1 (Purist) - Temporal: 1 (Strict) - Boundaries: 1 (Closed) - Death: 1 (Traditional) - Power: 2 (Concentrated) - **Story Focus**: Purity vs contamination, exile horror, generational power ### The Frontier Mixer - Integration: 5 (Synthesis) - Temporal: 4 (Fluid) - Boundaries: 5 (Open) - Death: 3 (Balanced) - Power: 4 (Distributed) - **Story
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.