Template Picker
Let people start from a proven structure instead of a blank screen.
What it adds
A gallery of curated, versioned starting points that can be previewed and then applied to create a new record.
What your agent is told to do
6
What your agent is told to do
6-
1
Treat templates as curated and versioned content, separate from user records. Record which template and which version produced each object so support can trace it later.
-
2
Show only templates compatible with the object type being created and with the user's plan. Locked templates may be visible as an upgrade prompt, but must not be applicable.
-
3
Show a real preview of what applying it will create — the sections, fields, and items — before anything is written.
-
4
Applying a template to an object that already has content must never overwrite silently. Offer merge or a new object, or refuse.
-
5
Publishing a new template version must not retroactively change objects created from an earlier one.
-
6
Copying an existing user record is owned by Duplicate Record, and seeding demo content is owned by Sample Data. Do not implement either here — link to them instead.
Edge cases it handles
6
Edge cases it handles
6- A template referencing a field or integration the workspace does not have must degrade gracefully or be marked unavailable, not applied broken.
- A user's plan can be downgraded after a template was applied; the created object must keep working.
- A retired template must remain readable for objects already using it.
- Applying a large template must be atomic and show progress if it is slow.
- Templates with localised content need a language rule; do not silently apply English into a non-English workspace.
- An empty gallery — no compatible templates — needs its own state with a path to starting blank.
Definition of done
8
Definition of done
8- Only templates compatible with the object type and plan can be applied.
- A preview shows the created structure before anything is written.
- Every created object records the template id and version used.
- New template versions do not alter existing objects.
- Applying to an object with existing content never overwrites without consent.
- Unavailable or retired templates are handled explicitly rather than failing.
- 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.