Keep · astra-grok SKILL.md

Experience-first game brief

WhenUse at the start of any game or interactive slice — before look-lock, before mesh, before engine choice. Trigger when someone asks for "art for the game" or "build it in Unreal" without a written player experience.

StopReject pixel work, mesh work, and stack debates without a brief. Do not write a feature laundry list instead of a fantasy + loop. Do not invent three unique verbs — pick one and protect it. Do not start production mid-brief; brief ends with explicit go.

Steps

Interview or extract: audience, platform, session length, tone. Write unknowns as questions, not guesses.
Write **player fantasy** in 2–3 sentences (who I am, what it feels like to be powerful/clever/scared).
Write the **30-second loop**: verb → obstacle → feedback → reward → back to verb.
Define **win** and **lose** (or endless pressure) in observable terms.
List **controls** for the vertical slice (device-specific). Keep them few.
Name **one unique verb** the game owns; list verbs you will not steal from better games.
Only then: recommend art direction seeds and tech stack as servants of the brief.
Save `brief/GAME-BRIEF.md`. Require human go (or explicit auto-accept) before look-lock or production skills.

Oven

Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.) GenerateImage only for optional mood crumbs after the brief text exists — never as a substitute for the brief.

Done when

`GAME-BRIEF.md` has fantasy, 30s loop, win/lose, controls, one unique verb.
Art/tech sections are labeled as following the brief, not leading it.
No production files created before brief approval marker.
Open questions listed, not papered over.

Cross-model

Recipe is fixed: fantasy → loop → win/lose → controls → unique verb → then art/tech. Only the OVEN line swaps — drafting tools differ by host; the reject-pixel-without-brief rule stays identical across Astra, Grok Bot, Fable, and Claude.

LoadOVEN: Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.) GenerateImage only for optional mood crumbs after the brief text exists — never as a substitute for the brief. Done when: - `GAME-BRIEF.md` has fantasy, 30s loop, win/lose, controls, one unique verb. - Art/tech sections are label

SourceAstra skills reworked for Grok Bot

Copy SKILL.mdRaw SKILL.md

---
name: "Experience-first game brief"
description: "Use before art or tech when a game idea needs player fantasy, 30s loop, win/lose, controls, and one unique verb."
---

# Experience-first game brief

## When
Use at the start of any game or interactive slice — before look-lock, before mesh, before engine choice. Trigger when someone asks for "art for the game" or "build it in Unreal" without a written player experience.

## Stop
- Reject pixel work, mesh work, and stack debates without a brief.
- Do not write a feature laundry list instead of a fantasy + loop.
- Do not invent three unique verbs — pick one and protect it.
- Do not start production mid-brief; brief ends with explicit go.

## OVEN
Default: Grok Bot tools — GenerateImage / computerUse / browserUse / Shell / Blender MCP if connected / Screenshot. (Swap this one line for Astra / Fable / Claude.) GenerateImage only for optional mood crumbs after the brief text exists — never as a substitute for the brief.

## Steps
1. Interview or extract: audience, platform, session length, tone. Write unknowns as questions, not guesses.
2. Write **player fantasy** in 2–3 sentences (who I am, what it feels like to be powerful/clever/scared).
3. Write the **30-second loop**: verb → obstacle → feedback → reward → back to verb.
4. Define **win** and **lose** (or endless pressure) in observable terms.
5. List **controls** for the vertical slice (device-specific). Keep them few.
6. Name **one unique verb** the game owns; list verbs you will not steal from better games.
7. Only then: recommend art direction seeds and tech stack as servants of the brief.
8. Save `brief/GAME-BRIEF.md`. Require human go (or explicit auto-accept) before look-lock or production skills.

## Done when
- `GAME-BRIEF.md` has fantasy, 30s loop, win/lose, controls, one unique verb.
- Art/tech sections are labeled as following the brief, not leading it.
- No production files created before brief approval marker.
- Open questions listed, not papered over.

## Cross-model
Recipe is fixed: fantasy → loop → win/lose → controls → unique verb → then art/tech. Only the OVEN line swaps — drafting tools differ by host; the reject-pixel-without-brief rule stays identical across Astra, Grok Bot, Fable, and Claude.