II.
Role JSON
Structured · liverole:game-designer
Game Designer json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "role:game-designer",
"_kind": "Role",
"_file": "role/roles/roles-expanded-3.yaml",
"_cluster": "role",
"attributes": {
"displayName": "Game Designer",
"isAgentic": false,
"requiredCapabilities": [],
"requiredDomains": [],
"description": "Designs game mechanics, systems, and player experiences — rule sets,\nprogression systems, economy balancing, and difficulty curves.\nCreates design documents, prototypes gameplay loops, and iterates\nbased on playtesting feedback.\n"
},
"outgoingEdges": [
{
"from": "role:game-designer",
"to": "responsibility:user-research",
"kind": "holds_responsibility"
},
{
"from": "role:game-designer",
"to": "responsibility:metric-definition",
"kind": "holds_responsibility"
},
{
"from": "role:game-designer",
"to": "domain:game-design",
"kind": "applies_to",
"attributes": {}
},
{
"from": "role:game-designer",
"to": "domain:gaming",
"kind": "applies_to",
"attributes": {}
}
],
"incomingEdges": [
{
"from": "domain:gaming-industry",
"to": "role:game-designer",
"kind": "employs_role"
}
]
}