taruvi-refine-providers
Overview
Reference module for wiring and using Taruvi's Refine data providers in the frontend — covering client setup, all provider types, hook usage, auth flow, and access control batching.
Compliance rule: This skill and its references are the source of truth for all provider usage. Do not substitute with simpler patterns, copy outdated project code, or skip prescribed steps. If a requirement cannot be met, stop and ask the user.
Provider Map
Use this as the canonical provider inventory for Taruvi + Refine apps:
| Provider | Refine registration key | Primary purpose | Typical hooks |
|---|---|---|---|
dataProvider(client) |
default |
Datatable/database CRUD + filters/sort/pagination/aggregation | useList, useOne, useCreate, useUpdate, useDelete, useUpdateMany, useDeleteMany |
storageDataProvider(client) |
storage |
File/object upload, listing, download, delete | useCreate, useList, useOne, useDelete, useDeleteMany |
appDataProvider(client) |
app |
App-level operations: function execute, analytics execute, roles, settings, secrets | useCustom (functions/analytics), useList (roles/secrets), useOne (settings/secrets) |
userDataProvider(client) |
user |
User CRUD and user-related app data | useList, useOne, useCreate, useUpdate, useDelete |
authProvider(client) |
authProvider prop |
Login/logout/session/identity/permissions | Refine auth lifecycle (check, login, logout, getIdentity) |
accessControlProvider(client) |
accessControlProvider prop |
Batched Cerbos permission checks for useCan/CanAccess |
useCan, CanAccess |
More from taruvi-ai/taruvi-skills
taruvi-app-developer
>
19taruvi-functions
>
18taruvi-database
>
18taruvi-storage
>
18taruvi-backend-provisioning
Provision Taruvi backend resources via the Taruvi MCP server — datatables with Frictionless schemas, storage buckets, users, roles, Cerbos policies, serverless functions, analytics queries, secrets, tags, and audited raw SQL. Use when the user wants to create a datatable, add a role, write a Cerbos policy, provision a bucket, upsert schema, assign a role, register a function, run an analytics query, or otherwise change Taruvi's backend state. TRIGGERS include "Taruvi datatable", "Frictionless schema", "Cerbos policy", "manage_policies", "provision Taruvi", "upsert rows", "multi-tenant table", "Taruvi MCP tools", "create_update_schema", "delete_datatable", "execute_raw_sql". SKIP when writing Python code that runs inside a Taruvi function (use taruvi-functions) or building Refine UI (use taruvi-refine-frontend). Knows all 24 MCP tool contracts, correct invocation order, destructive-op protocol, and the Frictionless/Cerbos essentials the tools expect.
8