Run any Skill in Manus with one click

ss14-client-server-shared

Stars3

Forks7

UpdatedMay 23, 2026 at 21:36

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ss14-art

ss14-art/ss14-core

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

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

SS14 Client Server Shared

Placement Decisions

Content.Shared/_Art: predicted gameplay, shared components, network event definitions, shared public APIs, data used by both sides.
Content.Server/_Art: authority-only logic, persistence, admin/server services, systems impossible to predict.
Content.Client/_Art: UI, visualizers, overlays, client-only presentation, client BUI windows.
Resources/_Art: prototypes, maps, audio, textures, localization.
Tests go in Content.Tests or Content.IntegrationTests based on scope.

Dependency Direction

Shared cannot depend on Server or Client.
Server and Client may depend on Shared.
Client code is never authoritative.
Server must validate client-origin actions.

Bundled References

references/client-server-primer.md: assembly responsibilities and dependency direction.
references/shared-and-prediction.md: shared abstract systems, client/server derived systems, and predicted split choices.
references/networking-and-dirty.md: dirtying, component state, and server validation reminders.

Predicted Split Pattern

When a system needs side-specific code:

Put common logic in an abstract shared system.
Inherit from it on server and client.
Add an empty client system if needed so shared predicted logic runs client-side.

Upstream Files

Touch non-_Art files only for integration points and mark those edits.

More from this repository

same repository

ss14-ai-workflow

ss14-art/ss14-core

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.

2026-06-183

ss14-art-core

ss14-art/ss14-core

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.

2026-06-183

ss14-porting-and-licensing

ss14-art/ss14-core

Porting, attribution, fork isolation, upstream merge, and license guidance for SS14-ART-CORE. Use before importing code/assets from WizDen, Delta-V, Starlight,

2026-06-183

ss14-prototype-basics

ss14-art/ss14-core

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.

2026-06-183

ss14-upstream-maintenance

ss14-art/ss14-core

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.

2026-06-183

ss14-wizden-docs

ss14-art/ss14-core

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.

2026-06-183

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

SS14 Client Server Shared

Placement Decisions

Content.Shared/_Art: predicted gameplay, shared components, network event definitions, shared public APIs, data used by both sides.
Content.Server/_Art: authority-only logic, persistence, admin/server services, systems impossible to predict.
Content.Client/_Art: UI, visualizers, overlays, client-only presentation, client BUI windows.
Resources/_Art: prototypes, maps, audio, textures, localization.
Tests go in Content.Tests or Content.IntegrationTests based on scope.

Dependency Direction

Shared cannot depend on Server or Client.
Server and Client may depend on Shared.
Client code is never authoritative.
Server must validate client-origin actions.

Bundled References

references/client-server-primer.md: assembly responsibilities and dependency direction.
references/shared-and-prediction.md: shared abstract systems, client/server derived systems, and predicted split choices.
references/networking-and-dirty.md: dirtying, component state, and server validation reminders.

Predicted Split Pattern

When a system needs side-specific code:

Put common logic in an abstract shared system.
Inherit from it on server and client.
Add an empty client system if needed so shared predicted logic runs client-side.

Upstream Files

Touch non-_Art files only for integration points and mark those edits.