Using AI for BGA game development - Revision history

Victoria La at 18:44, 16 July 2026

2026-07-16T18:44:31Z

← Older revision		Revision as of 18:44, 16 July 2026
Line 32:		Line 32:

	== Skills ==		== Skills ==
	The best way to save the workflows is to use skills. If you developed some AI skills ~~I suggest sharing~~ it		The best way to save the workflows is to use skills. If you developed some AI skills share it here by providing link (and contact if not clear from link).
	here by providing link ~~to git~~ repo
			DISCLAIMER: skills shared here comes from community and not affiliated with BGA itself, contact repo maintainer for questions

Whez: /* Skills */

2026-07-14T10:02:05Z

Skills

← Older revision		Revision as of 10:02, 14 July 2026
Line 36:		Line 36:


	~~'''~~claude-code-bga~~''' (~~[https://github.com/rbellec/claude-code-bga ~~GitHub~~], MIT) is a skill for [https://claude.ai/claude-code Claude Code] targeting the new (2025+) BGA framework. ~~It encodes~~:		=== claude-code-bga — from rulebook to a testable game on Studio ===
	* ~~project~~ setup: Makefile, SFTP deploy, config files, git workflow;		[https://github.com/rbellec/claude-code-bga claude-code-bga] (MIT) is a skill for [https://claude.ai/claude-code Claude Code] targeting the new (2025+) BGA framework. Rather than a single prompt, it packages the full development workflow:
	* PHP state-machine and ES6 client ~~patterns~~, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);
	* ~~a rules-~~clarification ~~workflow:~~ ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game's author, instead of being silently guessed;		* '''Project setup''' — Makefile, SFTP deploy, config files, git workflow;
	* ~~an automated~~ deploy-and-test loop via the Claude in Chrome extension: deploy, start a hotseat table on Studio, read the browser console for PHP/JS errors, fix, repeat (~30 s per cycle);		* '''Framework patterns''' — PHP state machine and ES6 client, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);
	* ~~a list of known BGA~~ pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).		* '''Rules clarification''' — ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game's author, instead of being silently guessed;
			* '''Automated deploy-and-test loop''' — via the Claude in Chrome extension: deploy, start a hotseat table on Studio, read the browser console for PHP/JS errors, fix, repeat (~30 s per cycle);
			* '''Known pitfalls''' — dbmodel.sql comments, table name conflicts, zombie handling, and other traps documented with their fixes.

	It has been used to implement several games on Studio (e.g. [https://github.com/rbellec/BGA_quantum_tic_tac_toe Quantum Tic-Tac-Toe], [https://github.com/rbellec/Go-On-Rasalva-on-BGA Go On Rasalva]), to migrate a legacy game to the new framework, and to walk through rule edge cases directly on Studio tables during testing. The generated code still needs review by the developer — the skill automates the BGA-specific plumbing and test cycle, not the game design decisions.		It has been used to implement several games on Studio (e.g. [https://github.com/rbellec/BGA_quantum_tic_tac_toe Quantum Tic-Tac-Toe], [https://github.com/rbellec/Go-On-Rasalva-on-BGA Go On Rasalva]), to migrate a legacy game to the new framework, and to walk through rule edge cases directly on Studio tables during testing. The generated code still needs review by the developer — the skill automates the BGA-specific plumbing and test cycle, not the game design decisions.

Whez: /* Skills */

2026-07-14T09:24:15Z

Skills

← Older revision		Revision as of 09:24, 14 July 2026
Line 37:		Line 37:

	'''claude-code-bga''' ([https://github.com/rbellec/claude-code-bga GitHub], MIT) is a skill for [https://claude.ai/claude-code Claude Code] targeting the new (2025+) BGA framework. It encodes:		'''claude-code-bga''' ([https://github.com/rbellec/claude-code-bga GitHub], MIT) is a skill for [https://claude.ai/claude-code Claude Code] targeting the new (2025+) BGA framework. It encodes:
	*project setup: Makefile, SFTP deploy, config files, git workflow;		* project setup: Makefile, SFTP deploy, config files, git workflow;
	*PHP state-machine and ES6 client patterns, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);		* PHP state-machine and ES6 client patterns, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);
	*a rules-clarification workflow: ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game's author, instead of being silently guessed;		* a rules-clarification workflow: ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game's author, instead of being silently guessed;
	*an automated deploy-and-test loop via the Claude in Chrome extension: deploy, start a hotseat table on Studio, read the browser console for PHP/JS errors, fix, repeat (~30 s per cycle);		* an automated deploy-and-test loop via the Claude in Chrome extension: deploy, start a hotseat table on Studio, read the browser console for PHP/JS errors, fix, repeat (~30 s per cycle);
	* a list of known BGA pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).		* a list of known BGA pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).

	It has been used to implement several games on Studio (e.g. [https://github.com/rbellec/BGA_quantum_tic_tac_toe Quantum Tic-Tac-Toe], [https://github.com/rbellec/Go-On-Rasalva-on-BGA Go On Rasalva]), to migrate a legacy game to the new framework, and to walk through rule edge cases directly on Studio tables during testing. The generated code still needs review by the developer — the skill automates the BGA-specific plumbing and test cycle, not the game design decisions.		It has been used to implement several games on Studio (e.g. [https://github.com/rbellec/BGA_quantum_tic_tac_toe Quantum Tic-Tac-Toe], [https://github.com/rbellec/Go-On-Rasalva-on-BGA Go On Rasalva]), to migrate a legacy game to the new framework, and to walk through rule edge cases directly on Studio tables during testing. The generated code still needs review by the developer — the skill automates the BGA-specific plumbing and test cycle, not the game design decisions.

	== Other resources ==		== Other resources ==
	* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp		* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp

Whez: /* Skills */

2026-07-14T09:18:41Z

Skills

← Older revision		Revision as of 09:18, 14 July 2026
Line 35:		Line 35:
	here by providing link to git repo		here by providing link to git repo


			'''claude-code-bga''' ([https://github.com/rbellec/claude-code-bga GitHub], MIT) is a skill for [https://claude.ai/claude-code Claude Code] targeting the new (2025+) BGA framework. It encodes:
			*project setup: Makefile, SFTP deploy, config files, git workflow;
			*PHP state-machine and ES6 client patterns, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);
			*a rules-clarification workflow: ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game's author, instead of being silently guessed;
			*an automated deploy-and-test loop via the Claude in Chrome extension: deploy, start a hotseat table on Studio, read the browser console for PHP/JS errors, fix, repeat (~30 s per cycle);
			* a list of known BGA pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).
			It has been used to implement several games on Studio (e.g. [https://github.com/rbellec/BGA_quantum_tic_tac_toe Quantum Tic-Tac-Toe], [https://github.com/rbellec/Go-On-Rasalva-on-BGA Go On Rasalva]), to migrate a legacy game to the new framework, and to walk through rule edge cases directly on Studio tables during testing. The generated code still needs review by the developer — the skill automates the BGA-specific plumbing and test cycle, not the game design decisions.
	== Other resources ==		== Other resources ==
	* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp		* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp

Victoria La: /* Other resources = */

2026-07-13T23:51:13Z

Other resources =

← Older revision		Revision as of 23:51, 13 July 2026
Line 35:		Line 35:
	here by providing link to git repo		here by providing link to git repo

	== Other resources ===		== Other resources ==
	* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp		* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp
	* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/		* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/

Victoria La at 23:50, 13 July 2026

2026-07-13T23:50:59Z

← Older revision		Revision as of 23:50, 13 July 2026
Line 34:		Line 34:
	The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it		The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it
	here by providing link to git repo		here by providing link to git repo

			== Other resources ===
			* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp
			* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/
			* https://www.reddit.com/r/ClaudeAI/comments/1uc7izy/i_added_a_clause_to_andrej_karpathys_4_claudemd/
			* https://www.reddit.com/r/ClaudeAI/comments/1t4ncbj/10_things_about_claude_that_took_me_way_too_long/


	----		----

	[[Category:Studio]]		[[Category:Studio]]

Victoria La: /* Overview */

2026-07-13T23:49:43Z

Overview

← Older revision		Revision as of 23:49, 13 July 2026
Line 10:		Line 10:
	* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures		* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures
	* Debugging complex state machine flows by analyzing execution traces		* Debugging complex state machine flows by analyzing execution traces
	* ~~Refactoring repetitive~~ patterns across multiple ~~operation classes~~		* Extracting patterns across multiple open source games
	* Writing client-side UI code (TypeScript/JS) for token rendering and animations		* Writing client-side UI code (TypeScript/JS) for token rendering and animations
	* Reviewing code for common BGA framework pitfalls and anti-patterns		* Reviewing code for common BGA framework pitfalls and anti-patterns
	* Generating CSS/SCSS for card layouts and sprite positioning from asset images		* Generating CSS/SCSS for card layouts and sprite positioning from asset images
	* Explaining unfamiliar parts of the BGA framework or existing codebase		* Explaining unfamiliar parts of the BGA framework or existing codebase
			* Reviewing against bga UI guildlines
			* Migrating game from old framework

	== Setup ==		== Setup ==

Victoria La at 23:44, 9 April 2026

2026-04-09T23:44:32Z

← Older revision		Revision as of 23:44, 9 April 2026
Line 33:		Line 33:
	The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it		The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it
	here by providing link to git repo		here by providing link to git repo

			----

			[[Category:Studio]]

Victoria La at 14:11, 7 April 2026

2026-04-07T14:11:46Z

← Older revision		Revision as of 14:11, 7 April 2026
Line 1:		Line 1:
	~~tbd~~		This page is to share resources and advice about using AI for BGA development.
			== Overview ==

			At the point of writing (Apr 2026) there is no model that can successfully code meaningful game completely using BGA framework.
			But AI can be used for a lot of tasks, examples of usages:

			* Generating boilerplate code
			* Translating game rules from a rulebook into structured game logic and state machines
			* Writing and maintaining unit tests for game operations
			* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures
			* Debugging complex state machine flows by analyzing execution traces
			* Refactoring repetitive patterns across multiple operation classes
			* Writing client-side UI code (TypeScript/JS) for token rendering and animations
			* Reviewing code for common BGA framework pitfalls and anti-patterns
			* Generating CSS/SCSS for card layouts and sprite positioning from asset images
			* Explaining unfamiliar parts of the BGA framework or existing codebase


			== Setup ==
			To set up AI for success you need to add some documentation to your project, I suggest to use misc/docs folder.
			In addition you can run something like /init command to create initial AI document which it will use for your project.

			Files:
			* CLAUDE.md (or AI.md) - top-level project instructions that AI tools read automatically (would be in root of project)
			* RULES.md - exact rules converted from PDF (you can use AI to do that too. Make sure it is NOT summarized)
			* DESIGN.md - design of your game (software design) - if it does not exist ask AI to create software design document
			* PROCEDURES.md - add workflows that you want AI to follow (can reference explicit skills)
			* PLAN.md - implementation plan (when game is not complete)
			* TODO.md - todo list (when game is complete but few things left)
			* ASSETS.md - asset pipeline documentation (PDF sources, sprite sheets, conversion steps, sounds, fonts)

			== Skills ==
			The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it
			here by providing link to git repo

Victoria La: Created page with "tbd"

2026-04-07T13:54:28Z

Created page with "tbd"

New page

tbd