Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

ss14-atmos

Étoiles0

Forks0

Mis à jour20 mai 2026 à 14:00

Atmospherics guidance for SS14 Shine work, including gas simulation, pipes, vents, scrubbers, air alarms, mapping atmos, flow/reaction design, performance, and why most atmos logic is authoritative/server-side rather than predicted.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

ss14-art

ss14-art/shine

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	ss14-atmos
description	Atmospherics guidance for SS14 Shine work, including gas simulation, pipes, vents, scrubbers, air alarms, mapping atmos, flow/reaction design, performance, and why most atmos logic is authoritative/server-side rather than predicted.

SS14 Atmos

Placement

Most atmos simulation is server-authoritative and belongs in Content.Server/_sh.
Shared data/events may live in Content.Shared/_sh when UI, prediction-adjacent data, or prototypes need it.
Client code is presentation only.

Rules

Do not predict atmos simulation unless a current local pattern proves it is safe.
Avoid per-tick broad scans; use existing atmos update flows.
Keep gas/device behavior configurable through components/prototypes.
For mapping-related atmos, check map/grid/device assumptions.
Use localized UI/examine text.

Bundled References

references/atmos-authority.md: why atmos usually stays server-authoritative and how to split shared data safely.
references/atmos-mapping-checks.md: mapping and prototype checks for pipes, vents, scrubbers, air alarms, and gas assumptions.

Sources

See ss14-wizden-docs for atmos department design, mapping atmos guidance, and transform/physics/grid docs.

Plus depuis ce dépôt

même dépôt

shine-project

ss14-art/shine

Master workflow for working in the Shine Project SS14 fork. Use for any code, content, resource, test, review, or agent-instruction change in this repository, especially Content.Shared, Content.Server, Content.Client, Resources, .agents, CodeRabbit, and fork/upstream merge-sensitive work.

2026-05-200

ss14-ai-workflow

ss14-art/shine

Preflight, implementation, and self-review workflow for AI agents working on Shine Project SS14 code. Use when planning or making any repository change, reviewing PRs, hardening instructions, or deciding which .agents skills/rules apply.

2026-05-200

ss14-audio

ss14-art/shine

Audio guidance for SS14 Shine work, including SoundSpecifier, sound collections, predicted audio, MIDI/soundfonts, resource placement, localization-adjacent feedback, and avoiding duplicated or hardcoded sound playback.

2026-05-200

ss14-chemistry

ss14-art/shine

Chemistry guidance for SS14 Shine work, including reagents, reactions, metabolism, solution containers, reagent effects/conditions, entity solutions, and chemistry prototype localization.

2026-05-200

ss14-client-server-shared

ss14-art/shine

Placement and dependency rules for SS14 Content.Shared, Content.Server, Content.Client, Resources, and tests. Use when deciding where Shine code belongs or when splitting predicted/shared logic from server authority and client presentation.

2026-05-200

ss14-code-style

ss14-art/shine

SS14 C# and YAML code style for Shine Project, including handler naming, dependency naming, Entity generic APIs, On/Try/Can/Do method shape, DataField/ProtoId/Prototype style, localization naming, comments, classes, TimeSpan, and performance guardrails.

2026-05-200

name	ss14-atmos
description	Atmospherics guidance for SS14 Shine work, including gas simulation, pipes, vents, scrubbers, air alarms, mapping atmos, flow/reaction design, performance, and why most atmos logic is authoritative/server-side rather than predicted.

SS14 Atmos

Placement

Most atmos simulation is server-authoritative and belongs in Content.Server/_sh.
Shared data/events may live in Content.Shared/_sh when UI, prediction-adjacent data, or prototypes need it.
Client code is presentation only.

Rules

Do not predict atmos simulation unless a current local pattern proves it is safe.
Avoid per-tick broad scans; use existing atmos update flows.
Keep gas/device behavior configurable through components/prototypes.
For mapping-related atmos, check map/grid/device assumptions.
Use localized UI/examine text.

Bundled References

references/atmos-authority.md: why atmos usually stays server-authoritative and how to split shared data safely.
references/atmos-mapping-checks.md: mapping and prototype checks for pipes, vents, scrubbers, air alarms, and gas assumptions.

Sources

See ss14-wizden-docs for atmos department design, mapping atmos guidance, and transform/physics/grid docs.