Update to Gondwana

{
  "name": "explain-gondwana-api",
  "description": "Explains Gondwana APIs, architecture, concepts, and current engine behavior using the official wiki plus live source and tests. Use when the user asks how Gondwana works, what a type/property/subsystem does, why the engine is designed a certain way, how two Gondwana concepts differ, or whether a documented capability exists today.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 450
    }
  ],
  "skill_md_contents": "---\r\nname: explain-gondwana-api\r\ndescription: Explains Gondwana APIs, architecture, concepts, and current engine behavior using the official wiki plus live source and tests. Use when the user asks how Gondwana works, what a type/property/subsystem does, why the engine is designed a certain way, how two Gondwana concepts differ, or whether a documented capability exists today.\r\n---\r\n\r\n# Explain a Gondwana API or Concept\r\n\r\nUse this skill for accurate explanations of Gondwana rather than implementation-first work.\r\n\r\n## Use the right source for the question\r\n\r\nGondwana deliberately has different sources of truth for different questions.\r\n\r\nUse the **wiki** first for:\r\n\r\n- mental models,\r\n- terminology,\r\n- architecture,\r\n- normal game-developer workflows,\r\n- coordinate-space explanations,\r\n- subsystem overviews.\r\n\r\nUse **current source and tests** to verify:\r\n\r\n- exact APIs and signatures,\r\n- current implementation order,\r\n- ownership,\r\n- inheritance/copy/cache behavior,\r\n- current regression guarantees,\r\n- whether a feature actually exists on the current branch.\r\n\r\nUse demos/templates to show how current public APIs are composed in real game code.\r\n\r\nDo not treat `ROADMAP.md`, an open issue, old changelog text, or historical documentation as proof that a feature is implemented.\r\n\r\n## Workflow\r\n\r\n1. If the Gondwana MCP tools are available, call `get_repository_info` for source-sensitive questions.\r\n2. Read/search the relevant wiki topic.\r\n3. Search/read the defining source files for exact implementation claims.\r\n4. Search relevant tests when behavior or ordering matters.\r\n5. Inspect a current demo/template when a usage example would improve the answer.\r\n6. Reconcile the sources using the precedence in `AGENTS.md`.\r\n\r\nIf documentation and current implementation disagree, say so plainly and identify which describes current behavior.\r\n\r\n## Answer style\r\n\r\nStart with the conceptual answer, then add implementation detail only as needed.\r\n\r\nFor code-facing explanations:\r\n\r\n- name the relevant Gondwana types,\r\n- distinguish public API from internals,\r\n- identify coordinate space when relevant,\r\n- identify lifecycle/update/render stage when relevant,\r\n- cite or name the relevant source paths and wiki pages when the host supports citations.\r\n\r\nAvoid explaining Gondwana by analogy to Unity, Godot, ECS engines, or generic game-engine conventions when Gondwana's own architecture answers the question directly.\r\n\r\n## Roadmap versus current behavior\r\n\r\nWhen a question concerns planned work, label it clearly:\r\n\r\n- **Implemented now**\r\n- **Partially implemented**\r\n- **Planned**\r\n- **Exploratory/design discussion**\r\n\r\nNever silently upgrade planned behavior into a current guarantee.\r\n"
}