data-operations

Standardize Wix CMS collection CRUD and pagination workflows with BaseCrudService.

Updated May 1, 2026
One-click install
npx skills add https://github.com/Rachit246-art/rvglobal1 --skill data-operations-rachit246-art
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-operations
Source: https://github.com/Rachit246-art/rvglobal1/tree/main/.emdash/skills/data-operations
Command: npx skills add https://github.com/Rachit246-art/rvglobal1 --skill data-operations-rachit246-art

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of implementing consistent, error-resistant data access patterns for Wix CMS collections so your list and detail pages stay predictable while you create, read, update, delete, and manage references.

Core Features & Use Cases

  • BaseCrudService CRUD Patterns: Create, paginate-read, read-by-id (with optional singleRef/multiRef), update, and delete using collection-id first and item-id second.
  • Reference Management: Add and remove multi-references to link related entities (e.g., tags, categories, related items).
  • Production Page Patterns: Implement list pages with pagination/infinite scroll requirements, and detail pages with loading, not-found handling, and reference fetching.
  • Optimistic UI Updates: Update UI state immediately for create/update/delete/reference mutations, then sync or reload on failure.

Quick Start

Use the data-operations skill to implement a paginated “items” list by calling BaseCrudService.getAll with limit and skip, rendering result.items, and wiring load-more behavior to result.hasNext and result.nextSkip.

Frequently Asked Questions about data-operations

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

FAQPage Schema
How do I implement paginated list pages with Wix CMS collections?

You can implement paginated Wix CMS list pages by calling BaseCrudService.getAll with limit and skip parameters, then rendering result.items while wiring load-more behavior to result.hasNext and result.nextSkip.

How do I fetch Wix CMS items with singleRef and multiRef relationships?

Fetching Wix CMS items by id supports optional singleRef and multiRef relationships, allowing you to retrieve related entities while maintaining strict parameter ordering with collection-id first and item-id second.

What's the best way to handle UI state for optimistic updates in a Wix CMS CRUD app?

Optimistic UI updates for Wix CMS CRUD operations work by updating the UI state immediately for create, update, delete, and reference mutations, then syncing or reloading the state if the mutation fails.

Can I manage multi-references for related entities like tags in Wix CMS?

Yes, you can add and remove multi-references to link related Wix CMS entities such as tags or categories, ensuring your related items stay connected through standardized reference mutations.

What loading and error states do I need for a Wix CMS detail page?

Production Wix CMS detail pages require specific UI handling for loading states, not-found handling, and reference fetching to ensure data access patterns remain predictable and error-resistant.

Why does my Wix CMS CRUD operation fail when fetching by item id?

Wix CMS CRUD operations require strict parameter ordering with collection-id first and item-id second; failing to maintain this sequence when using BaseCrudService will cause your fetch operations to fail.