ux-activity-feed

Designs and critiques activity feeds with gated feed-type decisions and audit handoffs.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-activity-feed-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-activity-feed
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/ux/screens/activity-feed
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-activity-feed-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Activity feeds often ship with overcrowded entries, loud timestamps, ungrouped notifications, and blank first-run screens, and teams frequently pick chronological versus ranked ordering by accident. This Skill structures feed design around deliberate decisions so the output surfaces what matters and lets noise fade. ## Core Features & Use Cases - Feed-type gating: Forces an upfront choice between chronological and ranked/algorithmic feeds, with warnings against retrofitting an algorithm later. - Always-true core rules: Curated entries, legible text, abbreviated relative timestamps, seeded empty states, minimal per-entry controls, and visible refresh status. - Context-dependent trade-offs: Guidance on notification aggregation, follow recommendations, sponsored content labeling, and per-entry control sets. - Use Case: A designer asks an AI assistant to design a social app's home feed; the Skill first establishes ranked versus chronological ordering, then applies entry curation and empty-state seeding, and finally routes the result through heuristics, microcopy, and dark-patterns audits. ## Quick Start Ask your AI assistant to design or review an activity feed, news feed, notifications feed, or timeline for your product.

Frequently Asked Questions about ux-activity-feed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design an activity feed for a social app?▼

Start by deciding whether the feed is chronological or ranked, based on whether recency or relevance matters more. Then curate each entry to essential fields, use abbreviated relative timestamps, seed the empty state for new users, and include only the controls the feed's purpose needs.

Should my feed be chronological or algorithmic?▼

Choose chronological when when something happened is the point, such as transaction logs or team activity histories. Choose ranked when relevance matters more than recency. Decide upfront, because switching from chronological to algorithmic later upsets users.

How do I handle empty states in a new activity feed?▼

Never show a blank feed to new or quiet accounts. Seed it with suggested people to follow, popular or trending content, invite-friends prompts, or profile-completion nudges so users see immediate activity during the critical first days after install.

When should notifications be aggregated in a feed?▼

Aggregate similar notifications when volume is high or users are power users, combining events like "256 people followed you today" by time, type, or interaction. Keep individual events separate in low-volume feeds where each one is meaningful.

What design mistakes make activity feeds hard to use?▼

Common failures include cramming every data field into each entry, using loud exact timestamps, showing every social control on every row, disguising sponsored content as organic, and leaving a frozen screen during refresh without a loading indicator.