Run any Skill in Manus with one click

ss14-databases-migrations

Stars0

Forks0

UpdatedMay 20, 2026 at 14:00

Database and EF Core migration guidance for Shine Project SS14 work, including fork-owned tables, SQLite/Postgres compatibility, namespaced migrations, server database projects, and avoiding upstream table churn.

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

Database ArchitectsComputer and Mathematical Occupations·SOC 15-1243

File Explorer

4 files

SKILL.md

readonly

name	ss14-databases-migrations
description	Database and EF Core migration guidance for Shine Project SS14 work, including fork-owned tables, SQLite/Postgres compatibility, namespaced migrations, server database projects, and avoiding upstream table churn.

SS14 Databases Migrations

Rules

Avoid modifying upstream tables.
Prefer Shine-owned tables with one-to-one relations for fork-only data.
Namespace migrations and model types clearly.
Test SQLite and Postgres when schema or query behavior changes.
Keep persistence out of predicted simulation logic.
Do not store player-facing text or prototype IDs in ways that block localization or future prototype changes.

.NET 10

The repo uses EF Core 10 packages. Check Directory.Packages.props and existing migration patterns before adding code.

Bundled References

references/efcore-fork-rules.md: fork-owned tables, namespaced models/migrations, and upstream table boundaries.
references/migration-validation.md: SQLite/Postgres validation and review checklist.

Placement

Shared database models: database-specific shared project if existing pattern requires it.
Server persistence: Content.Server.Database or Content.Server/_sh according to local pattern.
Do not touch RobustToolbox persistence.

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-databases-migrations
description	Database and EF Core migration guidance for Shine Project SS14 work, including fork-owned tables, SQLite/Postgres compatibility, namespaced migrations, server database projects, and avoiding upstream table churn.

SS14 Databases Migrations

Rules

Avoid modifying upstream tables.
Prefer Shine-owned tables with one-to-one relations for fork-only data.
Namespace migrations and model types clearly.
Test SQLite and Postgres when schema or query behavior changes.
Keep persistence out of predicted simulation logic.
Do not store player-facing text or prototype IDs in ways that block localization or future prototype changes.

.NET 10

The repo uses EF Core 10 packages. Check Directory.Packages.props and existing migration patterns before adding code.

Bundled References

references/efcore-fork-rules.md: fork-owned tables, namespaced models/migrations, and upstream table boundaries.
references/migration-validation.md: SQLite/Postgres validation and review checklist.

Placement

Shared database models: database-specific shared project if existing pattern requires it.
Server persistence: Content.Server.Database or Content.Server/_sh according to local pattern.
Do not touch RobustToolbox persistence.