UI Event Naming Schema
Give every tracked interaction a name that still means the same thing in a year.
What it adds
A documented vocabulary and structure for event names and properties, applied across the app's existing tracking.
What your agent is told to do
5
What your agent is told to do
5-
1
Audit the events the app already sends and list them. The duplicates, the near-synonyms, and the ones nobody can explain are the reason the schema is needed, and they are also the migration list.
-
2
Fix a structure of object, action, and context: what was acted on, what happened to it, and where. Fix a closed set of actions — viewed, clicked, opened, submitted, selected, failed — and require every new event to reuse one of them.
-
3
Keep variable detail in properties, never in the name. A record identifier, a plan name, or a workspace slug baked into an event name produces thousands of unaggregatable one-off events.
-
4
Separate product events, which describe what a user achieved, from operational events, which describe how the interface behaved. They have different audiences, different retention, and often different destinations.
-
5
Version the schema and treat a change of meaning as a new name rather than a redefinition. A chart that silently changes what it counts halfway through is worse than one that visibly breaks.
Edge cases it handles
7
Edge cases it handles
7- Without a fixed object, action, and context structure, two teams will record the same interaction under three names and the numbers will never reconcile. The structure has to be enforced at the point events are declared, not agreed informally.
- Identifiers, search terms, and other variable values in event names create unbounded cardinality that no analytics tool can aggregate and every analytics bill will reflect. They belong in properties.
- A breaking change needs a new name and an overlap period where both are sent, so historical comparisons stay possible rather than showing a cliff on the day of the rename.
- Product and operational events must be distinguishable at a glance, because an operational event counted as product usage inflates engagement with things like retries and background refreshes.
- Property names and value shapes need the same discipline as event names; the same concept appearing as workspaceId in one event and workspace in another defeats every join.
- The schema must cover failures as first-class events, not just successes, or the funnel shows what worked and nothing about what did not.
- A deprecated name must remain documented after it stops being sent, so anyone reading an old dashboard can tell what it used to mean.
Definition of done
9
Definition of done
9- Every event in the app follows the documented object, action, and context structure.
- Actions come from a fixed, published list rather than being invented per screen.
- No event name contains an identifier, a search term, or any other variable value.
- Product and operational events are separated and labelled.
- Property names and value shapes are consistent across every event that carries them.
- Breaking changes ship as new names with a documented overlap period.
- The existing events that predated the schema have been migrated or explicitly deprecated in writing.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Segment Event Forwarding
Segment Event Forwarding
Send one clean stream of product events to Segment and let it fan out downstream.
What it does
A documented event schema and a single forwarding path emitting track, identify, group, and page calls with consistent identity.
How it works
- 1 Write the event schema before writing any code: the exact set of event names, the properties each carries with their types, and the traits attached to a user and to an account. Every downstream tool inherits this schema, so a name chosen carelessly is expensive to change later.
- 2 Establish one identity model and apply it everywhere. Use a stable internal user identifier that never changes, associate the anonymous identifier from the first visit with it at signup, and attach the account or workspace so downstream tools can roll events up by customer.
- 3 Route every event through one internal emitter rather than calling the provider from feature code. That emitter validates the event against the schema, drops or flags anything unrecognised, and is the single place where identity and default properties are attached.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/segment-event-forwarding
Data Table Cell Primitives
Data Table Cell Primitives
Render every kind of table cell the same way, wherever the table happens to be.
What it does
A shared set of cell renderers for numbers, dates, people, statuses, links, and row actions, used by every table in the app.
How it works
- 1 Catalogue the cell types the app's tables already render and reduce them to a small set: number and currency, date and relative time, person or avatar, status or badge, link or identifier, and an actions cell.
- 2 Separate each cell's underlying value from its presentation, so sorting, filtering, grouping, and export operate on the raw value while the user sees the formatted one.
- 3 Align and format numerically consistent cells the same way everywhere — figures right-aligned with tabular figures and a fixed precision per column, dates in the user's locale and time zone, currency with its code where more than one is possible.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/data-table-cell-primitives
Interaction Telemetry Guardrails
Interaction Telemetry Guardrails
Collect useful interaction signal without recording what people type or read.
What it does
Redaction, sampling, and consent rules applied to interaction events before they leave the browser.
How it works
- 1 Set the default to sending no content. An event records that a thing was interacted with, its type and its identifier; it does not record the text inside it unless that field is explicitly listed as safe.
- 2 Redact at the point of collection rather than after ingestion. Once a customer's message body reaches the analytics vendor, deleting it is a support request to a third party and a disclosure you have already made.
- 3 Sample the high-frequency signals — scrolling, hovering, typing, resizing — at a rate recorded on the event itself, so the numbers can be scaled back up correctly instead of being read as raw counts.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/interaction-telemetry-guardrails
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.