Run any Skill in Manus with one click

ss14-porting-and-licensing

Stars0

Forks0

UpdatedMay 20, 2026 at 14:00

Porting, attribution, fork isolation, upstream merge, and license guidance for Shine Project. Use before importing code/assets from WizDen, Delta-V, other SS14 forks, tgstation, assets, or external repositories, and before modifying upstream files.

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	ss14-porting-and-licensing
description	Porting, attribution, fork isolation, upstream merge, and license guidance for Shine Project. Use before importing code/assets from WizDen, Delta-V, other SS14 forks, tgstation, assets, or external repositories, and before modifying upstream files.

SS14 Porting And Licensing

Before Porting

Identify source repository, commit, original author, and license.
Check whether code/assets are MIT, AGPL, MPL, CC-BY-SA, CC-BY-NC-SA, or another license.
Do not import incompatible assets or hidden-source-incompatible code.
Preserve attribution in metadata, comments, or license files as appropriate.

Fork Isolation

Put new Shine code/assets under _sh.
Namespace serialized types and prototype IDs with a Shine prefix.
Avoid changing upstream files. If required, use tight shine-edit markers.
Preserve path similarity under _sh so upstream equivalents are easy to compare.

Database Porting

Avoid modifying upstream tables.
Prefer one-to-one fork-owned tables for Shine-only data.
Namespace migrations.
Test SQLite and Postgres paths when persistence changes.

Bundled References

references/source-license-checklist.md: source, commit, author, license, compatibility, and import decision checks.
references/attribution-patterns.md: code, asset, RSI, station image, and generic attribution placement.

Sources

See ss14-wizden-docs for forking tips, PRs with engine changes, generic attribution, station image specs, and PR guidelines.

More from this repository

same repository

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

name	ss14-porting-and-licensing
description	Porting, attribution, fork isolation, upstream merge, and license guidance for Shine Project. Use before importing code/assets from WizDen, Delta-V, other SS14 forks, tgstation, assets, or external repositories, and before modifying upstream files.

SS14 Porting And Licensing

Before Porting

Identify source repository, commit, original author, and license.
Check whether code/assets are MIT, AGPL, MPL, CC-BY-SA, CC-BY-NC-SA, or another license.
Do not import incompatible assets or hidden-source-incompatible code.
Preserve attribution in metadata, comments, or license files as appropriate.

Fork Isolation

Put new Shine code/assets under _sh.
Namespace serialized types and prototype IDs with a Shine prefix.
Avoid changing upstream files. If required, use tight shine-edit markers.
Preserve path similarity under _sh so upstream equivalents are easy to compare.

Database Porting

Avoid modifying upstream tables.
Prefer one-to-one fork-owned tables for Shine-only data.
Namespace migrations.
Test SQLite and Postgres paths when persistence changes.

Bundled References

references/source-license-checklist.md: source, commit, author, license, compatibility, and import decision checks.
references/attribution-patterns.md: code, asset, RSI, station image, and generic attribution placement.

Sources

See ss14-wizden-docs for forking tips, PRs with engine changes, generic attribution, station image specs, and PR guidelines.