Run any Skill in Manus with one click

shine-project

Stars0

Forks0

UpdatedMay 20, 2026 at 14:00

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.

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/shine

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

4 files

SKILL.md

readonly

name	shine-project
description	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.

Shine Project

This is the root skill for Shine Project. Use it first, then load narrower SS14 skills only as needed.

Required Preflight

Read .agents/rules/shine-hard-guardrails.md.
Read .agents/rules/shine-upstream-edit-markers.md.
Read .agents/rules/ss14-skill-preflight-and-refresh.md.
Identify affected assemblies and load the matching skills.
Search the repo for current patterns before coding.

Bundled References

references/preflight-checklist.md: quick checklist before editing code, resources, tests, or agent instructions.
references/shine-path-map.md: where Shine-owned C#, YAML, FTL, assets, tests, and configs belong.

Hard Rules

Never edit RobustToolbox/**.
Put new Shine-only code under _sh.
Wrap every change outside _sh in a narrow marker block:

// shine-edit start: reason
CODE
// shine-edit end

Keep mechanics modular and data-driven.
Do not duplicate existing mechanics.
Do not hardcode when a prototype, CVar, ProtoId<T>, DataField, SoundSpecifier, SpriteSpecifier, or localization key can express the behavior.
Use .NET 10-current APIs by checking global.json, package versions, local code, and official docs when framework details matter.

Work Shape

Prefer this order:

Understand existing implementation.
Decide whether the change belongs in Shared, Server, Client, Resources, or tests.
Add fork-only code under _sh.
Touch upstream files only for integration points and mark them.
Add localization and prototypes with namespaced IDs.
Validate with the narrowest useful command.
Review the diff against .agents/rules/ss14-review-checklist.md.

Skill Routing

Use .agents/rules/ss14-skill-preflight-and-refresh.md for exact routing. Common pairings:

Gameplay feature: ss14-ecs-basics, ss14-client-server-shared, ss14-networking-prediction, ss14-prototype-basics.
UI: ss14-ui-xaml, ss14-ui-bui or ss14-ui-eui.
Resources: ss14-prototype-basics, ss14-sprite-rendering, ss14-audio.
Persistence: ss14-databases-migrations.
Review bot work: ss14-ai-workflow, ss14-code-style, ss14-testing.

More from this repository

same repository

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

ss14-art/shine

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.

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	shine-project
description	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.

Shine Project

This is the root skill for Shine Project. Use it first, then load narrower SS14 skills only as needed.

Required Preflight

Read .agents/rules/shine-hard-guardrails.md.
Read .agents/rules/shine-upstream-edit-markers.md.
Read .agents/rules/ss14-skill-preflight-and-refresh.md.
Identify affected assemblies and load the matching skills.
Search the repo for current patterns before coding.

Bundled References

references/preflight-checklist.md: quick checklist before editing code, resources, tests, or agent instructions.
references/shine-path-map.md: where Shine-owned C#, YAML, FTL, assets, tests, and configs belong.

Hard Rules

Never edit RobustToolbox/**.
Put new Shine-only code under _sh.
Wrap every change outside _sh in a narrow marker block:

// shine-edit start: reason
CODE
// shine-edit end

Keep mechanics modular and data-driven.
Do not duplicate existing mechanics.
Do not hardcode when a prototype, CVar, ProtoId<T>, DataField, SoundSpecifier, SpriteSpecifier, or localization key can express the behavior.
Use .NET 10-current APIs by checking global.json, package versions, local code, and official docs when framework details matter.

Work Shape

Prefer this order:

Understand existing implementation.
Decide whether the change belongs in Shared, Server, Client, Resources, or tests.
Add fork-only code under _sh.
Touch upstream files only for integration points and mark them.
Add localization and prototypes with namespaced IDs.
Validate with the narrowest useful command.
Review the diff against .agents/rules/ss14-review-checklist.md.

Skill Routing

Use .agents/rules/ss14-skill-preflight-and-refresh.md for exact routing. Common pairings:

Gameplay feature: ss14-ecs-basics, ss14-client-server-shared, ss14-networking-prediction, ss14-prototype-basics.
UI: ss14-ui-xaml, ss14-ui-bui or ss14-ui-eui.
Resources: ss14-prototype-basics, ss14-sprite-rendering, ss14-audio.
Persistence: ss14-databases-migrations.
Review bot work: ss14-ai-workflow, ss14-code-style, ss14-testing.