add-analyticslisted
Install: claude install-skill sesori-ai/sesori_apps_monorepo
# add-analytics
Design analytics that answer a product question without creating misleading or
sensitive data.
## Before adding an event
An event is worthwhile only when all of these are concrete:
1. **Decision:** What product decision or investor metric changes if this moves?
2. **Meaning:** Is it an intent, confirmed outcome, state transition, or view?
3. **Authority:** Which business success/failure seam proves it happened?
4. **Population:** Is the unit an account, installation, or action? Never mix
those denominators under one label.
5. **Privacy:** Can every parameter be a bounded enum/boolean or explicitly
approved scalar without code, content, paths, identity, or entity IDs?
6. **Reporting:** Which curated model/view consumes it, and how are coverage,
maturity, freshness, and deduplication handled?
If the answer is only “this button was tapped,” skip it unless that tap is the
only honest signal for a defined funnel step.
## Current and planned seams
The source of truth is the closed models under
`client/module_core/lib/src/foundation/models/product_analytics/`, with
repository delivery/preference records under `repositories/models/` and service
state under `services/models/`:
- Consumers call `ProductAnalyticsService` for authenticated account-linked
events.
- Five approved account-less authentication events call
`InstallationAnalyticsService`: the started/completed/failed attempt funnel
plus Firebase's recommended `sign_up` and `login` outcomes