仕事場

Selected production work

Make an impression.
Earn the trust.

Case studies for Web3 frontends and Figma builds, including the technical decisions and tradeoffs behind each one.

01ImpressionVisual conviction
02TrustEvidence in detail
03ConnectionA reason to talk
Atlas online48 frames · 6 sequences
稼働確認
02

Trust, made visible

One flagship, opened end to end.

信頼は細部に宿る
Rillex Casino
Scroll ↕
Preparing full preview…

Flagship system

Rillex Casino

Full-Stack Crypto Casino Frontend - Next.js 16, 22 Feature Modules, 6 Auth Methods, 20 Languages
01
22 feature modules with explicit boundaries
02
Cross-tab auth sync handles refresh timing
03
80-90% Figma fidelity through a token system
Inspect architecture and tradeoffs
03

Connection through range

Choose a case file. The evidence room responds.

触れて、確かめる
Evidence roommajor / 14 tools
WS: transaction connected - userId: 12345Deposit flow: `approve()` confirmed, `transfer()` sent, the API recorded it, then the transaction WebSocket reported the status.Theme: 'midnight-ocean' applied - CSS vars swapped, zero flash (class injected before hydration)Search: `pg soft` ran through `selectFilteredGames` and `selectVisibleGames`, then used the memoized selector chain.Cross-tab logout: received the broadcast, cleared Zustand, and removed the cookie.
実証

Web3

MemeWin - Web3 Crypto Casino Platform

Large-Scale Refactor - 54+ Providers, 9 EVM Chains, 8-Branch Zustand Tree, Runtime Theming, ~75K Lines

  • Three monolithic hooks became 21 focused modules
  • An eight-branch Zustand store keeps state work divided
  • Eleven OKLCh themes switch at runtime without a flash
Open the case file

The connection

Seen enough to start a real engineering conversation?

Bring the hard frontend problem: visual fidelity, Web3 state, real-time behavior, or the architecture that connects them.