メニュー
Atmospherics guidance for SS14 SS14-ART-CORE 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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Preflight, implementation, and self-review workflow for AI agents working on SS14-ART-CORE SS14 code. Use when planning or making any repository change, reviewing PRs, hardening instructions, or deciding which .agents skills/rules apply.
Master workflow for working in the SS14-ART-CORE 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.
Porting, attribution, fork isolation, upstream merge, and license guidance for SS14-ART-CORE. Use before importing code/assets from WizDen, Delta-V, Starlight,
SS14 YAML prototype, data field, localization, guidebook, entity table, reagent, and resource placement guidance. Use when editing Resources, prototypes, FTL, YAML, entity definitions, components serialized to YAML, or guidebook entries.
Upstream/fork maintenance guidance for SS14-ART-CORE. Use when touching non-_Art files, reviewing upstream diffs, preserving path similarity, porting fork code, marking ss14-art-edit blocks, or deciding whether an engine/content change is allowed.
Route and summarize the local WizDen documentation snapshot for SS14-ART-CORE SS14 work. Use when an agent needs SS14/RobustToolbox docs context for ECS, prediction, networking, UI, prototypes, mapping, departments, design docs, rendering, toolshed, setup, debugging, porting, or licensing.
| name | ss14-atmos |
| description | Atmospherics guidance for SS14 SS14-ART-CORE 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. |
Content.Server/_Art.Content.Shared/_Art when UI, prediction-adjacent data, or prototypes need it.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.See ss14-wizden-docs for atmos department design, mapping atmos guidance, and transform/physics/grid docs.