Fullscreen Workspace
Hide surrounding chrome when users need the whole screen for the work.
What it adds
A focus mode that removes navigation and sidebars so an editor, canvas, or dashboard fills the viewport.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify the views where the chrome competes with the work — editors, builders, large tables, dashboards — and add focus mode there only.
-
2
Implement it as an app-level layout change first. Native browser fullscreen is an optional enhancement on top, because it can be blocked or unavailable.
-
3
Always show a visible exit control, and bind Escape to exit. Do not rely on the browser's own fullscreen hint, which fades after a few seconds.
-
4
Keep save status, unsaved-changes indicators, and blocking alerts visible in focus mode. Hiding chrome must not hide whether the user's work is safe.
-
5
Do not unmount and remount the view when toggling modes. Re-creating the editor loses unsaved state, undo history, and scroll position.
Edge cases it handles
6
Edge cases it handles
6- If the browser denies or exits fullscreen, the app must fall back to its own focus layout rather than getting stuck in a half state.
- Exiting must restore the previous layout, scroll position, and selection.
- Modals, toasts, and command palettes must render above the fullscreen surface, not behind it.
- Entering focus mode while a dialog is open should be refused or should carry the dialog with it.
- The mode should be reflected in state that survives a refresh, or the user is thrown out of focus mode by any reload.
- On mobile, browser chrome and the on-screen keyboard change the usable height — measure the real viewport rather than assuming full screen height.
Definition of done
8
Definition of done
8- Focus mode works without native browser fullscreen support.
- An always-visible exit control and Escape both leave the mode.
- Unsaved state, undo history, and scroll position survive entering and exiting.
- Save status and blocking alerts remain visible while in focus mode.
- Overlays render above the fullscreen surface.
- Exiting restores the exact previous layout.
- 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
Opening Hours Display
Opening Hours Display
Say whether you are open right now and when you next open.
What it does
A live open or closed state alongside the weekly hours, with holiday closures folded in.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/opening-hours-display
Dark Mode
Dark Mode
Add a dark theme that respects the system preference and the user's choice.
What it does
A complete dark theme, defaulting to the operating system preference and overridable by the user.
How it works
- 1 Audit every colour in the app first and report where they are defined. If colours are hardcoded throughout, extract them into tokens before anything else — that refactor is the bulk of this work.
- 2 Define a dark palette against those tokens. Do not simply invert the light theme.
- 3 Default to the system preference via prefers-color-scheme, and let the user override it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/dark-mode
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.