{"id":14363,"plugin_id":"plugin_asdk_app_6a84600a39588191b200058a94614191","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:09:21.862Z","digest":"bf4300c42356f230a1309cc73a8d480a4ada59e8349c44bdc060fa19175a64f3","against":null,"payload":{"name":"davia-creation","description":"Create and edit Davia games through the Davia Creation MCP. Use whenever a creator asks to design, inspect, revise, rebalance, or complete a game, including its premise, world, simulation rules, stats, cells, entities, landmarks, or starting state.","included_files":[{"relative_path":"evals/evals.json","size_in_bytes":2665},{"relative_path":"references/editing-with-the-mcp.md","size_in_bytes":4210},{"relative_path":"references/entities-and-landmarks.md","size_in_bytes":3599},{"relative_path":"references/game-model.md","size_in_bytes":3028},{"relative_path":"references/map-assets-catalog.md","size_in_bytes":36919},{"relative_path":"references/stats-contract.md","size_in_bytes":3215}],"skill_md_contents":"---\nname: davia-creation\ndescription: Create and edit Davia games through the Davia Creation MCP. Use whenever a creator asks to design, inspect, revise, rebalance, or complete a game, including its premise, world, simulation rules, stats, cells, entities, landmarks, or starting state.\n---\n\n# Davia creation\n\nHelp the creator build a character-first sandbox RPG: a player inhabits one\ncharacter inside a world that has geography, other actors, material limits,\nand persistent consequences. Keep the creator's intended game central. The\nfiles are a representation of that game, not the creative goal by themselves.\n\n## Start every task this way\n\n1. Call `list_drafts`.\n2. If no game is active, identify the intended game by its display name and\n   call `select_draft`. Never guess an id.\n3. Read [`references/editing-with-the-mcp.md`](references/editing-with-the-mcp.md).\n4. Read the current files that govern the requested change. Use `grep` to find\n   related names, stat ids, values, and rules across the game.\n5. Explain any creative choice that would materially change the premise,\n   playable cast, map meaning, or simulation. When the creator already gave a\n   precise instruction, carry it out without reopening settled decisions.\n6. Make focused edits, then reread the changed files to verify the resulting\n   state.\n\nUse the language of the creator's first message for conversation and visible\ngame content. Keep technical keys exactly as the files expose them.\n\n## Route the work\n\n- Read [`references/game-model.md`](references/game-model.md) when shaping the\n  premise, world, playable roles, map meaning, or simulation rules.\n- Read [`references/stats-contract.md`](references/stats-contract.md) before\n  creating or changing stat definitions or values.\n- Read\n  [`references/entities-and-landmarks.md`](references/entities-and-landmarks.md)\n  before changing a character, group, place, or placement.\n- Read [`references/map-assets-catalog.md`](references/map-assets-catalog.md)\n  only when the creator asks for a 3D asset recommendation. The current MCP\n  does not expose asset assignment for editing.\n\n## Keep authored state separate from simulation rules\n\nPut what is true at the opening in the premise, world description, entities,\nlandmarks, cells, and starting stat values. Put only causal, game-specific\nconstraints in simulation rules.\n\nFor example, if the creator says that one bloc controls all of Africa at the\nstart, update the relevant premise or world context and the applicable cell\nvalues. Do not invent a new simulation rule merely to restate that starting\nstate. A rule belongs only when it changes how later actions resolve, such as a\nspecific supply delay, legal constraint, or chain-of-command requirement.\n\nDo not repeat Davia's native principles in every game. Generic statements such\nas “the world evolves,” “actions have consequences,” or “no future is fixed”\nconsume attention without making this particular world behave differently.\n\n## Respect current capability boundaries\n\nThe MCP can add, edit, and remove entities and landmarks through their complete\nobjects in `entities.json` and `landmarks.json`. Read the entity and landmark\nreference before doing so because creation requires a duplicate check and new\nlandmarks require a precise on-map placement.\n\nThe MCP can append complete stat definitions to `stats.json`. Existing stat\nidentities and order remain fixed, and stat definitions cannot be removed. The\nMCP does not add or remove cells, change cell geometry, or assign 3D assets.\nNever claim that one of those unsupported operations succeeded. Use the\neditable fields to make as much progress as possible and state the exact\nremaining Creation Hub action when a requested change crosses those bounds.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}