<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.doc.boardgamearena.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Whez</id>
	<title>Board Game Arena - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.doc.boardgamearena.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Whez"/>
	<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/Special:Contributions/Whez"/>
	<updated>2026-11-16T17:21:23Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30683</id>
		<title>Using AI for BGA game development</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30683"/>
		<updated>2026-07-14T10:02:05Z</updated>

		<summary type="html">&lt;p&gt;Whez: /* Skills */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to share resources and advice about using AI for BGA development.&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
At the point of writing (Apr 2026) there is no model that can successfully code meaningful game completely using BGA framework.&lt;br /&gt;
But AI can be used for a lot of tasks, examples of usages:&lt;br /&gt;
&lt;br /&gt;
* Generating boilerplate code &lt;br /&gt;
* Translating game rules from a rulebook into structured game logic and state machines&lt;br /&gt;
* Writing and maintaining unit tests for game operations&lt;br /&gt;
* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures&lt;br /&gt;
* Debugging complex state machine flows by analyzing execution traces&lt;br /&gt;
* Extracting patterns across multiple open source games&lt;br /&gt;
* Writing client-side UI code (TypeScript/JS) for token rendering and animations&lt;br /&gt;
* Reviewing code for common BGA framework pitfalls and anti-patterns&lt;br /&gt;
* Generating CSS/SCSS for card layouts and sprite positioning from asset images&lt;br /&gt;
* Explaining unfamiliar parts of the BGA framework or existing codebase&lt;br /&gt;
* Reviewing against bga UI guildlines&lt;br /&gt;
* Migrating game from old framework&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
To set up AI for success you need to add some documentation to your project, I suggest to use misc/docs folder.&lt;br /&gt;
In addition you can run something like /init command to create initial AI document which it will use for your project.&lt;br /&gt;
&lt;br /&gt;
Files:&lt;br /&gt;
* CLAUDE.md (or AI.md) - top-level project instructions that AI tools read automatically (would be in root of project)&lt;br /&gt;
* RULES.md - exact rules converted from PDF (you can use AI to do that too. Make sure it is NOT summarized)&lt;br /&gt;
* DESIGN.md - design of your game (software design) - if it does not exist ask AI to create software design document&lt;br /&gt;
* PROCEDURES.md - add workflows that you want AI to follow (can reference explicit skills)&lt;br /&gt;
* PLAN.md - implementation plan (when game is not complete)&lt;br /&gt;
* TODO.md - todo list (when game is complete but few things left)&lt;br /&gt;
* ASSETS.md - asset pipeline documentation (PDF sources, sprite sheets, conversion steps, sounds, fonts)&lt;br /&gt;
&lt;br /&gt;
== Skills ==&lt;br /&gt;
The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it &lt;br /&gt;
here by providing link to git repo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== claude-code-bga — from rulebook to a testable game on Studio ===&lt;br /&gt;
[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:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Project setup&#039;&#039;&#039; — Makefile, SFTP deploy, config files, git workflow;&lt;br /&gt;
* &#039;&#039;&#039;Framework patterns&#039;&#039;&#039; — PHP state machine and ES6 client, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);&lt;br /&gt;
* &#039;&#039;&#039;Rules clarification&#039;&#039;&#039; — ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game&#039;s author, instead of being silently guessed;&lt;br /&gt;
* &#039;&#039;&#039;Automated deploy-and-test loop&#039;&#039;&#039; — 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);&lt;br /&gt;
* &#039;&#039;&#039;Known pitfalls&#039;&#039;&#039; — dbmodel.sql comments, table name conflicts, zombie handling, and other traps documented with their fixes.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Other resources ==&lt;br /&gt;
* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1uc7izy/i_added_a_clause_to_andrej_karpathys_4_claudemd/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1t4ncbj/10_things_about_claude_that_took_me_way_too_long/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
 [[Category:Studio]]&lt;/div&gt;</summary>
		<author><name>Whez</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30682</id>
		<title>Using AI for BGA game development</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30682"/>
		<updated>2026-07-14T09:24:15Z</updated>

		<summary type="html">&lt;p&gt;Whez: /* Skills */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to share resources and advice about using AI for BGA development.&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
At the point of writing (Apr 2026) there is no model that can successfully code meaningful game completely using BGA framework.&lt;br /&gt;
But AI can be used for a lot of tasks, examples of usages:&lt;br /&gt;
&lt;br /&gt;
* Generating boilerplate code &lt;br /&gt;
* Translating game rules from a rulebook into structured game logic and state machines&lt;br /&gt;
* Writing and maintaining unit tests for game operations&lt;br /&gt;
* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures&lt;br /&gt;
* Debugging complex state machine flows by analyzing execution traces&lt;br /&gt;
* Extracting patterns across multiple open source games&lt;br /&gt;
* Writing client-side UI code (TypeScript/JS) for token rendering and animations&lt;br /&gt;
* Reviewing code for common BGA framework pitfalls and anti-patterns&lt;br /&gt;
* Generating CSS/SCSS for card layouts and sprite positioning from asset images&lt;br /&gt;
* Explaining unfamiliar parts of the BGA framework or existing codebase&lt;br /&gt;
* Reviewing against bga UI guildlines&lt;br /&gt;
* Migrating game from old framework&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
To set up AI for success you need to add some documentation to your project, I suggest to use misc/docs folder.&lt;br /&gt;
In addition you can run something like /init command to create initial AI document which it will use for your project.&lt;br /&gt;
&lt;br /&gt;
Files:&lt;br /&gt;
* CLAUDE.md (or AI.md) - top-level project instructions that AI tools read automatically (would be in root of project)&lt;br /&gt;
* RULES.md - exact rules converted from PDF (you can use AI to do that too. Make sure it is NOT summarized)&lt;br /&gt;
* DESIGN.md - design of your game (software design) - if it does not exist ask AI to create software design document&lt;br /&gt;
* PROCEDURES.md - add workflows that you want AI to follow (can reference explicit skills)&lt;br /&gt;
* PLAN.md - implementation plan (when game is not complete)&lt;br /&gt;
* TODO.md - todo list (when game is complete but few things left)&lt;br /&gt;
* ASSETS.md - asset pipeline documentation (PDF sources, sprite sheets, conversion steps, sounds, fonts)&lt;br /&gt;
&lt;br /&gt;
== Skills ==&lt;br /&gt;
The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it &lt;br /&gt;
here by providing link to git repo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;claude-code-bga&#039;&#039;&#039; ([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:&lt;br /&gt;
* project setup: Makefile, SFTP deploy, config files, git workflow;&lt;br /&gt;
* PHP state-machine and ES6 client patterns, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);&lt;br /&gt;
* a rules-clarification workflow: ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game&#039;s author, instead of being silently guessed;&lt;br /&gt;
* 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);&lt;br /&gt;
* a list of known BGA pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Other resources ==&lt;br /&gt;
* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1uc7izy/i_added_a_clause_to_andrej_karpathys_4_claudemd/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1t4ncbj/10_things_about_claude_that_took_me_way_too_long/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
 [[Category:Studio]]&lt;/div&gt;</summary>
		<author><name>Whez</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30681</id>
		<title>Using AI for BGA game development</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Using_AI_for_BGA_game_development&amp;diff=30681"/>
		<updated>2026-07-14T09:18:41Z</updated>

		<summary type="html">&lt;p&gt;Whez: /* Skills */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page is to share resources and advice about using AI for BGA development.&lt;br /&gt;
== Overview ==&lt;br /&gt;
&lt;br /&gt;
At the point of writing (Apr 2026) there is no model that can successfully code meaningful game completely using BGA framework.&lt;br /&gt;
But AI can be used for a lot of tasks, examples of usages:&lt;br /&gt;
&lt;br /&gt;
* Generating boilerplate code &lt;br /&gt;
* Translating game rules from a rulebook into structured game logic and state machines&lt;br /&gt;
* Writing and maintaining unit tests for game operations&lt;br /&gt;
* Converting game material (cards, tokens, boards) from spreadsheets into PHP data structures&lt;br /&gt;
* Debugging complex state machine flows by analyzing execution traces&lt;br /&gt;
* Extracting patterns across multiple open source games&lt;br /&gt;
* Writing client-side UI code (TypeScript/JS) for token rendering and animations&lt;br /&gt;
* Reviewing code for common BGA framework pitfalls and anti-patterns&lt;br /&gt;
* Generating CSS/SCSS for card layouts and sprite positioning from asset images&lt;br /&gt;
* Explaining unfamiliar parts of the BGA framework or existing codebase&lt;br /&gt;
* Reviewing against bga UI guildlines&lt;br /&gt;
* Migrating game from old framework&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
To set up AI for success you need to add some documentation to your project, I suggest to use misc/docs folder.&lt;br /&gt;
In addition you can run something like /init command to create initial AI document which it will use for your project.&lt;br /&gt;
&lt;br /&gt;
Files:&lt;br /&gt;
* CLAUDE.md (or AI.md) - top-level project instructions that AI tools read automatically (would be in root of project)&lt;br /&gt;
* RULES.md - exact rules converted from PDF (you can use AI to do that too. Make sure it is NOT summarized)&lt;br /&gt;
* DESIGN.md - design of your game (software design) - if it does not exist ask AI to create software design document&lt;br /&gt;
* PROCEDURES.md - add workflows that you want AI to follow (can reference explicit skills)&lt;br /&gt;
* PLAN.md - implementation plan (when game is not complete)&lt;br /&gt;
* TODO.md - todo list (when game is complete but few things left)&lt;br /&gt;
* ASSETS.md - asset pipeline documentation (PDF sources, sprite sheets, conversion steps, sounds, fonts)&lt;br /&gt;
&lt;br /&gt;
== Skills ==&lt;br /&gt;
The best way to save the workflows is to use skills. If you developed some AI skills I suggest sharing it &lt;br /&gt;
here by providing link to git repo&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;claude-code-bga&#039;&#039;&#039; ([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:&lt;br /&gt;
*project setup: Makefile, SFTP deploy, config files, git workflow;&lt;br /&gt;
*PHP state-machine and ES6 client patterns, plus on-demand reference guides for the standard BGA libraries (Deck, BgaCards, Stock, Counter, Scrollmap, …);&lt;br /&gt;
*a rules-clarification workflow: ambiguities found during implementation are logged as tracked questions and assumptions to discuss with the game&#039;s author, instead of being silently guessed;&lt;br /&gt;
*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);&lt;br /&gt;
* a list of known BGA pitfalls (dbmodel.sql comments, table name conflicts, zombie handling, …).&lt;br /&gt;
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.&lt;br /&gt;
== Other resources ==&lt;br /&gt;
* Chrome MCP server allows AI to see the real game https://developer.chrome.com/blog/chrome-devtools-mcp&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1us9hfz/asked_claude_what_in_my_docs_was_hurting_its/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1uc7izy/i_added_a_clause_to_andrej_karpathys_4_claudemd/&lt;br /&gt;
* https://www.reddit.com/r/ClaudeAI/comments/1t4ncbj/10_things_about_claude_that_took_me_way_too_long/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
 [[Category:Studio]]&lt;/div&gt;</summary>
		<author><name>Whez</name></author>
	</entry>
</feed>