create-stellar-system
Create Stellar System
Design a stellar system that is internally consistent with basic orbital and thermal physics. Keep outputs clear, structured, and reusable for downstream lore or simulation work.
Workflow
- Define the central star and its primary constraints.
- Establish orbital architecture and stability rules.
- Map thermal zones and energy flows.
- Assign plausible planetary compositions by orbital region.
- Produce a final system sheet using the output template.
1) Stellar Core Logic
The star is the primary gravitational and thermal driver.
- Choose classification (for example, M-class dwarf or G-class main sequence).
- Estimate luminosity/flux behavior across AU distances.
- Note stellar wind and magnetosphere pressure to inform atmospheric stripping and auroral intensity.
- Identify the likely habitable zone and rough frost line.
2) Orbital Mechanics And Stability
All major bodies must satisfy long-term stability assumptions.
- Compute or estimate the tidal locking radius from stellar mass.
- Set eccentricity targets:
- Low (
e < 0.01) for stable, near-circular orbits. - Higher (
e > 0.1) only with explicit perturbation causes (resonance forcing, collisions, shepherd masses).
- Low (
- Use orbital resonances (for example, 2:1 or 3:2) to justify compact multi-body systems.
3) Thermal Gradient And Energy Budget
Model the system as heat flow from source to sink.
- Primary source: stellar radiation.
- Secondary sources: tidal heating, radiogenic decay, residual contraction, or exotic sources if justified.
- Sinks: albedo reflection, atmospheric transport, radiation to space, or other setting-specific sinks.
- Place the frost line where volatile compounds can condense.
4) Planetary Compositional Logic
Tie composition to formation zone and migration history.
- Inner refractory zone: iron, nickel, silicates, dense rocky bodies.
- Outer volatile zone: ices and gas-rich compositions (
H2O,CO2,H2,He,N2,CH4,NH3,H2S,PH3, ...). - Include accretion dynamics: massive shepherd bodies can clear disk gaps and create ring/belt structure.
5) Triple Observational Standard
For complete mapping, describe system observations from three vantage points:
- Perihelion Watch: high-energy/star-proximal phenomena.
- Median Watch: temperate-zone traffic, intersections, and stable operations.
- Aphelion Watch: deep-system anomalies and boundary dynamics.
Output Template
Use this template for each major body:
### [Object Name]
- **Classification:** (Terrestrial / Metallic / Gas Giant / Ice Giant / Singularity)
- **Mass:** [Value in Earth masses or kg]
- **Diameter (average):** [X] m or km
- **Semi-Major Axis:** [X] AU
- **Orbital Period:** [X] Earth Years
- **Orbital Speed (average):** [X] km/s
- **Eccentricity (e):** [X.XXX]
- **Tidal Status:** (Locked / Resonant / Asynchronous)
- **Rotation Period:** [X] Hours or Days
- **Axial Tilt:** [X] Degrees
- **Surface Gravity:** [X] g
- **Hill Sphere Radius:** [X] km or AU
- **Surface Temperature (average):** [X] K
- **Atmospheric Profile:** [Pressure in bars] / [Chemical composition]
- **Geological Activity:** (Tectonic / Cryovolcanic / Inert)
- **Chemical Composition:** (for example, heavy metals, liquid hydrocarbons, rare isotopes)
Quality Checks
Before finalizing, verify:
- Every body's orbit is physically plausible with the defined star mass.
- Thermal zones match star output and orbital distances.
- Composition matches formation region or clearly documented migration history.
- The final write-up uses consistent units and terminology.
More from lfortin/skills
setup-os-monitor
Install and configure the Node.js `os-monitor` package, including legacy-version fallback, threshold tuning, event handlers, stream mode, and validation. Use this skill whenever the user asks to set up OS/system monitoring in Node.js, wire alerts for memory/load/disk/uptime, or integrate `os-monitor` into an app, even if they do not explicitly mention the package name.
10setup-cgi-core
Install and configure the Node.js `cgi-core` package to host CGI scripts via CLI or middleware for HTTP server, including interpreter mappings, buffer/timeouts, status pages, env injection, and proxy-safe `trustProxy` usage. Use this skill whenever users need to run legacy CGI scripts (Perl, Python, Bash, Node, etc.) in a modern Node setup, replace Apache for lightweight CGI hosting, or wire `/cgi-bin` routing in local/dev environments.
9