Table Column Chooser
Let users choose which columns matter instead of forcing one table layout on everyone.
What it adds
A control for showing, hiding, and reordering table columns, driven by a column definition rather than markup.
What your agent is told to do
5
What your agent is told to do
5-
1
Derive the chooser from a single column definition that also drives the table itself. Two lists will drift apart.
-
2
Filter the offered columns by permission before rendering. A column the user cannot read must not appear in the chooser at all, not even greyed out — its presence leaks the shape of the data.
-
3
Mark identity and action columns as required so they cannot be hidden. A table with no way to tell rows apart or act on them is broken, not customised.
-
4
Provide a reset to the default column set, always reachable, including when the user has hidden almost everything.
-
5
Storage, scoping to device or account or workspace, and applying the saved choice before first paint are owned by Persistent View Preferences; use that mechanism rather than inventing a second one.
Edge cases it handles
6
Edge cases it handles
6- A saved choice referencing a renamed or deleted column must be migrated or dropped silently, never crash the table.
- A newly added column needs a defined default: visible for everyone, or hidden until chosen. Decide, and state it.
- Hiding a column that is currently the sort key must either clear the sort or keep sorting by it with an explanation.
- Hiding a column must not remove it from exports unless the user asked for that — say which behaviour applies.
- The chooser must be usable with a keyboard, and reordering must have a keyboard path, not drag only.
- With many columns the chooser needs its own search and grouping, or it becomes a wall of checkboxes.
Definition of done
8
Definition of done
8- The chooser and the table are generated from one column definition.
- Columns the user cannot view never appear in the chooser.
- Required identity and action columns cannot be hidden.
- Saved choices survive column renames and removals without error.
- A reset to defaults is always available.
- Persistence is delegated to Persistent View Preferences.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
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.