Board Cards in the Game skill for AI agents

​

When your agent uses it

• Gameplay code needs the stats, lists or links people put on the board as cards
• A person says use the characters from the board or make the levels we planned, or cards the game uses changed

​

Install

npx -y summer-engine@latest skills install summer-board-to-game --agent claude-code

​

The skill

​

1. Export

board.export {gameId, agent}                        -> files: [{path, content}], skipped, how
board.export {gameId, agent, types: ["Character"]}  -> only those types and what they link to

• res://data/types/character_data.gd: class_name CharacterData extends Resource, one @export per field. A choice is @export_enum, a link is the linked type (@export var faction: FactionData, @export var drops: Array[ItemData]). A field named like a GDScript word gets a trailing _ (class is class_).
• res://data/characters/ember_knight.tres: one per card.
• res://data/board_data.gd: class_name BoardData, every card preloaded, a list per type and a lookup by name.

​

2. Use it in gameplay code

# Every card of a type, as typed Resources.
for c in BoardData.characters:
	if c.role == "enemy":
		spawn_table.append(c)

# One card by name.
var boss: CharacterData = BoardData.character("Ember Knight")
health.max_value = boss.hp
for item in boss.drops:
	loot.add(item)

# Links are real references.
print(boss.faction.name)

• Read stats from the resource; do not copy numbers into scripts. The person tunes hp on the card, and the game follows.
• A resource is shared by everything that loads it. Before changing values at run time (damage taken, upgrades), duplicate() it, or keep run-time state in the node.
• A link whose card is gone, or that skipped names, is null. Check before use where a missing card would crash.
• Names follow the type: BoardData.quest_steps and BoardData.quest_step("...") for QuestStep.
• Look up by name only for named things (the boss, the starting level). Iterate for lists (all enemies, all levels).

​

3. Keep board and game in step

• Tune on the card, then re-export. board.canvas {action: "update", itemId, props: {hp: 1200}}, then board.export. Never edit a generated .gd or .tres by hand or in the inspector: the next export overwrites it.
• A field the game needs and the type lacks: add it to the type (summer-board-types section 3), fill the cards, re-export. Do not add an @export to the generated class.
• Logic is not data. How a boss fights is a script in the game; its hp, speed and drops are the card. A card can name the behaviour as a choice (behaviour: "charger") that your code maps to a script.
• Say what you did. After an export the game uses, board.post one line: what changed in the game (“Enemies now spawn from the 6 Character cards with role enemy”).
• Re-export when the board changes. A card update that a teammate’s message names, or a task done on a card the game uses, means re-export before you test.

​

4. Before you say it is done

• The project opens with no errors from res://data/.
• Play the scene that uses the data (playtesting-a-feature): the boss has the card’s hp, the level list matches the board.
• board.query the types you used: no card has issues. A card with a missing required field exports with that field at its default, which is usually a bug in play.

​

From a shell

​

Related skills

• summer-board: Summer Board co-op: tasks, claims, files, card frames.
• summer-board-types: Define and reuse types on a Summer Board (Character, Level, Item) so ideas become typed cards: read the board’s types first, reuse before you define.