Time Zone-Aware Scheduling
Schedule things for the right local time when everyone is in a different zone.
What it adds
Scheduling that stores an unambiguous instant alongside the intended zone, and survives daylight-saving transitions.
What your agent is told to do
5
What your agent is told to do
5-
1
Store both the resolved instant and the IANA zone identifier the user chose. The instant alone loses the intent; the local time alone is ambiguous.
-
2
Show the user the zone their schedule is in, and show viewers in other zones the same moment converted to theirs with the zone named.
-
3
Decide per schedule type whether it is a fixed instant or a recurring local wall-clock time, and store that intent explicitly — the two diverge every time the clocks change.
-
4
Resolve daylight-saving edge cases with a stated rule: a nonexistent local time and a repeated local time both need a defined answer, not whatever the library defaults to.
-
5
Do NOT store a UTC offset in place of a zone name. Offsets go stale the moment the rules change, and governments change them.
Edge cases it handles
6
Edge cases it handles
6- A local time that does not exist during a spring-forward gap must be shifted by a documented rule and shown to the user.
- A repeated local time in an autumn-back overlap must pick one occurrence deliberately.
- Existing schedules must not shift when a country changes its time-zone rules — historical instants stay fixed.
- A recurring 9am local schedule must remain 9am local across a DST change, which means its UTC time moves.
- The browser-detected zone is a default, not a decision — let the user change it.
- Sends near a transition must not fire twice or be skipped.
Definition of done
8
Definition of done
8- Every schedule stores an instant plus an IANA zone identifier.
- Fixed-instant and recurring-local schedules are distinguishable in the data.
- Times are displayed in the viewer's zone with the zone named.
- Nonexistent and ambiguous local times resolve by a documented rule.
- A DST transition does not duplicate or skip a scheduled run.
- Time-zone rule updates do not move existing scheduled instants.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Voice Dictation
Voice Dictation
Put a microphone in text fields so people can speak their input instead of typing it.
What it does
A dictation control on the app's longer text inputs that transcribes speech into the field as the user talks.
How it works
- 1 Add the control to the fields where typing is genuinely tedious: long descriptions, notes, comments, and message bodies. A microphone on a postcode field is clutter.
- 2 Show interim results in the field as they arrive, visually distinct from committed text, so the speaker can see it is working and correct course before they finish.
- 3 Reuse the app's existing Voice Transcription for the server-side path so one recognition configuration and one set of language settings serve both dictation and recorded audio.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-dictation
Help Text Pattern
Help Text Pattern
Put field guidance in one predictable place, phrased the same way every time.
What it does
A consistent treatment for the short explanatory text that sits with a field and its control.
How it works
- 1 Collect the guidance the app currently scatters across placeholders, tooltips, asterisked footnotes, and modal help, and move it into one slot beneath the field.
- 2 Keep guidance that is required to complete the field permanently visible. A format rule hidden behind a hover target is not available to a touch user or a keyboard user.
- 3 Write help as the rule the user needs before typing — the accepted format, the consequence of the choice — not as a restatement of the label.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/help-text-pattern
Form Section Pattern
Form Section Pattern
Break long forms into labelled sections people can scan instead of read.
What it does
A section pattern grouping related fields under a heading, a description, and its own actions.
How it works
- 1 Find the forms that have grown past a screenful — settings, profiles, checkout, configuration — and group their fields by the question each group answers, not by the table the columns come from.
- 2 Give each section a heading in the document's heading order and an optional one-line description, so screen reader and keyboard users can jump between sections.
- 3 Allow at most one level of nesting. A section inside a section inside a tab gives the user no orientation and pushes the fields into a narrow gutter.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/form-section-pattern
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.