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

ss14-ui-xaml

스타2

포크12

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

Work with SS14 XAML windows, controls, `.xaml.cs` code-behind, UI layout, style classes, localized UI text, FancyWindow patterns, and client-side UI widgets.

설치

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

Manus에서 실행

출처

ss14-art

ss14-art/open-space

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

다운로드

Manus에서 실행

SS14 XAML UI

Use this skill for XAML-first client UI layout and code-behind.

XAML should describe layout and stable widgets; code-behind should bind state, events, and formatting without becoming gameplay logic.

Workflow

Find the existing UI family.

Reuse nearby FancyWindow, control, style, and code-behind patterns.
Keep .xaml and .xaml.cs paired and named consistently.
Prefer extending existing controls over creating one-off layouts.

Keep layout declarative.

Put structure, margins, containers, and named controls in XAML.
Keep event wiring, state application, and formatting in code-behind.
Do not build an entire window imperatively in C# when XAML is practical.

Localize visible text.

Use Loc bindings or localized code-behind strings for titles, labels, buttons, tooltips, and empty states.
Do not commit hardcoded player-facing UI text.

Respect UI ownership.

XAML and code-behind are client presentation.
BUI/EUI state and messages belong in their own skills; load them when the window is backed by networked UI state.

Validate the UI path.

Build client code after code-behind edits.
Run or inspect the UI in-game when practical, especially for dynamic lists and narrow windows.

Reference Map

../ss14-ui-bui/SKILL.md
../ss14-ui-eui/SKILL.md
../ss14-localization-strings/SKILL.md
../ss14-localization-code/SKILL.md

Good File Anchors

Content.Client/**/*.xaml
Content.Client/**/*.xaml.cs
Content.Client/**/UI/**
Content.Client/**/Styles/**

Common Pitfalls

Constructing full windows in C# instead of XAML.
Hardcoding UI text.
Adding global style changes for one window.
Putting gameplay decisions in code-behind instead of systems or UI message handlers.

이 저장소의 다른 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-xaml
description	Work with SS14 XAML windows, controls, `.xaml.cs` code-behind, UI layout, style classes, localized UI text, FancyWindow patterns, and client-side UI widgets.

SS14 XAML UI

Use this skill for XAML-first client UI layout and code-behind.

XAML should describe layout and stable widgets; code-behind should bind state, events, and formatting without becoming gameplay logic.

Workflow

Find the existing UI family.

Reuse nearby FancyWindow, control, style, and code-behind patterns.
Keep .xaml and .xaml.cs paired and named consistently.
Prefer extending existing controls over creating one-off layouts.

Keep layout declarative.

Put structure, margins, containers, and named controls in XAML.
Keep event wiring, state application, and formatting in code-behind.
Do not build an entire window imperatively in C# when XAML is practical.

Localize visible text.

Use Loc bindings or localized code-behind strings for titles, labels, buttons, tooltips, and empty states.
Do not commit hardcoded player-facing UI text.

Respect UI ownership.

XAML and code-behind are client presentation.
BUI/EUI state and messages belong in their own skills; load them when the window is backed by networked UI state.

Validate the UI path.

Build client code after code-behind edits.
Run or inspect the UI in-game when practical, especially for dynamic lists and narrow windows.

Reference Map

../ss14-ui-bui/SKILL.md
../ss14-ui-eui/SKILL.md
../ss14-localization-strings/SKILL.md
../ss14-localization-code/SKILL.md

Good File Anchors

Content.Client/**/*.xaml
Content.Client/**/*.xaml.cs
Content.Client/**/UI/**
Content.Client/**/Styles/**

Common Pitfalls

Constructing full windows in C# instead of XAML.
Hardcoding UI text.
Adding global style changes for one window.
Putting gameplay decisions in code-behind instead of systems or UI message handlers.