mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 10:17:06 +00:00
DonchitosandClaude Opus 5.5
be8993bbc5
Fix release for 1.1.2: the 14 longest skills keep their later phases after a compaction, a question nobody answered is never taken as an answer, settings read the same from a subfolder, the commit check works for a project in a subfolder of a larger repository, every skill opens with a title, and the shipped allow rules no longer approve deleting a branch or writing files without asking. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.2 → v1.1.3). Refs #83 Refs #133 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
# /test-setup — Phase 5: Create Smoke Test Seed
|
|
|
|
> Part of `/test-setup`. `SKILL.md` names when to read this file; the settings it
|
|
> resolved and the rules under its later headings still apply here.
|
|
|
|
## Phase 5: Create Smoke Test Seed
|
|
|
|
Create `tests/smoke/critical-paths.md`:
|
|
|
|
```markdown
|
|
# Smoke Test: Critical Paths
|
|
|
|
**Purpose**: Run these 10-15 checks in under 15 minutes before any QA hand-off.
|
|
**Run via**: `/smoke-check` (which reads this file)
|
|
**Update**: Add new entries when new core systems are implemented.
|
|
|
|
## Core Stability (always run)
|
|
|
|
1. Game launches to main menu without crash
|
|
2. New game / session can be started from the main menu
|
|
3. Main menu responds to all inputs without freezing
|
|
|
|
## Core Mechanic (update per sprint)
|
|
|
|
<!-- Add the primary mechanic for each sprint here as it is implemented -->
|
|
<!-- Example: "Player can move, jump, and the camera follows correctly" -->
|
|
4. [Primary mechanic — update when first core system is implemented]
|
|
|
|
## Data Integrity
|
|
|
|
5. Save game completes without error (once save system is implemented)
|
|
6. Load game restores correct state (once load system is implemented)
|
|
|
|
## Performance
|
|
|
|
7. No visible frame rate drops on target hardware (60fps target)
|
|
8. No memory growth over 5 minutes of play (once core loop is implemented)
|
|
```
|
|
|
|
---
|