Step 1 of 10
Inspect the existing chat architecture and choose presence data flow
Establish where WebSocket connections, user identity, and chat participants already exist so presence can be added without breaking the app.
Presence works best when the builder first maps the current auth, chat, and socket layers instead of generating a parallel system.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Inspect the current codebase and summarize the existing architecture for auth, chat conversations, messages, frontend state, and any real-time transport. Identify where the authenticated user ID becomes available, where chat participants are loaded, whether WebSockets or Socket.IO already exist, and where presence state should live on both backend and frontend. Produce a concrete implementation plan with files to edit, server events to add, client listeners to add, and how presence should be scoped to relevant conversations or participants.
Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.
Actual change check
Expected after this step
A clear integration plan that maps current auth, sockets, conversations, and UI components to the new presence system.
Should NOT happen
- An existing feature broke
- A button only logs to console
- Data disappears after refresh
- Errors fail silently with no visible state
This is what should exist before you continue. If reality does not match, do not move on.
Track what changed, failed, or needs follow-up. Notes export with the flow.