← LevelweaveCONTENT HISTORY
WHAT CHANGED
Update to Levelweave
Snapshot Nov 3, 2026 · 00:15 UTC · version 0.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Levelweave and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Design or implement visual novels, branching dialogue, interactive fiction, and story-driven game mechanics with coherent state.",
"included_files": [],
"name": "build-narrative-game",
"skill_md_contents": "---\nname: build-narrative-game\ndescription: Design or implement visual novels, branching dialogue, interactive fiction, and story-driven game mechanics with coherent state.\n---\n\n# Build Narrative Game\n\n\n1. Define player agency, branching structure, variables/flags, pacing, scene transitions and narrative endings; avoid fake choice branches that immediately converge without consequence.\n2. Read `../../references/renpy.md` for Ren’Py-focused visual novel implementation. Existing custom engines may be retained.\n3. Model dialogue and conditional state separately from presentation when possible. Track dead ends, unreachable branches, missing assets and uninitialized variables.\n4. Provide accessible typography, readable pacing, rollback/skip settings if supported, clear choices and consistent UI.\n5. Validate branch completeness with a graph walkthrough and actual engine lint/build commands when available; include save/load tests.\n6. Use original or appropriately licensed narrative, character assets and music. If user requests an existing commercial IP, prefer an original alternative unless rights are confirmed.\n7. Deliver scripts, branch map, input/output state definitions, tested endings, and unresolved narrative assumptions.\n\n## Execution truth and safeguards\n- A skill is an instruction workflow, not a remotely running game engine or a separately running AI agent. Inspect tools and repo state before claiming execution.\n- Preserve existing projects, names, dependencies, save formats, and user work unless a change is explicitly requested. Obtain approval for deployment, payments, destructive edits, publication, and major third-party connections.\n- Avoid reproducing protected commercial characters, levels, dialogue, soundtracks, logos, or copyrighted assets unless authorized. For assets, record origin and license. Read `../../references/security-and-rights.md`.\n- Report what was implemented, what was actually run, what failed, and what remains unverified; never describe proposed tests as passed.\n"
}SHA-256 of public snapshot: fc162fac222120beb9753eb369a91a7c84c92199097b7c411f9aeddc9f96a892