vibekits

# vibekits

AI Summary

Purpose:

• Repo-specific memory for vibekits, a personal React/Vite random tools and

casual browser games project.

Key points:

• Local path is ~/hw/project/vibekits.
• The README describes random decision tools and casual browser games built with

React, TypeScript, Vite, TailwindCSS, i18n, and Supabase-ready auth primitives.

• Current MVP evidence includes language-prefixed routes, roulette, Flappy Bird,

Supabase Auth hook, ranking placeholder, ad placeholder, and share button.

• The repo now contains many more tools/games in tests and TODO entries, but

public production usage metrics are Needs confirmation.

Relevant when:

• Working on Vibekits routes, games, random tools, ranking, sharing,

monetization, or portfolio/onboarding material.

Do not read full document unless:

• You need current commands, game architecture rules, or Supabase safety notes.

Linked documents:

• ai/workspace/repos.md
• ai/wiki/projects/vibekits.md
• ai/worklog/index.md

Repo Info

• Repo ID: vibekits
• Main branch: main
• Local path: ~/hw/project/vibekits
• Remote: [email protected]:hyunwook711/vibekits.git
• Latest observed commit: 4295cba 2026-05-29 Add dual rankings for home run derby

Common Commands

npm install
npm run dev
npm test -- --run
npm run build
npm run lint
npm run verify:games
npm run preview

Architecture Notes

• Client app stack: React 19, TypeScript, Vite, TailwindCSS, React Router,

react-i18next, Supabase client, Three.js, and cannon-es.

• Tests use Vitest, Testing Library, jsdom, and Playwright.
• URL structure is language-prefixed for Korean and English, with Japanese and

Traditional Chinese resource files prepared.

• Random tools and games are separated under src/tools/ and src/games/.
• Repo AGENTS.md requires game engine logic to remain separate from React UI.

React owns UI, ads, ranking, sharing, routing, and lifecycle controls; pure TypeScript game classes own loops, input, collision, scoring, rendering, and cleanup.

• Supabase global ranking is guarded by config and should remain disabled until

RLS and Edge Function validation are ready.

Known Pitfalls

• Never put Supabase secret keys, service-role keys, JWT secrets, database URLs,

or OAuth client secrets in VITE_* variables.

• Direct browser score inserts are forbidden; score submission should go through

a secure Edge Function path.

• Public deployment URL, traffic, revenue, and active user metrics are Needs

confirmation.

Current Work

• Personal portfolio/onboarding material is being generated from this repo.
• TODO.md shows remaining work around production Supabase ranking, result

sharing images, common game quality, and additional random tools.

Decisions

• Treat Vibekits as a standalone personal product/project portfolio item.
• Present verified features from README/package/tests and mark operations metrics

as Needs confirmation.

Open Questions

• Production domain and deployment state: Needs confirmation.
• Whether AdSense is live or only placeholder wiring: Needs confirmation.
• Whether global ranking has been deployed with RLS/Edge Function validation:

Needs confirmation.