lexx-lazz/lil-guys

Purpose and Entry Point

Lil Guys is a small shared virtual-pet care application. Users anonymously join a common pet collection, adopt pets, feed them, and observe synchronized happiness changes. The browser entry point is index.html; it contains the UI, client-side behavior, styling integration, and Firebase interaction.

Client Application Shell

index.html is the application’s primary runtime boundary: it renders the responsive pet-management interface and executes the JavaScript needed for adoption, selection, feeding, cooldown visualization, mood display, and speech bubbles. Tailwind CSS is used for presentation, likely loaded or configured directly from this single-page entry.

Identity and Shared Access

Firebase Authentication provides anonymous sign-in so each browser can access the shared application without account setup. Firebase project selection and deployment aliases are defined in .firebaserc; the Firebase hosting/runtime configuration is in firebase.json.

Real-Time Pet State

Cloud Firestore is the authoritative shared state store. The client reads pet records in real time and writes adoption/feed updates, allowing every connected participant to observe the same list and changing happiness values. Firestore query/index requirements are captured in firestore.indexes.json.

Pet-Care Domain Behavior

The browser-side domain logic manages:

• Pet type and name creation during adoption.

• Food preference effects that raise or lower happiness.

• Feeding cooldown/“chewing” state and its visual meter.

• Happiness decay on a 12-hour cadence.

• Mood-derived happiness bars, emoji, and periodically displayed speech bubbles.

This logic is client-driven but persists shared outcomes through Firestore, making database updates the synchronization boundary.

Security and Deployment Boundaries

Firestore access policy is enforced independently of the browser by firestore.rules, which should constrain anonymous users to the intended shared-pet operations. Firebase Hosting deployment and other Firebase service settings are defined by firebase.json; .firebaserc selects the target Firebase project.

Primary Flow

1. Browser loads index.html.

2. Client anonymously authenticates with Firebase.

3. Client subscribes to Firestore pet data and renders the shared collection.

4. User adopts or feeds a selected pet; client calculates local domain effects and writes updated state.

5. Firestore propagates updates to all subscribed clients.

6. Client continuously derives UI state such as cooldown progress, happiness decay eligibility, mood, and speech from pet records and time.