Update to Davia Creation

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 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.
+description: Create and edit Davia game drafts 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.
 ---
 
 # Davia creation
@@ -13,8 +13,10 @@
 ## Start every task this way
 
 1. Call `list_drafts`.
-2. If no game is active, identify the intended game by its display name and
-   call `select_draft`. Never guess an id.
+2. Identify the intended game by its display name; ask when the target is
+   unclear. Copy its returned `ref` exactly into the `draft` argument of every
+   filesystem tool call. Never invent a reference or use a draft UUID. If the
+   reference is forgotten or unavailable, call `list_drafts` again.
 3. Read [`references/editing-with-the-mcp.md`](references/editing-with-the-mcp.md).
 4. Read the current files that govern the requested change. Use `grep` to find
    related names, stat ids, values, and rules across the game.
@@ -27,6 +29,11 @@
 Use the language of the creator's first message for conversation and visible
 game content. Keep technical keys exactly as the files expose them.
 
+The first non-text stat with cell values colors the map. Unless the creator
+says otherwise, keep the territorial stat there (who holds each place: allegiance,
+faction, country) and give it a value on every land cell. See
+[`references/stats-contract.md`](references/stats-contract.md#the-map-stat).
+
 ## Route the work
 
 - Read [`references/game-model.md`](references/game-model.md) when shaping the
@@ -37,35 +44,19 @@
   [`references/entities-and-landmarks.md`](references/entities-and-landmarks.md)
   before changing a character, group, place, or placement.
 - Read [`references/map-assets-catalog.md`](references/map-assets-catalog.md)
-  only when the creator asks for a 3D asset recommendation. The current MCP
-  does not expose asset assignment for editing.
-
-## Keep authored state separate from simulation rules
-
-Put what is true at the opening in the premise, world description, entities,
-landmarks, cells, and starting stat values. Put only causal, game-specific
-constraints in simulation rules.
-
-For example, if the creator says that one bloc controls all of Africa at the
-start, update the relevant premise or world context and the applicable cell
-values. Do not invent a new simulation rule merely to restate that starting
-state. A rule belongs only when it changes how later actions resolve, such as a
-specific supply delay, legal constraint, or chain-of-command requirement.
-
-Do not repeat Davia's native principles in every game. Generic statements such
-as “the world evolves,” “actions have consequences,” or “no future is fixed”
-consume attention without making this particular world behave differently.
+  and call `browse_map_assets` before recommending or assigning a 3D asset. It
+  also explains where to send a creator who wants a custom 3D model built
+  with Blender.
+  Use the filters returned beside every page to refine broad browsing, and use
+  its optional text query when the creator names a specific subject.
+- Read [`references/geometry.md`](references/geometry.md) before splitting or
+  merging cells. Use `split_cell` / `merge_cells`, then verify the result.
 
 ## Respect current capability boundaries
 
-The MCP can add, edit, and remove entities and landmarks through their complete
-objects in `entities.json` and `landmarks.json`. Read the entity and landmark
-reference before doing so because creation requires a duplicate check and new
-landmarks require a precise on-map placement.
-
-The MCP can append complete stat definitions to `stats.json`. Existing stat
-identities and order remain fixed, and stat definitions cannot be removed. The
-MCP does not add or remove cells, change cell geometry, or assign 3D assets.
-Never claim that one of those unsupported operations succeeded. Use the
-editable fields to make as much progress as possible and state the exact
-remaining Creation Hub action when a requested change crosses those bounds.
+Keep existing stat identities; reorder definitions to change display order. The
+filesystem cannot add or remove cells; use the bounded geometry tools to split
+or merge existing cells. Follow the linked contracts for stat creation,
+entities, landmarks, placement, and map assets. Make progress through supported
+fields and name the remaining Creation Hub action when a request exceeds these
+bounds. Never claim an unsupported operation succeeded.