Opening Hours Display
Say whether you are open right now and when you next open.
What it adds
A live open or closed state alongside the weekly hours, with holiday closures folded in.
What your agent is told to do
5
What your agent is told to do
5-
1
Lead with the current state in plain words and follow it with the next transition: open until a time, or closed until a day and time. The weekly table is supporting detail, not the headline.
-
2
Store hours as intervals against the business's own zone, and keep holiday and one-off closures as overrides that win over the regular week rather than as edits to it.
-
3
Compute the state on the server for the first render so the page does not briefly claim the wrong thing, then let the page update itself as the clock crosses a boundary without a reload.
-
4
If the app already has a Recurring Schedule Builder or Quiet Hours, reuse its interval storage and its editing screen for the weekly pattern instead of building a second hours editor that will drift out of agreement.
-
5
Do not compute open or closed from the viewer's device clock and zone. A visitor abroad will be told a shop is closed while its doors are open.
Edge cases it handles
8
Edge cases it handles
8- Open or closed is always evaluated in the business's zone, never the viewer's, and the displayed times should say which zone they are in when the two differ.
- A holiday or one-off closure must override the regular schedule and be surfaced before it happens, so someone reading on Thursday learns that Friday is closed.
- Inside the final part of an open window, say closing soon with the closing time rather than a bare open. A customer told only open will set off for a place about to shut.
- Hours that run past midnight belong to the day they started on. Treating them as two separate days makes a late-night window read as closed at one minute past twelve.
- When the schedule is missing, incomplete, or the current state cannot be determined, fall back to a plain list of hours with no claim about right now. A confident wrong answer is worse than none.
- Daylight-saving transitions must not shift the stored opening times. Store local wall-clock intervals plus the zone, not fixed instants.
- A permanently closed or temporarily suspended location needs its own state rather than being rendered as closed until an opening that will never come.
- The state must be conveyed in text, not by a coloured dot alone, and must be readable by a screen reader.
Definition of done
8
Definition of done
8- The current open or closed state appears above the weekly hours, with the next transition named.
- State is computed in the business's zone and is correct for a viewer in any other zone.
- Holiday and one-off closures override the regular schedule and are surfaced in advance.
- A closing-soon state appears inside the final window of an open period.
- Hours crossing midnight display and evaluate as one continuous window.
- An unknown or incomplete schedule degrades to a plain hours list with no live claim.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Beautiful Empty States
Beautiful Empty States
Replace blank screens with useful, contextual empty states.
What it does
Every list, table, and dashboard in your app has a "nothing here yet" state. Most
apps ship a blank rectangle — and it is often the very first thing a new user sees.
An empty state should say what belongs here, why it is empty, and what to do next.
How it works
- 1 Inventory the empty cases first. List every collection view in the app and
- 2 Distinguish the three kinds of empty. They are not the same, and must not
- 3 Build one reusable empty-state component from the existing design system,
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/beautiful-empty-states
Media Aspect Ratio System
Media Aspect Ratio System
Give every thumbnail, avatar, and hero a shared, reserved shape so nothing jumps.
What it does
A small set of named aspect ratios applied to every image and video surface, with reserved space, a defined fit, and a defined fallback.
How it works
- 1 Catalogue the media surfaces already in the app — list thumbnails, card covers, avatars, hero banners, video embeds, attachment previews — and reduce them to a handful of named ratios rather than a per-component value.
- 2 Reserve the box before the media loads so the ratio holds space from first paint. Layout that settles after an image arrives moves whatever the user was about to click.
- 3 Set the fit per content type, not per component: faces and product shots crop to fill from a sensible focal point, diagrams and screenshots fit whole with padding, because cropping a diagram loses the content it exists to show.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/media-aspect-ratio-system
Expandable Text
Expandable Text
Shorten long text without making the full content hard to reach.
What it does
Long text clamped to a few lines, with an explicit control to show the rest and collapse it again.
How it works
- 1 Clamp by rendered lines, not by character count. Cutting a string at a fixed length breaks words, mangles markup, and truncates differently at every width.
- 2 Only show the expand control when the text is genuinely clipped. A 'Show more' on a two-line paragraph is noise.
- 3 Use a real button with an accessible label naming what expands, and expose the expanded state. An untagged 'more...' is invisible to a screen reader.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/expandable-text
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.