Displays chronological events and activity through timelines, activity feeds, Gantt charts, and calendar interfaces. Use when showing historical events, project schedules, social feeds, notifications, audit logs, or time-based data. Provides implementation patterns for vertical/horizontal timelines, interactive visualizations, real-time updates, and responsive designs with accessibility (WCAG/ARIA).
npx skills add https://github.com/ancoleman/ai-design-components --skill displaying-timelines
This skill enables systematic creation of timeline and activity components, from simple vertical timelines to complex interactive Gantt charts. It provides clear decision frameworks based on use case and data characteristics, ensuring optimal performance, real-time updates, and accessible implementations.
Activate this skill when:
Select component type based on use case:
Social Activity → Activity Feed (infinite scroll, reactions)
System Events → Audit Log (searchable, exportable, precise timestamps)
User Notifications → Notification Feed (read/unread, grouped by date)
Historical Events → Vertical Timeline (milestones, alternating sides)
Project Planning → Gantt Chart (dependencies, drag-to-reschedule)
Scheduling → Calendar Interface (month/week/day views)
Interactive Roadmap → Horizontal Timeline (zoom, pan, filter)
For detailed selection criteria, reference references/component-selection.md.
Social Feed Pattern:
references/activity-feeds.mdNotification Feed Pattern:
references/notification-feeds.mdAudit Log Pattern:
references/audit-logs.mdExample: examples/social-activity-feed.tsx
Vertical Timeline:
references/vertical-timelines.mdHorizontal Timeline:
references/horizontal-timelines.mdInteractive Timeline:
references/interactive-timelines.mdExample: examples/milestone-timeline.tsx
Project Planning Features:
To generate Gantt chart data:
python scripts/generate_gantt_data.py --tasks 50 --dependencies auto
Reference references/gantt-patterns.md for implementation details.
Example: examples/project-gantt.tsx
Month View:
Week View:
Day/Agenda View:
Reference references/calendar-patterns.md for all views.
Example: examples/calendar-scheduler.tsx
Essential timestamp patterns:
Relative (Recent Events):
Absolute (Older Events):
Implementation Considerations:
To format timestamps consistently:
node scripts/format_timestamps.js --locale en-US --timezone auto
Reference references/timestamp-formatting.md for complete patterns.
Live Activity Feed:
Implementation Pattern:
Reference references/real-time-updates.md for WebSocket patterns.
Example: examples/realtime-activity.tsx
Critical performance thresholds:
<100 events → Client-side rendering, no virtualization
100-1,000 events → Virtual scrolling recommended
1,000+ events → Virtual scrolling + server pagination
Real-time → Debounce updates, batch insertions
Optimization Strategies:
To benchmark performance:
node scripts/benchmark_timeline.js --events 10000
Reference references/performance-optimization.md for details.
Essential WCAG compliance:
Semantic HTML:
<ol> or <ul> for timelinesARIA Patterns:
role="feed" for activity feedsrole="article" for timeline itemsaria-label for timestampsaria-busy during loadingKeyboard Navigation:
Screen Reader Support:
To validate accessibility:
node scripts/validate_timeline_accessibility.js
Reference references/accessibility-patterns.md for complete requirements.
Three proven strategies:
1. Stack Vertically (Mobile)
2. Simplify Display
3. Horizontal Scroll
Reference references/responsive-strategies.md for implementations.
Example: examples/responsive-timeline.tsx
Best for timeline visualizations with rich content:
npm install react-chrono
See examples/react-chrono-timeline.tsx for setup.
Alternative: react-vertical-timeline-component
Best for project management:
npm install @svar/gantt
Enterprise Alternative: Bryntum Gantt
Best for scheduling interfaces:
npm install react-big-calendar
Alternative: FullCalendar
For detailed comparison, reference references/library-comparison.md.
Timelines use the design-tokens skill for consistent theming:
Timeline-Specific Tokens:
--timeline-line-color - Connecting line color--timeline-dot-color - Event marker color--timeline-dot-active-color - Current/active event--event-card-bg - Event card background--timestamp-color - Timestamp textStandard Token Categories:
Supports light, dark, high-contrast, and custom themes.
Reference the design-tokens skill for theme switching.
Start with the example matching the requirements:
social-activity-feed.tsx # Social feed with reactions
notification-center.tsx # Notification system with filters
audit-log-viewer.tsx # System audit log
milestone-timeline.tsx # Vertical timeline with milestones
project-gantt.tsx # Gantt chart with dependencies
calendar-scheduler.tsx # Full calendar with all views
realtime-activity.tsx # Live updates via WebSocket
responsive-timeline.tsx # Mobile-optimized timeline
Generate mock timeline data:
python scripts/generate_timeline_data.py --events 500 --realtime
Test real-time updates:
node scripts/simulate_realtime.js --rate 5/sec --duration 60s
Validate accessibility:
node scripts/validate_timeline_accessibility.js
Benchmark performance:
node scripts/benchmark_timeline.js --events 10000 --virtual
Mobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches principles and constraints, not fixed layouts. Use for React Native, Flutter, or native mobile apps.
Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable. Use whenever someone is planning a study, asks how to assign subjects/samples to groups, mentions randomization, blocking, stratification, controls, factorial or fractional-factorial designs, design of experiments (DOE), screening many factors, response-surface optimization, crossover or repeated-measures or split-plot designs, cluster/group randomization, Latin squares, plate layouts, batch/run-order effects, replication vs. pseudoreplication, or sequential/adaptive/group-sequential designs. Trigger even for informal phrasings like "how should I set up this experiment", "how do I avoid confounding", "what's the best way to test these 6 factors", or "assign these mice to conditions". For computing the sample size or power once the design is chosen, use statistical-power; for analyzing data already collected, use statistical-analysis.
Design systems, plan implementations, review architecture decisions - Use when you need to plan a complex feature, design system architecture, or make high-level technical decisions.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
>- Plans, configures, and manages core GKE cluster networking. Covers private clusters, VPC-native configurations, DNS, node egress, Dataplane V2, and IP planning. Use when designing GKE networking layouts, configuring private clusters, setting up Dataplane V2, planning GKE IP ranges, or managing VPC- native cluster modes. Don't use for application ingress, load balancing, or service networking (use gke-service-networking instead).
Read this before adding or importing a component; follow the workflow instead of guessing. Explains how to add a new component to an azldev distro, covering inspecting the upstream spec, the inline-versus-dedicated-file decision, and validating with render, diff-sources, and build. Triggers include add component, new package, import package, create comp.toml, new component.
How to work in a Plain Notes project (the `plain-notes` starter pack): a flat notes/ folder plus a daily/ journal. The 'I just want to write' layout. Read when the project has these folders, OR when asked to jot a note, capture a quick thought, or write today's journal entry. Carries the linking habit and daily-entry behavior so templates and folder descriptions stay minimal. Complements the platform `open-knowledge` skill; does not replace it.
How to work in a Worldbuilding project (the `worldbuilding` starter pack): a fiction encyclopedia of characters, settings, themes, factions, and lore. Read when the project has these folders, OR when asked to add a character, setting, faction, or piece of lore, or to check the world for internal consistency. Carries the auto-stub and consistency behaviors so that guidance does not live inside template bodies or folder descriptions. Complements the platform `open-knowledge` skill; does not replace it.
Take ancoleman/displaying-timelines from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.