One design system for the website, admin, owner portal, POS and app. Start with the design guide, then the complete mockups, then the plan that takes it into the monorepo.
Tokens, Archivo type, tiles, buttons, lists, data, score tracker, POS, motion, voice and the component catalogue.
Open guide →Branching (one PR at the end), shared packages, parity rules, and the waves of parallel agents.
Read plan →About 40 decisions the mockups surfaced (money, the Jadwal timeline, navigation, copy, the app), each with my recommendation.
Answer →The new v2 design doc that replaces docs/DESIGN-SYSTEM.md.
Read →kakimahjong.com: every route in the approved player’s-view style, including booking end to end and /game.
Open →The web POS on a tablet: floor, bill and payment, the new Jadwal timeline, check-in, tabs, open play and more.
Open →The venue owner’s dashboard, locations, pricing, coaches, finance, reports and settings.
Open →Every admin route: overview, venues, bookings, money, users, moderation, staff and audit.
Open →Every screen of the consumer app: tabs, booking and QRIS, Cari Kaki, events, tournaments, clubs, chat, the score tracker, and account. The direction isn’t final yet.
Open →Today’s tracker flow in the new design (Riichi, Chombo, Catat menang, Seri, End game), clickable, to compare with Flow 2.
Play it →A clickable prototype of the new buttons (New hand, Delete last hand, End game, Cancel game) and the reordered New hand flow, with real Riichi points.
Play it →Flow 2 for Hong Kong and ITM: everything today’s tracker does (multi-win, Hitung poin, tile pad with kim, “Pilih susunan tangan”, dice, half game), with only the new step order and the 4 table buttons. Switch with Riichi · HKM · ITM at the top.
Play it →The app tracker’s table as it is (Kong, Catat kemenangan, Ronde buntu, Akhiri permainan). Catat kemenangan opens ONE scrolling page: who HU, buangan or zi mo, who discarded, points, result. Kong opens its own sheet: who made the kong and which kong (hong zhong, am kong, 4 bunga…).
Play it →The POS “Papan peringkat” for owners and operators, the owner’s settings (boards, periods, new season with typed confirmation, TV link), the 16:9 TV screen and the /book/[venue] board tab, all reading one setting. The settings are clickable and every screen follows.
Open →Four layouts for the host’s Cari Kaki screen: tap an empty seat to add a player or make someone host (co-host), instead of two stacked buttons. Pick A, B, C or D.
Compare →The score tracker with a 4th Chicken Hand tab (ITM stays the default), the name step laid out clockwise East → South → West → North, counting with variant C, and End game → save or not. Switch Indonesian / English: the wind names follow.
Play it →Four layouts for the same fast flow: press HU!, tap the winner, counted. No confirm, a +1 animation shows who got it, and a full-size Undo is always on screen. Meja, Kipas, Kuadran and Geser (hold HU! and slide).
Try them →Same design as the real tournament manager (Ringkasan, Peserta table, Penempatan with drag/tap swap + search, Meja langsung, Klasemen, Host, Aturan). Chicken Hand only changes the scoring (hu) and adds Batas per meja: rounds (− / +, 16 default) or a time picker.
Open it →Each player has their own − / + hu counter: tap + and it counts, no select-then-confirm. Open it next to the manager in the same browser and Meja 3 updates live.
Play it →A new score tracker mode that only counts hu: a new hand asks only who won (one or more) or a draw, and tapping a name on the board opens it with that player picked. Includes the recap and the Chicken Hand leaderboard (hu, then games, then who got there first).
Play it →A clickable simulation of the new coach feature across the venue POS, the coach POS and the player app: create a coach, recurring and date schedules, the add-on at booking, accept, then pay within 24 hours. It has 10 runnable test cases, a live Inbox of emails, WhatsApp and POS notifications, and the open questions.
Play it →A clickable proposal for the first-run flow: value first, guest browsing, sign-in only when needed, and every question asked in context. Includes old vs new mapping and open questions.
Play it →How venue prices read on the app and the mobile website. 1 · Sekarang (live since 3 Nov: the cheapest price, then weekday and weekend packages mixed together) and 2 · Dengan harga akhir pekan (weekday and weekend prices side by side, with the price for the picked day marked).
Compare →The first rounds: the app ideas, Cari Kaki options, the three website directions and the colour comparison.
Open →Every route, action, state and API call.
Open →Web POS vs native POS, plus the new Jadwal timeline.
Open →Locations, pricing, finance and operators.
Open →Every admin action and its guard rails.
Open →The consumer app’s full inventory, for the later app redesign.
Open →How the token and component packages plug into Next and Expo.
Open →redesign/v2. One PR to main when it has been tested.