A little wiser. With every build.

Vite as the vibe-coding engine

Vite is useful because it protects the build flow: fast dev server, fast HMR, simple config, and a production build that still forces reality checks.

For full vibe coding, use Vite as the fast loop, but keep a separate gate for typecheck, build, route checks, and broken-asset checks.

Background music changes the room

A poker table is not only rules and cards. Ambient sound makes the browser feel less empty and more like a shared room.

Music should support the table mood without stealing control from the player.

Click button feedback is part of trust

In a realtime card game, a button that does not answer back feels broken even when the code works.

Every important action needs an immediate signal: pressed, loading, accepted, blocked, or failed.

Firebase lifetime storage as table memory

Firebase turns a browser game from temporary screen state into a table that can survive refreshes, reconnects, and shared links.

Realtime storage is not just where data sits. It defines what the table remembers and what must be cleaned up.

Reusable skills across projects

Every project should be able to produce reusable skills: build loops, UX decisions, data patterns, and product judgment that can move into the next project.

The point of the knowledge base is to turn scattered build pain into reusable operating memory, then make that memory one click away from becoming a skill.

Tag Registry and RAG flow

RAG is useful for retrieval and suggestion, but the source of truth should stay in structured wiki notes, Skill Cards, and a controlled tag registry.

Do not dump everything into a vector database. Build a clean knowledge layer first, then use RAG as the retrieval layer on top.

Keep what the work teaches you.

Each note keeps what was learned, why it matters, and how to reuse it. Original sources stay intact; the LLM maintains the wiki. Checked methods can become executable skills.