Structure multi-POV stories through catalyst environments. Use when building interconnected narratives, when perspectives need meaningful intersection, or when a shared setting needs to generate distinct storylines.
npx skills add https://github.com/jwynia/agent-skills --skill perspectival-constellation
You help writers create multi-perspective stories where a shared catalyst environment generates genuinely distinct but interconnected narratives. The key insight is that the setting itself must function as a transformation pressure that forces characters into heightened states.
The shared thread (place, event, institution, moment) must function as a catalyst environment that creates conditions where people are forced into states of change, vulnerability, or heightened stakes.
This generates enough narrative potential density to sustain multiple distinct storylines that remain authentically connected.
Effective catalysts create:
Geographic Liminality:
Temporal Liminality:
Social Liminality:
Life/Death Proximity:
Identity Transformation Points:
Economic Survival Pressure:
Forced Proximity Systems:
Professional Mask-Slip Zones:
Simultaneous Perspectives:
Sequential Handoffs:
Recursive Revelations:
Awareness Gradients:
Knowledge Asymmetries:
Transformation Pressure Check:
Narrative Sustainability Test:
Diversity Potential Analysis:
Individual Story Integrity:
Interconnection Authenticity:
Use the Pressure Point Mapping method:
context/output-config.md in the projectstories/structure/ or explorations/stories/Pattern: {story-name}-constellation-{date}.md
context/output-config.md{story-name}-constellation-{date}.mdTrigger phrases: "design the complete constellation", "optimize revelation order", "map all intersections"
| Task | Agent Type | When to Spawn |
|------|------------|---------------|
| Setting research | general-purpose | When modeling catalyst on real environments |
| Character development | general-purpose | When deepening individual perspectives |
Pattern: Characters meet or affect each other in ways that don't follow logically from the catalyst environment's structure.
Why it fails: The power of perspectival constellation is that connections feel structurally inevitable. When intersections are contrived, readers sense authorial manipulation rather than organic collision.
Fix: Map how the catalyst environment naturally creates interaction opportunities. Who would share waiting rooms? Who processes whose paperwork? Let structural logic, not plot convenience, drive connection.
Pattern: Treating all perspectives as equally important, giving each the same space and emphasis.
Why it fails: Not all positions in a catalyst environment have equal narrative potential. Forcing equality creates filler perspectives or stretches thin material. Some characters are full novels; others are short stories.
Fix: Let perspectives earn their weight through the transformation pressure they experience. A nurse during a crisis might carry more narrative potential than a visitor. Match space to story density.
Pattern: Characters knowing more or less than their position would allow—either mysteriously informed or artificially ignorant.
Why it fails: Information asymmetry is where multi-POV drama lives. When characters have convenient knowledge or ignorance, the perspective structure feels arbitrary rather than illuminating.
Fix: Map what each position would actually know. The receptionist hears fragments; the doctor sees records; the patient knows their own pain. Authentic asymmetry creates discovery through perspective shift.
Pattern: Perspectives intersect only to advance plot mechanics—passing information, providing assistance, creating obstacles.
Why it fails: The best perspective connections should matter to both characters independently. When one character exists only to serve another's plot, that perspective feels hollow.
Fix: Ensure intersections are meaningful to all perspectives involved. The brief encounter that's a turning point for one character might be just background for another, but both should have their own stake in the moment.
Pattern: Choosing settings that gather people together but don't force them into heightened states—pleasant cafes, ordinary workplaces, casual gatherings.
Why it fails: Without transformation pressure, perspectives become slice-of-life snapshots rather than revelatory windows. The catalyst must force masks to drop and stakes to matter.
Fix: Apply the transformation pressure test. Does this environment force people out of their normal patterns? If everyone could walk away unchanged, the catalyst is too weak.
| Skill | What it provides |
|-------|------------------|
| statistical-distance | Characters at statistical edge rather than center |
| positional-revelation | How positions create structural access and involvement |
| settlement-design | Physical environments where perspectives can intersect |
| Skill | What this provides |
|-------|-------------|
| scene-sequencing | Structure for multi-thread narrative pacing |
| dialogue | Distinct voices for each perspective |
| endings | Resolution patterns for interconnected story threads |
| Skill | Relationship |
|-------|--------------|
| positional-revelation | Perspectival-constellation uses shared environments; positional-revelation creates individual structural access. Use together for multi-POV stories with structurally-inevitable involvement |
| statistical-distance | Both push against default character types—apply statistical-distance to each perspective to avoid stock types gathering in your catalyst environment |
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take jwynia/perspectival-constellation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.