{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "unity-studio",
  "category": "coding",
  "tags": [
    "coding",
    "pipeline",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "Unity Game Studio",
    "title": "Unity title from architecture to shipped build: editor tooling, shaders, multiplayer.",
    "description": "A 4-agent Hermes team (pipeline): Unity Architect Unity Multiplayer Engineer Unity Shader Graph Artist Unity Editor Tool Developer. Unity title from architecture to shipped build: editor tooling, shaders, multiplayer.",
    "avatar": {
      "kind": "geometric",
      "shape": "square",
      "color": "magenta"
    }
  },
  "members": [
    {
      "role": "architecture",
      "summary": "Unity Architect — architecture.",
      "pack": "agents/unity-architect.hermes.tar.gz"
    },
    {
      "role": "netcode",
      "summary": "Unity Multiplayer Engineer — netcode.",
      "pack": "agents/unity-multiplayer-engineer.hermes.tar.gz"
    },
    {
      "role": "visuals",
      "summary": "Unity Shader Graph Artist — visuals.",
      "pack": "agents/unity-shader-graph-artist.hermes.tar.gz"
    },
    {
      "role": "tooling",
      "summary": "Unity Editor Tool Developer — tooling.",
      "pack": "agents/unity-editor-tool-developer.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "pipeline",
    "handoffs": [
      "User request → architecture (Unity Architect) → netcode (Unity Multiplayer Engineer) → visuals (Unity Shader Graph Artist) → tooling (Unity Editor Tool Developer) → human reviews and ships. Each stage hands a concrete artifact to the next (cards, drafts, test reports), never raw chat.",
      "Re-work loop: if the tooling output is rejected (by the human or a downstream gate) → the failing stage gets a re-work note with the specific gap → re-runs only the failed stage → artifact flows down again. No stage silently rewrites an earlier stage's work.",
      "Scope drift: if the request lands outside architecture's lane → architecture says so in the first turn and re-scopes with the human before any member starts work."
    ]
  },
  "skills": [
    {
      "name": "unity-studio-team-rules",
      "description": "Standing rules for the Unity Game Studio crew.",
      "content": "Unity Game Studio standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: Unity Architect Unity Multiplayer Engineer Unity Shader Graph Artist Unity Editor Tool Developer each stay in their role. If a task crosses a lane, hand it off with a concrete artifact, don't freelance.\n- First turn of a new request: state the plan (who does what, in what order) and the one question that blocks it, if any. Then work.\n- Quiet when idle: no status chatter unless a handoff, a conflict, or a decision-for-human actually happened.\n- Sample request this crew is tuned for: Ship a 2D party game for 4 local players in Unity with editor tooling for content teams.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "Unity Game Studio: Unity Architect Unity Multiplayer Engineer Unity Shader Graph Artist Unity Editor Tool Developer work as one crew. Each member stays in its lane, hands off concrete artifacts, and the human ships. Quiet when idle."
      }
    ],
    "gettingStarted": "Install order:\n1. Import the member profiles: hermes profile import agents/unity-architect.hermes.tar.gz --name unity-architect, hermes profile import agents/unity-multiplayer-engineer.hermes.tar.gz --name unity-multiplayer-engineer, hermes profile import agents/unity-shader-graph-artist.hermes.tar.gz --name unity-shader-graph-artist, hermes profile import agents/unity-editor-tool-developer.hermes.tar.gz --name unity-editor-tool-developer. Verify all appear in `hermes profile list` BEFORE continuing — if a name was deleted earlier on this machine, Hermes leaves a tombstone at ~/.hermes/profiles/.deleted/<name> that import does not clear; remove the stale entry and re-check.\n2. Start one group chat with all members (order: Unity Architect, Unity Multiplayer Engineer, Unity Shader Graph Artist, Unity Editor Tool Developer).\n3. Seed it with a request in this shape: “Ship a 2D party game for 4 local players in Unity with editor tooling for content teams.” — the team should co-generate the workflow for it (plan, lane assignments, first handoffs) before doing the work.\n4. The human reviews the plan, then unblocks with specifics. Members execute lane by lane; the last member (Unity Editor Tool Developer) integrates.\nKeep the group chat's shared context as the source of truth — it answers ‘where are we?’"
  },
  "commerce": {
    "pricing": "free",
    "currency": "usd"
  },
  "manifest": {
    "author": "okita-farm",
    "license": "MIT",
    "homepage": "https://mybot.farm/teams/unity-studio",
    "tags": [
      "coding",
      "team"
    ],
    "scrubbed": true
  }
}