Social Feed Embed
Show your latest social posts on your own pages without breaking when the network is down.
What it adds
A server-side fetch of an external social account's recent posts, cached and rendered in the app's own markup.
What your agent is told to do
5
What your agent is told to do
5-
1
Fetch the posts on the server on a schedule and store them, then render from your own store. Do not have every visitor's browser call the social platform directly.
-
2
Render the posts in the app's own card markup with your own typography and spacing. A dropped-in third-party script fights your styling, tracks your visitors, and disappears when the platform changes its widget.
-
3
Reuse the app's existing image pipeline for post media so thumbnails are resized and served from your own storage rather than hotlinked from the platform.
-
4
Give operators a settings screen showing the connected account, the last successful fetch, and the current authorisation state, with a clear reconnect action.
-
5
Do not fail the page when the feed cannot be refreshed. Serve the last good cached copy, and if there is no cached copy, hide the section entirely rather than rendering an empty box.
Edge cases it handles
8
Edge cases it handles
8- An upstream outage must not blank the section. Keep serving the last successful fetch and mark it stale internally, so the page looks the same to a visitor who does not care why.
- The platform will rate-limit you. Back off exponentially on rejection, respect any retry hint returned, and never retry a failed fetch on every page request.
- If any third-party markup is embedded at all, sandbox it so it cannot run scripts against your page, read cookies, or navigate the top-level window.
- Posts load after the page does and will push content down. Reserve the section's height from the cached post count and known media dimensions so nothing jumps.
- Account authorisation expires or gets revoked. Surface that to the operator with a visible reconnect prompt instead of quietly serving a feed that stops updating and slowly goes stale.
- Post text and media come from a platform where a caption can be edited or deleted after you cached it. Refresh on a schedule and drop posts that no longer exist upstream.
- Media needs alt text. Use the platform's own description where one exists and fall back to something meaningful rather than an empty attribute.
- If the app has Consent and Cookie Preferences, an embed that would set third-party cookies must not load until consent is given, and must show a placeholder with an explicit load action instead.
Definition of done
9
Definition of done
9- Posts render from the app's own cached copy, not from a live browser request to the platform.
- An upstream outage or rate limit leaves the last good posts visible with no error on the page.
- Retries use exponential backoff and honour any retry hint the platform returns.
- The section's height is reserved so late-arriving posts do not shift the layout.
- Revoked or expired authorisation is visible to the operator with a reconnect action.
- Any embedded third-party markup is sandboxed and cannot script the host page.
- Every post image carries meaningful alt text.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Social Sharing
Social Sharing
Make your links look good when someone posts them.
What it does
Open Graph tags, share buttons, and preview images so shared links don't render as bare URLs.
How it works
- 1 Add Open Graph and Twitter Card tags to every publicly shareable page, with a title, description, and image.
- 2 Generate a preview image per record where it makes sense, rather than one generic image for the whole site.
- 3 Add share actions that use the native share sheet on mobile and copy-link on desktop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/social-sharing
Share Image Generator
Share Image Generator
Give every shared link a proper preview image instead of a blank card.
What it does
Server-side generation of a per-page preview image, referenced by the page's existing share metadata.
How it works
- 1 Find where the app already sets its share metadata, most likely alongside Social Sharing or Shareable Deep Links, and point the image tag at the generated URL rather than adding a parallel metadata block.
- 2 Generate the image on the server from the record's own title, author, and a brand mark. Do not render it in the visitor's browser; the services that fetch previews do not run scripts.
- 3 Design one template that degrades well, then add variants only where the content type genuinely differs. Three good templates beat a configurable layout engine nobody tunes.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/share-image-generator
Ratings and Reviews
Ratings and Reviews
Show real customer opinion on an item instead of asking buyers to take your word.
What it does
A star rating and written review per item, with a stored aggregate shown alongside the item and a moderation step before publication.
How it works
- 1 Show the aggregate where the item appears: an average, a count, and a breakdown by star level. Read that from a stored aggregate on the item, updated as reviews change, not from an aggregate query over the review table on every page render.
- 2 Decide who is allowed to review and enforce it server-side. Restricting reviews to verified purchasers is the single change that most improves trust and most reduces spam.
- 3 Route new reviews through the app's existing Moderation Queue and reuse AI Text Content Moderation if it is present, rather than adding a second approval inbox. Do not build a parallel review-approval screen.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ratings-and-reviews
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.