Labels and Tags
Organise records with reusable labels you can filter by.
What it adds
A label catalog with a defined scope, normalised names, safe rename and delete, and label-based filtering on every list.
What your agent is told to do
5
What your agent is told to do
5-
1
Decide the scope of the catalog before anything else — per user, per workspace, or global — and enforce it in every query. Mixing scopes later is a migration, not a setting.
-
2
Normalise names on the way in: trim whitespace, collapse internal spaces, and compare case-insensitively so 'Urgent', 'urgent' and ' urgent ' cannot coexist. Store the display form the user typed.
-
3
Make rename a true rename on the label record, so every record already carrying it updates at once. Never implement rename as delete-and-recreate.
-
4
Deleting a label must remove it from every record that has it in the same operation, and must warn with the affected count first. An assignment pointing at a deleted label is a bug that shows up as a blank chip months later.
-
5
Add label filtering to every list that shows these records, including combining multiple labels. Do not build a new chip-entry control for assigning labels — that input is owned by Tag Input; use it.
Edge cases it handles
6
Edge cases it handles
6- Role-gated creation: some apps want anyone to apply labels but only admins to create new ones. Make that a setting, not a hardcoded rule.
- Colour is decoration, never the only signal — a label must be identifiable by its name for colour-blind users and in monochrome contexts.
- Cap the number of labels per record and the label name length, and say so before the user hits the limit.
- Merging two labels that mean the same thing must reassign records without creating duplicate assignments.
- A record whose labels the viewer cannot all see must not leak the hidden ones through filter counts or autocomplete.
- Filtering by several labels needs a defined meaning — all of them or any of them — shown in the UI rather than assumed.
Definition of done
8
Definition of done
8- Label scope is enforced in every query, with no cross-scope leakage.
- Names are normalised so case and whitespace variants cannot create duplicates.
- Renaming updates every record instantly; deleting removes assignments and warns with a count first.
- Label creation can be restricted by role independently of label use.
- Every list showing these records can be filtered by one or more labels, with the combining rule stated.
- Assignment uses the existing tag input control rather than a new one.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Location Map Block
Location Map Block
Put an interactive map on a page showing one location or a whole list of them.
What it does
A reusable map block rendering one or many pinned locations, with a static fallback and a text address alternative.
How it works
- 1 The app already has Mapbox Geocoding and Google Places Address Lookup. Turn addresses into coordinates through the existing integration and store the result on the record; do not add a second geocoding path for this block.
- 2 Make the block take either a single location or a collection, and render the same component for both. A one-pin map is a collection of one, not a separate feature.
- 3 Reserve the block's height before the map initialises so the surrounding page does not jump when tiles arrive. The placeholder should occupy exactly the space the map will fill.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/location-map-block
Weather Widget
Weather Widget
Show current conditions and a short forecast for a place your users care about.
What it does
A compact widget showing current conditions and a few days of forecast for a chosen location.
How it works
- 1 Add this as a tile in the app's existing Customizable Dashboard Widgets rather than as a fixed element bolted into a layout, so users who do not want it can remove it.
- 2 Fetch the forecast on the server on a schedule and serve the widget from the app's own cache. Calling the weather source from every visitor's browser leaks the credential and multiplies the request count by your traffic.
- 3 Show the observation time alongside the reading, and reuse the app's Stale Data Indicator conventions so ageing weather looks the same as any other ageing data in the product.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/weather-widget
Record Merge
Record Merge
Combine two duplicate records into one without losing anything attached.
What it does
A merge flow that picks a surviving value per field, reparents all related data, redirects old references, and can be audited afterwards.
How it works
- 1 Show the two records side by side, field by field, and require an explicit survivor for every field where they differ. Do not default to 'newest wins' silently; the user is merging because they know which one is right.
- 2 Reparent every related object — children, comments, attachments, activity, links, memberships — onto the survivor in a single transaction. A half-finished merge is worse than two duplicates.
- 3 Detect relationships that would become duplicates after reparenting (the same person as a member of both records, the same tag applied twice) and collapse them rather than violating a uniqueness constraint mid-merge.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/record-merge
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.