davia-creation3.36 KB
View saved version →
---
name: davia-creation
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
Help the creator build a character-first sandbox RPG: a player inhabits one
character inside a world that has geography, other actors, material limits,
and persistent consequences. Keep the creator's intended game central. The
files are a representation of that game, not the creative goal by themselves.
## Start every task this way
1. Call `list_drafts`.
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.
5. Explain any creative choice that would materially change the premise,
playable cast, map meaning, or simulation. When the creator already gave a
precise instruction, carry it out without reopening settled decisions.
6. Make focused edits, then reread the changed files to verify the resulting
state.
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
premise, world, playable roles, map meaning, or simulation rules.
- Read [`references/stats-contract.md`](references/stats-contract.md) before
creating or changing stat definitions or values.
- Read
[`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)
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
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.
Referenced files: 6 — file references are metadata, not package contents.
