Recurring Schedule Builder
Let users build a repeating schedule and see exactly what it will do.
What it adds
Plain controls for describing recurrence, with a preview of upcoming occurrences and safe editing of a series.
What your agent is told to do
5
What your agent is told to do
5-
1
Build the recurrence from ordinary controls — frequency, interval, days, end condition — and store it as a standard recurrence rule rather than an ad-hoc format.
-
2
Show the next several concrete occurrences, with dates and times, before the user saves. The preview is the feature; a rule nobody can verify is a rule nobody trusts.
-
3
Support end conditions properly: never, on a date, or after N occurrences.
-
4
When editing an existing series, ask whether the change applies to this occurrence, this and all following, or the entire series, and store exceptions rather than rewriting history.
-
5
Do NOT expand the whole series into stored rows up front. Generate occurrences on demand from the rule, or an infinite schedule becomes an infinite table.
Edge cases it handles
6
Edge cases it handles
6- Monthly on the 31st must have a stated behaviour in February — skip, or clamp to the last day.
- Yearly on 29 February needs the same decision.
- Splitting a series at 'this and following' must leave earlier occurrences untouched.
- Deleted single occurrences must persist as exclusions and survive later edits to the rule.
- A rule that produces no occurrences at all must be rejected at save time, with the reason.
- The preview must be computed in the schedule's own zone, including across DST transitions.
Definition of done
9
Definition of done
9- Recurrence is stored as a standard rule, not free text.
- The next occurrences are previewed before saving.
- End conditions cover never, until a date, and after a count.
- Editing offers this occurrence, this and following, or the whole series.
- Nonexistent dates such as the 31st of a short month resolve by a documented rule.
- Occurrences are generated on demand, not materialized indefinitely.
- Exclusions and skipped dates survive subsequent rule edits.
- 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.