Run any Skill in Manus with one click

ss14-testing

Stars0

Forks0

UpdatedMay 20, 2026 at 14:00

Test and validation guidance for Shine Project SS14 changes. Use when choosing build, YAML linter, unit, integration, database, prediction, or manual validation for code, prototypes, maps, resources, and review-bot changes.

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 Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	ss14-testing
description	Test and validation guidance for Shine Project SS14 changes. Use when choosing build, YAML linter, unit, integration, database, prediction, or manual validation for code, prototypes, maps, resources, and review-bot changes.

SS14 Testing

Choose Focused Validation

C# logic: build touched project and run focused tests.
Prototypes/resources: run YAML/prototype validation.
Networking/prediction: use integration tests or manual fake-lag two-client checks.
Database: test SQLite and Postgres migration paths.
UI: open the UI path in-game when possible and check localization and resizing.
Agent configs: validate YAML/JSON and skill frontmatter.

Bundled References

references/validation-command-map.md: command selection by changed area.
references/manual-test-report.md: what to record when automation is not enough.

Test Design

Test public EntitySystem APIs, not private implementation details.
Keep fixtures minimal and prototype IDs namespaced.
Add regression tests for bug fixes.
Avoid nondeterministic timing/randomness.

Manual Validation Notes

When tests are not practical, document:

command(s) run;
scenario tested;
fake lag/client count if prediction is involved;
residual risk.

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-testing
description	Test and validation guidance for Shine Project SS14 changes. Use when choosing build, YAML linter, unit, integration, database, prediction, or manual validation for code, prototypes, maps, resources, and review-bot changes.

SS14 Testing

Choose Focused Validation

C# logic: build touched project and run focused tests.
Prototypes/resources: run YAML/prototype validation.
Networking/prediction: use integration tests or manual fake-lag two-client checks.
Database: test SQLite and Postgres migration paths.
UI: open the UI path in-game when possible and check localization and resizing.
Agent configs: validate YAML/JSON and skill frontmatter.

Bundled References

references/validation-command-map.md: command selection by changed area.
references/manual-test-report.md: what to record when automation is not enough.

Test Design

Test public EntitySystem APIs, not private implementation details.
Keep fixtures minimal and prototype IDs namespaced.
Add regression tests for bug fixes.
Avoid nondeterministic timing/randomness.

Manual Validation Notes

When tests are not practical, document:

command(s) run;
scenario tested;
fake lag/client count if prediction is involved;
residual risk.