notque/vexjoy-agent / skills/game/game-dev
game-dev
FlaggedGame development: design, asset pipelines, Phaser, Unity CLI and builds, vanilla JS frontend, GM mode, match booking.
references/capabilities/35-game-design-peak-end-audit.md
View on GitHub# game-design-peak-end-audit
## Purpose
Shape memorable highs and endings without manipulative pressure. This packet is a repository-aware operating procedure, not a label to apply to a design.
## Evidence intake
Inspect repository evidence before requesting context: session flow, reward timing, narrative, UI, economy. Then inspect these capability-specific signals: earned peak, contrast, closure, unresolved invitation, cooldown, session exit. Ask only for external evidence, confidential player research, decision authority, or constraints unavailable in the repository.
Mark every claim as `observed`, `documented`, `measured`, or `inferred`. Give each inference a confidence level and a disproof route.
## Method
1. Map effort, uncertainty, emotional intensity, reward, cooldown, closure, and return invitation across a session.
2. Separate earned peaks from arbitrary reward spikes and closure from absence pressure.
3. Design endings that preserve agency: close, choose the next intention, or leave safely.
## Capability matrix
| Lens | Repository question | Player or delivery consequence |
|---|---|---|
| earned peak | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
| contrast | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
| closure | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
| unresolved invitation | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
| cooldown | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
| session exit | What evidence shows how this changes the reviewed moment? | Record the effect, confidence, and repair test. |
## Diagnostic questions
- What exact player moment or delivery decision is under review?
- Which capability lens above has the strongest evidence and which is only an inference?
- Which competing explanation would produce the same visible symptom?
- What is the smallest change or test that would separate them?
## Output schema
Return all of the following, not a generic summary:
- session emotion timeline
- peak candidates
- end-state audit
- changes and guards
## Failure modes
- Do not use unresolved loss or expiring reward as a substitute for a satisfying end.
- Do not stack peaks until none is memorable.
- Do not use loss threats to convert a close into a return loop.
## Example application
When a team needs to shape memorable highs and endings without manipulative pressure, begin with the available build path and the capability matrix above. Apply the named method to the affected moment, not an abstract feature description. If direct player evidence is absent, publish an evidence gap rather than a false conclusion; label the result as inferred and use the validation below to move it toward measured evidence.
## Decision procedure
1. Use `earned peak` as the first discriminating lens, because it is closest to the stated capability.
2. Compare it against `session exit` before selecting a fix; this prevents a single-dimension conclusion.
3. Convert the result into `peak-end map` with an owner, a quality guard, and a stop rule.
## Validation
Ask players for the most memorable and final moment after a delayed recall.
## Full-diagnostic disposition
In a complete repository diagnostic, run this packet and record `assessed`, `evidence gap`, or `not applicable` with a game-specific reason. A missing artifact is a finding; it never permits silent omission.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |