specbio
Create speculative organisms for the Ellieworld worldbuilding project. Use whenever designing, inventing, or filling ecological niches with new organisms for this world. Generates structured specs and prose descriptions validated against hard planetary constraints and critiqued for evolutionary plausibility.
What this skill does
# Specbio — Organism Creation for Ellieworld ## Before You Begin Read the project worldbuilding docs to ground yourself. At minimum: - `docs/phylogeny.md` — clade tree and evolutionary logic - `docs/naming-morphemes.md` — taxonomic naming system - `docs/mat-bestiary.md` — detailed organism profiles (the quality bar for output) For deeper context (read as needed): - `docs/ocean-ecology.md` — mat structure, shedding, productivity - `docs/ellieworld.md` — planetary parameters, climate, geography - `docs/plans/2026-02-18-ir-photosynthesis-design.md` — IR photosynthesis biochemistry Read [references/constraints.md](references/constraints.md) for the condensed physical constraints. ## Workflow ### 1. Establish the Niche What ecological role? Specify habitat (mat underside, mat top, mat interior, water column, land, vent, coastal), trophic role (producer, grazer, filter-feeder, predator, parasite, mutualist, scavenger, detritivore), and geographic zone (substellar, day-side, terminator, night-side). ### 2. Place in the Tree Every organism needs a phylogenetic position. Read `docs/phylogeny.md` for the current tree. Placement determines inherited toolkit — an organism can't have capabilities its ancestors never evolved unless convergence is explicitly justified. ### 3. Design the Organism Output format: ```markdown ## [Common Name] — [One-line ecological identity] **Clade:** [phylogenetic position] **Habitat:** [where it lives] **Symmetry:** [inherited or derived, justified if derived] **Size:** [dimensions + mass] **Metabolism:** [energy source] **Skeleton/structure:** [materials, architecture] **Sensory:** [modalities, justified by habitat] **Locomotion:** [mechanism or sessile] **Feeding:** [mechanism, diet, rate] **Reproduction:** [mode, output, timing] **Shedding strategy:** [how it survives, or why it doesn't need to] **Lifespan:** [duration, iteroparity/semelparity] ### Anatomy [Detailed morphological description. Specific dimensions, materials, mechanisms. Match the detail level of docs/mat-bestiary.md entries.] ### Ecology [Interactions: predators, prey, mutualists, competitors. Community-level effects.] ### Life Cycle [Developmental stages, transitions, timing.] ### Evolutionary Notes [What selective pressures shaped this. What ancestral features retained or lost. Why this organism exists.] "[Closing line — poetic, one sentence, in quotes.]" ``` ### 4. Name It Combine morphemes from `docs/naming-morphemes.md`: 2-4 morphemes encoding the most distinctive features + suffix. Common name stays evocative and short. ### 5. Validate Check against physical constraints (see [references/constraints.md](references/constraints.md)): - [ ] No visible light — all vision is IR - [ ] Surface gravity is 1.95g — weight budgets reflect this - [ ] Tidally locked: no day-night cycle, no seasons. Geography IS climate - [ ] Night side: no photosynthesis possible - [ ] 3,100 hPa, 12.9% CO₂ atmosphere - [ ] Ocean mixed layer: 700m, violently convective, no stratification except under mat - [ ] Photic zone ~5m deep (IR absorbed by water) - [ ] Silicic acid, iron, sulfur abundant. Calcium carbonate and chitin absent - [ ] Atmospheric IR windows constrain which wavelengths reach the surface Check against current biology (read the docs for current state): - [ ] Pigment availability matches habitat (water absorbs longer IR) - [ ] Sensory modalities match habitat (vision only where IR-lit) - [ ] Symmetry justified by clade placement - [ ] Shedding strategy exists or organism is expendable - [ ] Mat carrying capacity respected - [ ] Biomaterials are world-appropriate (silica dominant, no Earth-specific materials) - [ ] Body plan consistent with clade's ancestral toolkit ### 6. Critique After validation, assess evolutionary plausibility: - **Selection pressure:** What specific predator, parasite, or constraint drives the distinctive traits? - **Trade-offs:** What does this organism sacrifice? Every adaptation has a cost. - **Failure modes:** How does it die? What kills most individuals? - **Competitive exclusion:** Why doesn't an existing organism already fill this niche? - **Convergence check:** If it resembles an Earth organism, justify why similar physics/ecology produces similar solutions — or revise. - **Weaknesses:** 2-3 specific vulnerabilities. ## Style Notes Match the voice of `docs/mat-bestiary.md`: scientifically rigorous, mechanistically specific, with a closing poetic line in quotes. Dimensions in metric. Biological detail should be concrete enough that someone could build a simulation from it.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.