No offense, your How to Play page is full of Lorem Ipsum, I think you could get more out of search/heuristics before you need to burn $10,000 - $100,000 on H100s.

I’ve mostly used AI to code this project

first, optimize the FUCK out of your How to Play document. I read the first document I could find and I wasn’t sure if you move all your dudes in one turn or if you move only one dude each turn. You need a “cheatsheet” type reference document for mid-to-experienced players, a document designed for people who might not even know how to play chess/checkers/go, and you need a youtube video, and you need an FAQ. I didn’t think what you had was bad, just incomplete and not battle tested against hordes of new players. If you game’s GUI is really well designed, this could alleviate the burden for solid documentation, but you probably can’t send that to an AI. Then have clear documentation on the APIs and data structures a bot would have access to in order to read the game state it was access to (probably simple, as I did not see fog of war elements), and the APIs it would use to place moves.

Give all of this (minus the youtube video) to both chatGPT and claude. see if chatgpt/claude have advice on how to make the interface for potential bots better. If possible, spend time optimizing this first.

Give all of this (minus the youtube video) to both chatGPT and claude. Tell you it you want a design document markdown file for building V2 of your game bot code. I suggest allowing the user to pick if they face against V1 or V2 of your game bot. You’ll need to include that in the scope of the design document. Ask it to ask you a shitload of clarifying questions. You should eventually acquire a single design document. You should spend a lot of time on this document before moving forward, even if you’re just vibe chating chatgpt the whole time. If chatGPT/claude doesn’t ask you upgrade from free to the first paid tier at least once, you might need to spend more time on the design document. Read and fact check the final document. Commit this to your repo’s docs folder.

Then ask chatGPT and/or claude for a task list markdown file optimized for zencoder/kiro’s spec driver design feature. Open a new account in only one of those (zencoder: you have one week to use 770/day premium AI API calls per day, Kiro: you have 30 days to use 1000 credits). Last time I checked, neither require a credit card to get started. If you’re already paying for claude code and don’t want to open an account for free AI trials, try claude code’s “planning mode” feature. Only pick one tool, you should be able to accomplish this using only one of these. After you picked one, make sure to open them up to the spec-driven-design feature. give them the design document markdown file and task list markdown file. Kiro/Zencoder should translate the documents into it’s own preferred format, then be able to work on the tasks sequentially under your supervision.

You should have enough remaining credits to fix broken tests (or add tests), make amendments, or you can blow them on unrelated new features.