Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

ss14-client-server-shared

Estrelas0

Forks0

Atualizado20 de maio de 2026 às 14:00

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ss14-art

ss14-art/shine

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

5 arquivos

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 Shine code belongs or when splitting predicted/shared logic from server authority and client presentation.

SS14 Client Server Shared

Placement Decisions

Content.Shared/_sh: predicted gameplay, shared components, network event definitions, shared public APIs, data used by both sides.
Content.Server/_sh: authority-only logic, persistence, admin/server services, systems impossible to predict.
Content.Client/_sh: UI, visualizers, overlays, client-only presentation, client BUI windows.
Resources/_sh: 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-_sh files only for integration points and mark those edits.

Mais deste repositório

mesmo repositório

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-atmos

ss14-art/shine

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.

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-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-client-server-shared
description	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.

SS14 Client Server Shared

Placement Decisions

Content.Shared/_sh: predicted gameplay, shared components, network event definitions, shared public APIs, data used by both sides.
Content.Server/_sh: authority-only logic, persistence, admin/server services, systems impossible to predict.
Content.Client/_sh: UI, visualizers, overlays, client-only presentation, client BUI windows.
Resources/_sh: 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-_sh files only for integration points and mark those edits.