Flower Reversi
Reversi with flowers instead of discs: red dahlias against blue nemophilas, with petals scattering as each captured flower turns. The developer says Claude Code wrote all the code from a phone chat.
Official site tinkling-way-games.github.io, verified Nov 3, 2026. Linked as the play link (ブラウザで遊ぶ) in the README of the developer's tinkling-way-games/flower-reversi repository and in the developer's Qiita article.
Where to play
Every platform this game is on. Links are checked against official sources; we never host or mirror games.
- Play free — official siteBrowserReleasedFree
Runs in a desktop or mobile browser. No download.
Browser (no download) · Mobile · Official link verified Nov 3, 2026.
- View on GitHubGitHubReleased · Source code; no licence fileFree
Download from the GitHub releases page.
Desktop · Official link verified Nov 3, 2026.
About Flower Reversi
Flower Reversi is a free browser version of reversi, made to be played upright on a phone. The rules are the usual ones on an 8×8 board, with red moving first, but the pieces are flowers: red is a layered dahlia with a gold centre, blue a small five-petalled nemophila. A placed flower opens, and captured flowers turn one after another, nearest first, shedding petals in the new colour; each colour has its own synthesized sound. You can play the computer at three levels (random moves; a one-move look-ahead that likes corners; a four-move search that reads the endgame to the finish once ten or fewer squares are left) or pass one device between two players, with a hand-over screen between turns. Wins against the computer earn flower points, which unlock cosmetic flowers, boards and effects in a “flower garden”: camellia and peony for red, Chinese bellflower and hydrangea for blue, night and cherry-blossom boards, and a petal-storm effect. Records stay in the browser. The developer, TinklingWay, says the game went from first commit to last merged pull request in about three and a half hours on a Sunday evening, with Claude Code on the web driven from an iPhone; the developer wrote no code, made the requests, played it on the phone, reported bugs and merged the pull requests. Free, in Japanese.
How it was built
VerifiedThe README says the game was planned, implemented and published by operating Claude Code on the web from a phone: Claude Code wrote the code and the documentation, while the human made requests, played it on the phone, reported impressions and bugs, and merged the pull requests. In the developer's Qiita article (29 Sep 2026) the developer says they wrote not a single line of code; the work ran through the Claude mobile app and Claude Code on the web, and pull requests #2 to #7 all went “chat on the phone, Claude pushes, I merge”. One commit is in the developer's name because it was made from a PC, but the article says Claude wrote it. Claude also proposed the on-screen debug view (add ?debug to the URL) used to report bugs by screenshot, and fixed the phone overheating the developer reported. A security review was run with the Claude Code CLI and the GitHub Copilot extension in VS Code; the article does not say Copilot wrote game code.
- DeveloperQiita article: “私が書いたコードは1行もない。” (I wrote not one line of code); “発案は私、実装はClaude Code。” — Qiita (ちりん / TinklingWay)
Plain ES modules (JavaScript) and SVG with no framework, game engine, build step or external assets; sound effects are synthesized with Web Audio. Because the cloud container could not reach the npm registry, Claude set up tests, a dev server, a build and static checks using only Node.js built-ins (node --test, scripts/*.mjs) and JSDoc instead of TypeScript. The board rules and the computer player are checked with unit tests, and the look with phone-width screenshots taken in a browser inside the container. To keep the iPhone from heating up, endless animations and on-board CSS filters were removed and the number of petal particles is capped. A Content-Security-Policy blocks external loading and sending, and records are kept only in localStorage. Static hosting on GitHub Pages.
- Engine / framework
- None (vanilla JavaScript and SVG)
- Languages
- JavaScript
- Team size
- 1 (solo)Developer ReportedQiita (ちりん / TinklingWay)
- Initial build time
- About 3.5 hours, from the first commit at 20:02 to the last merged pull request at 23:28 on one eveningDeveloper ReportedQiita (ちりん / TinklingWay)
- Development time
- Not disclosed
- Development cost
- Not disclosed
- AI-written code
- ~100% of shipped codeDeveloper ReportedQiita (ちりん / TinklingWay)
“コードとドキュメントは Claude Code が書き、人間は要望を出す・スマホで遊んで感想や不具合を伝える・PR をマージする役に回っている。”- Building games by chat from the living room (Qiita, Japanese)
- tinkling-way-games/flower-reversi on GitHub
Verification notes: AI use, rules, modes, computer levels, the flower garden and the tech notes from the repository README (read as a raw file); the timeline, the three bug fixes and the zero-lines-of-code statement from the developer's Qiita article of 29 Sep 2026, which links both the play page and the repository. The article gives clock times but no calendar date for the build; it says Crackout was made the day before and its repository was moved the next day, with a check during the move dated 27 Sep 2026 01:50 JST, which points to the evening of Sunday 27 Sep 2026 itself; as the date is not stated, the release date is left blank. The repositories were moved from a personal account to the tinkling-way-games organization; the repository has no licence file, so the game is not marked open source. The play page (page language ja) loaded on 4 Nov 2026; its Content-Security-Policy allows no outside connections, so it cannot call AI services. The developer's location is not stated. The game was not played.
Development history
- A Sunday evening in late September 2026
Built in about three and a half hours with Claude Code on the web, operated from a phone, and published on GitHub Pages.
DeveloperQiita (ちりん / TinklingWay) The developer publishes an article on Qiita about building Crackout and Flower Reversi by chat with Claude Code.
DeveloperQiita (ちりん / TinklingWay)
Game performance
Each figure measures something different — concurrent players, owners, downloads and sales are never interchangeable and are never added together. Labels show where each number comes from.
Browser (official site)
No public metrics recorded for this listing.
Not publicly available: Concurrent players (site), Monthly revenue, Gross revenue.
GitHub
No public metrics recorded for this listing.
Not publicly available: GitHub stars.
Sales & revenue (all platforms)
Browser game — there are no downloads to count.
Reviews & rankings
Not yet reviewed by our editors.
Not currently ranked.
Sources
| Source | Type | Published | Accessed |
|---|---|---|---|
| Flower Reversi — 花を咲かせるリバーシ (README) GitHub (tinkling-way-games) · Japanese | Repository | Not confirmed | Nov 3, 2026 |
| リビングでゴロゴロしながら、チャットだけで数時間でゲームを公開した話 Qiita (ちりん / TinklingWay) · Japanese | Devlog | Sep 29, 2026 | Nov 3, 2026 |
| Official game page (language check) TinklingWay | Official site | Not confirmed | Nov 3, 2026 |
Similar games
