Persistent View Preferences
Remember how each user arranged a screen instead of resetting it every visit.
What it adds
Per-user persistence of sort order, visible columns, filters, and layout choices, restored on return.
What your agent is told to do
5
What your agent is told to do
5-
1
List every view-level choice the app currently forgets: sort, column visibility and order, filters, density, grouping, page size.
-
2
Decide for each whether it belongs to the device, the account, or the workspace, and be consistent. A column layout is usually account-wide; a sidebar width is usually device-local.
-
3
Restore preferences before the view renders, so the user never sees the default layout flash into their own.
-
4
Version the stored shape and discard or migrate anything that no longer matches the current columns and filters.
-
5
Do not persist transient state such as an open row, a search query typed once, or a selected checkbox. Restoring those is confusing, not helpful.
Edge cases it handles
6
Edge cases it handles
6- A preference referencing a deleted column or a filter the user has lost access to must be dropped, not applied.
- Signing in must not overwrite newer server preferences with stale local state left over from a signed-out session.
- Two tabs open on the same view must not fight over the stored value.
- Every persisted view needs a visible reset that returns it to defaults.
- In a multi-tenant app, one workspace's layout must not leak into another.
- A user with no stored preferences must get sensible defaults, not an empty layout.
Definition of done
7
Definition of done
7- Sort, filters, columns, and layout survive a reload and a new session.
- Each preference has a documented scope: device, account, or workspace.
- The saved layout is applied before first paint, with no visible reset.
- Preferences referencing removed columns or filters are discarded cleanly.
- Every view offers a reset to defaults.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Feedback Widget
Feedback Widget
Let anyone report a bug or send a comment from the page they are looking at.
What it does
An always-available launcher that opens a short feedback form and submits it with page context attached.
How it works
- 1 Put a single persistent launcher in one corner of the app and open a compact form in place. Do not route the user to a separate feedback page and lose the context they were about to describe.
- 2 Attach the current URL, the app version, the viewport size, the signed-in account, and a short trail of recent client errors automatically, so the reporter does not have to describe where they were.
- 3 Show the captured context to the user before they send it, in a collapsible section, and let them remove it. Silent collection of screen state is a trust problem.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/feedback-widget
Booking Page
Booking Page
A shareable page where someone picks an open time and confirms it in a few clicks.
What it does
A public scheduling page listing open slots, taking a booking, and confirming it to both sides.
How it works
- 1 Build the visitor path first: pick a date, see open times in their own zone, fill a short form, confirm, and receive an email with the details and a cancellation link. That is the minimum coherent version.
- 2 Derive open slots from the owner's availability rules and existing bookings on the server at request time. Do not trust a slot list the browser has been holding since page load.
- 3 Reuse the app's existing Time Zone-Aware Scheduling for conversion and storage, store every time as an absolute instant, and display it converted to the visitor's detected zone with the zone named on screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/booking-page
Date and Time Display Component
Date and Time Display Component
Render every date and time through one component so none of them are ambiguous.
What it does
A single shared way of displaying dates and times, covering absolute format, time zone, and optional relative phrasing.
How it works
- 1 Find every place the app renders a date or a time — tables, activity feeds, audit logs, exports, emails, tooltips — and route them all through one display path rather than formatting at each call site.
- 2 Never render an all-numeric date whose day and month could be swapped. Spell or abbreviate the month, or use an unambiguous ordering consistently, because a reader has no way to tell 04/07 from 07/04.
- 3 State the time zone whenever the value is a specific moment rather than a calendar day, and be explicit about whose zone it is — the viewer's, the record's, or the account's — rather than leaving it implied.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/date-and-time-display-component
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.