Print-Friendly View
Make the pages people actually print come out clean.
What it adds
Print styles for the screens users send to paper or PDF: invoices, reports, orders, summaries.
What your agent is told to do
5
What your agent is told to do
5-
1
Identify the handful of screens people genuinely print. Do not attempt to style the whole app.
-
2
Hide navigation, sidebars, sticky headers, toolbars, and anything that only works when clicked.
-
3
Set page breaks so tables do not split a row, and headings do not land alone at the foot of a page.
-
4
Expand collapsed sections that carry meaning in print, and leave out the ones that are only screen conveniences.
-
5
Do not build a separate print page or a second template. A duplicate view drifts out of sync with the real one.
Edge cases it handles
6
Edge cases it handles
6- Link text is useless on paper. Print the destination URL for links that matter and suppress it for navigation.
- Dark backgrounds and inverted panels waste ink. Print on white regardless of the active theme.
- Long tables need their header row repeated on each page.
- Include the generation date and the record identifier, so a printed copy can be traced back.
- Do not print internal admin controls, draft warnings, or debug information on a customer-facing document.
- Charts and images must fit the page width rather than being clipped at the margin.
Definition of done
7
Definition of done
7- The key screens print with no navigation, controls, or sticky elements.
- Nothing is clipped at the page edge in A4 and Letter.
- Table headers repeat and rows do not split across pages.
- Printed output is legible in both light and dark themes.
- Each printed page carries a date and identifier.
- 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
Countdown Timer
Countdown Timer
A live countdown to a deadline that ends cleanly instead of running negative.
What it does
A countdown component driven by a server-provided deadline, with a defined finished state.
How it works
- 1 Send the deadline and the server's current time together, compute the offset between server and device once, and count against the corrected value. The device clock cannot be trusted to be right.
- 2 Recompute the remaining time from the corrected clock on every tick rather than decrementing a stored number, so a suspended tab does not resume showing a value minutes behind reality.
- 3 Define the finished state explicitly: what the component shows at zero, whether it reveals something, disables a control, or triggers a refetch. Reuse the app's existing Progress Indicator System styling rather than introducing new type and colour for the digits.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/countdown-timer
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.