Contenu du pack

Un fichier SKILL.md (le guide pratique) + un modèle de départ. Aperçu :

Interactive Simulation Spec Writer

The idea in one paragraph

A simulation you can walk into needs more than a pretty world — it needs a plan for what should happen inside it. The Genie 4 announcement describes a guiding agent (Gemini 3.8 Flash) that looks at frames, breaks a goal into steps, and verifies each step. This skill turns that pattern into a writing method: you write the goal, decompose it into checkable steps, define how each step gets verified, and set the conditions that end the run. The output is a spec any builder — human or agent — can execute against.

What it is built on

• Per DeepMind's October 27, 2026 blog post, a Gemini 3.8 Flash guiding agent operates in the loop: it observes frames, decomposes a goal into steps, and verifies each step as it runs.
• DeepMind lists four advances for Genie 4: stronger photorealism, smoother motion, native generated audio, and longer coherence of about 2 minutes (TechCrunch), roughly double Genie 3.
• Genie 4 is a research preview for trusted testers with a waitlist; Google plans access for Google AI Ultra subscribers (inside Project Genie) and early Gemini API / AI Studio partners. No dates, prices, or published benchmarks were announced.
• DeepMind publicly acknowledges limitations including drift, object permanence, physics, and legible text — a spec must account for these rather than assume them away.

Workflow

1. State the goal in one sentence (input: idea -> output: goal statement). Write what the explorer should experience or accomplish, in plain language. If it needs a second sentence, it is two goals — split it.
2. Decompose into checkable steps (input: goal -> output: numbered step list). Break the goal into steps where each one has a yes/no completion test. A step like "explore the market" is not checkable; "reach the fountain at the market's center" is.
3. Define the verification loop (input: steps -> output: check procedure). For each step, write how completion is verified — what the guiding agent looks at, and what counts as evidence. Borrow the in-the-loop pattern: observe, compare against the step's test, then proceed.
4. Write the exit conditions (input: steps + loop -> output: exit rules). Define when the run ends: goal reached, explorer types a stop command, a time limit hits, or the world drifts past a tolerance you set. Every run needs at least two exit conditions.
5. Add failure handling (input: spec draft -> output: fallback rules). Decide what happens when a step cannot be verified — retry once, skip and log, or abort the run. Never let a stuck step spin forever.
6. Freeze the spec (input: full draft -> output: signed spec). Read it end to end as the person who must execute it. If any step is ambiguous, rewrite it now; ambiguity compounds in a live simulation.

Aperçu du modèle

Interactive Simulation Spec Template

Goal

_One sentence: what the explorer experiences or accomplishes._

Steps (each with a yes/no completion test)

Verification loop

_How each step is verified (what to observe, what counts as evidence):_

Exit conditions (at least two)

1. 2.

Failure handling

_What happens when a step cannot be verified: retry / skip+log / abort._

Spec metadata

• Target model:
• Date written:
• Known limits assumed:

Le pack de compétence lui-même (SKILL.md + modèle) est rédigé en anglais.

Acheter le pack complet — $4.99 Pro — les 531 compétences