webf-infinite-scrolling

Build infinite-scrolling lists with WebFListView virtualization in React and Vue.

Updated Nov 17, 2024
One-click install
npx skills add https://github.com/maurodf0/anime-tracker --skill webf-infinite-scrolling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webf-infinite-scrolling
Source: https://github.com/maurodf0/anime-tracker/tree/main/.claude/skills/webf-infinite-scrolling
Command: npx skills add https://github.com/maurodf0/anime-tracker --skill webf-infinite-scrolling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables building long, smooth-scrolling lists in web and hybrid UIs by leveraging WebFListView to virtualization-render thousands of items with native-like pull-to-refresh and load-more capabilities. It solves performance bottlenecks from rendering large DOM trees and provides deterministic item rendering for scroll-heavy interfaces.

Core Features & Use Cases

  • Virtualized rendering: WebFListView recycles item views to maintain 60fps scrolling on large datasets.
  • Pull-to-refresh + infinite scrolling: Out-of-the-box support for refreshing content and loading additional items as the user scrolls.
  • Direct-children requirement: Each list item must be a direct child of WebFListView for proper virtualization.
  • Cross-framework examples: Usage patterns for React and Vue are provided to fit modern web apps (e.g., feeds, catalogs, chat).

Quick Start

Use the webf-infinite-scrolling skill to create a feed with pull-to-refresh and load-more, ensuring each item is a direct child of WebFListView.

Frequently Asked Questions about webf-infinite-scrolling

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

FAQPage Schema
How do I build an infinite scrolling list with React or Vue without dropping frames?

Build infinite scrolling lists in React or Vue using WebFListView to virtualize-render thousands of items, recycling views to maintain 60fps scrolling on large datasets.

What is the correct way to structure components for list virtualization?

For list virtualization, each list item must be a direct child of WebFListView to ensure proper view recycling and deterministic item rendering during scroll.

Can I add pull-to-refresh and load-more functionality to a feed UI?

Yes, you can implement pull-to-refresh and load-more in feed UIs using WebFListView's out-of-the-box callbacks, finishLoad and finishRefresh, to manage content updates.

Why does my infinite scrolling list fail to virtualize items correctly?

Infinite scrolling virtualization fails if list items are not direct children of WebFListView, as the component requires this specific hierarchy to recycle item views properly.

Are there timeout handling scenarios I should know about when loading more items?

When loading more items, WebFListView documents specific timeout handling and no-wrap scenarios to ensure scrolling performance remains stable during content fetching delays.