원클릭으로 Manus에서 모든 스킬 실행

ss14-ui-eui

스타2

포크12

업데이트2026년 4월 21일 17:03

Work with SS14 EUI flows, `BaseEui`, `EuiStateBase`, `EuiMessageBase`, admin/debug windows, EUI state serialization, and client/server EUI message handling.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ss14-art

ss14-art/open-space

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

SS14 EUI

Use this skill for engine-style EUI windows, especially admin and debug tools.

EUI is for explicit client/server UI sessions. Keep messages typed, state minimal, permission-sensitive behavior server-authoritative, and windows tolerant of close/reopen cycles.

Workflow

Map the EUI chain.

Client: BaseEui, window/control, HandleState, and SendMessage.
Shared: state and message types when both sides need the contract.
Server: session setup, permission checks, state construction, and message handling.

Keep authority server-side.

Validate permissions and target entities on the server for admin/debug actions.
Treat client messages as requests, not proof that an action is allowed.
Avoid sending sensitive data unless the viewer is authorized.

Keep state and messages small.

Send IDs, summaries, and requested page data instead of huge object graphs.
Use NetEntity or stable identifiers for entities crossing the wire.
Handle stale targets, disconnects, and windows closing.

Pair EUI with XAML carefully.

Use ss14-ui-xaml for window layout and localized text.
Keep EUI message/state logic out of code-behind when a system can own it.

Validate with the real role.

Admin/debug EUI needs permission-aware runtime testing when possible.
Call out when the UI was built but not exercised in-game.

Reference Map

../ss14-ui-xaml/SKILL.md
../ss14-netcode/SKILL.md
../ss14-localization-strings/SKILL.md
../ss14-debugging-workflow/SKILL.md

Good File Anchors

Content.Client/**/*Eui.cs
Content.Server/**/*Eui.cs
Content.Shared/**/*Eui*.cs
Content.Client/Administration/UI/**

Common Pitfalls

Trusting client EUI messages for admin actions.
Sending too much state every update.
Forgetting close and stale-entity paths.
Mixing BUI and EUI patterns without a reason.

이 저장소의 다른 Skills

같은 저장소

ss14-upstream-maintenance

ss14-art/open-space

Safely maintain a forked SS14 codebase with minimal upstream churn. Use when deciding whether to edit upstream files, when extending behavior in `_OpenSpace`, when preserving path similarity, or when avoiding unnecessary changes to RobustToolbox and offs content.

2026-05-112

ss14-atmos

ss14-art/open-space

Work with SS14 atmospherics, gases, gas mixtures, fire, pressure, pipes, vents, pumps, scrubbers, air alarms, atmos overlays, and atmos-related prototypes or UI.

2026-04-212

ss14-audio

ss14-art/open-space

Work with SS14 audio systems, sound specifiers, sound collections, ambient or lobby music, jukeboxes, predicted sound feedback, or audio assets under `Resources/Audio` and `Resources/Prototypes/SoundCollections`.

2026-04-212

ss14-databases-migrations

ss14-art/open-space

Work with SS14 server database models, EF Core DbContexts, SQLite/Postgres migrations, persistence services, admin/player data storage, and schema compatibility.

2026-04-212

ss14-npc-ai

ss14-art/open-space

Work with SS14 NPC systems, HTN behavior, pathfinding, steering, AI debug overlays, mindless mobs, hostile or friendly mob behavior, and NPC-related prototypes.

2026-04-212

ss14-pvs

ss14-art/open-space

Work with SS14 PVS, visibility, network interest, PVS filters, PVS override behavior, visibility-dependent audio or popups, zoom PVS scale, or systems that behave differently when entities leave PVS.

2026-04-212

name	ss14-ui-eui
description	Work with SS14 EUI flows, `BaseEui`, `EuiStateBase`, `EuiMessageBase`, admin/debug windows, EUI state serialization, and client/server EUI message handling.

SS14 EUI

Use this skill for engine-style EUI windows, especially admin and debug tools.

EUI is for explicit client/server UI sessions. Keep messages typed, state minimal, permission-sensitive behavior server-authoritative, and windows tolerant of close/reopen cycles.

Workflow

Map the EUI chain.

Client: BaseEui, window/control, HandleState, and SendMessage.
Shared: state and message types when both sides need the contract.
Server: session setup, permission checks, state construction, and message handling.

Keep authority server-side.

Validate permissions and target entities on the server for admin/debug actions.
Treat client messages as requests, not proof that an action is allowed.
Avoid sending sensitive data unless the viewer is authorized.

Keep state and messages small.

Send IDs, summaries, and requested page data instead of huge object graphs.
Use NetEntity or stable identifiers for entities crossing the wire.
Handle stale targets, disconnects, and windows closing.

Pair EUI with XAML carefully.

Use ss14-ui-xaml for window layout and localized text.
Keep EUI message/state logic out of code-behind when a system can own it.

Validate with the real role.

Admin/debug EUI needs permission-aware runtime testing when possible.
Call out when the UI was built but not exercised in-game.

Reference Map

../ss14-ui-xaml/SKILL.md
../ss14-netcode/SKILL.md
../ss14-localization-strings/SKILL.md
../ss14-debugging-workflow/SKILL.md

Good File Anchors

Content.Client/**/*Eui.cs
Content.Server/**/*Eui.cs
Content.Shared/**/*Eui*.cs
Content.Client/Administration/UI/**

Common Pitfalls

Trusting client EUI messages for admin actions.
Sending too much state every update.
Forgetting close and stale-entity paths.
Mixing BUI and EUI patterns without a reason.