Goal Tracking
Let people define an outcome and watch progress toward it.
What it adds
User-defined goals built on tracked events or metrics, with a target, a period, and progress that stays truthful as definitions change.
What your agent is told to do
6
What your agent is told to do
6-
1
Let a user define a goal as a metric or event, a target value, and a period, and show progress as both the raw figure and the fraction of target.
-
2
Scope goals explicitly to a user, a workspace, or the whole account, and make the scope visible on the goal. An ambiguous goal is argued about in meetings.
-
3
Version goal definitions. When someone edits a target or a metric, create a new version rather than mutating the old one, so past periods keep the numbers they were judged on.
-
4
Show pace against the period — whether the goal is on track for the time elapsed — not just the total so far.
-
5
Do NOT silently recalculate historical periods when a definition changes. Retroactively rewriting a hit goal into a miss destroys trust in the whole dashboard.
-
6
Attribute each event to a period by a defined timestamp — when it occurred, not when it was ingested.
Edge cases it handles
7
Edge cases it handles
7- Events arriving late must land in the period they occurred in, and the affected figure must be marked as recently revised.
- Duplicate events must be deduplicated by a stable identifier before they count toward a goal.
- A goal whose underlying metric or event is deleted must show as broken rather than reading zero — zero looks like failure, not absence.
- Changing the period mid-flight changes the denominator; show the old period's result rather than reshaping it.
- A completed goal needs a terminal state, not a progress bar stuck at 100%.
- Timezone matters for daily and weekly goals — a goal that resets at the wrong midnight is wrong every day.
- Users must not be able to create a goal against data they cannot otherwise see; check permissions at definition time and again at read time.
Definition of done
8
Definition of done
8- A goal has a metric, target, period, and explicit scope, all visible on the goal.
- Editing a goal creates a new version and leaves past periods unchanged.
- Progress shows both absolute value and pace against elapsed time.
- Late events land in the period they occurred in; duplicates are excluded.
- A goal with a missing or inaccessible metric reads as broken, not zero.
- Completed and failed goals have terminal states.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
UI Event Naming Schema
UI Event Naming Schema
Give every tracked interaction a name that still means the same thing in a year.
What it does
A documented vocabulary and structure for event names and properties, applied across the app's existing tracking.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ui-event-naming-schema
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
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
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.