taruvi-storage
Overview
Reference module for Taruvi storage workflows — bucket management, object upload/download via REST path-based API or Refine provider hooks, visibility control, batch operations, and quota-aware UX patterns.
Compliance rule: This skill's prescribed patterns (multi-file upload by default, per-file status reporting, storage+metadata consistency) are mandatory. Do not fall back to simpler patterns. If a requirement cannot be met, stop and ask the user.
When to Use This Skill
- Creating or configuring a storage bucket (
app_category,visibility,allowed_mime_types) - Uploading files from the frontend using
storageDataProvider+useCreate - Downloading or serving files via the path-based GET API
- Deleting files individually or in bulk with
useDeleteMany - Building a file manager, attachment list, or media gallery
- Applying prefix/MIME/size/date filters to object listings
- Surfacing bucket quota usage in the UI
Do not use this skill for: database table CRUD (use taruvi-database skill), user data (use taruvi-refine-providers skill), or multi-resource storage + database operations (use taruvi-functions skill).
Step-by-Step Instructions
More from taruvi-ai/taruvi-skills
taruvi-app-developer
>
19taruvi-functions
>
18taruvi-database
>
18taruvi-refine-providers
>
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