rayfin-storage
Use only when the user explicitly requests experimental Rayfin Storage or the project already enables it. Triggers: Rayfin Storage, @microsoft/rayfin-storage, @blob, StorageObject, StorageClient, StorageFolderClient, createStorageClient, rayfin/storage, rayfin dev storage apply, rayfin up storage apply
- License 许可
- MIT
- 所属仓库
- microsoft/rayfin
- 最近更新
- 2026-11-12
- Stars
- ★ 662
- Forks
- 77
01 前言 Front Matter
- name
- rayfin-storage
- metadata
- { "author": "microsoft", "version": "0.1.0" }
- description
- Use only when the user explicitly requests experimental Rayfin Storage or the project already enables it. Triggers: Rayfin Storage, @microsoft/rayfin-storage, @blob, StorageObject, StorageClient, StorageFolderClient, createStorageClient, rayfin/storage, rayfin dev storage apply, rayfin up storage apply
03 SKILL.md 正文
Rayfin Storage
Rayfin Storage is experimental.
Do not select or suggest it for a generic file-upload request unless the user explicitly names Rayfin Storage or the project already enables services.storage.enabled.
Bootstrap
If @microsoft/rayfin-storage is missing, install the version compatible with the project's Rayfin packages before writing Storage code.
Enable Storage in rayfin/rayfin.yml:
services:
storage:
enabled: true
Version-matched documentation
Read node_modules/@microsoft/rayfin-storage/package.json, resolve rayfinDocs.dir, and read its index.md before changing Storage declarations or client code.
If direct file access is unavailable, use rayfin docs get --module rayfin-storage --path index.md or the equivalent Rayfin MCP get_doc call.
Storage folders use Core's shared @role() decorator and policy DSL.
Read node_modules/@microsoft/rayfin-core/assets/docs/permissions.md for that API.
Do not infer operation signatures, decorator options, result shapes, or error codes from this skill.
Guardrails
- Import
blob,StorageObject,ContentTypes, and byte-size helpers from@microsoft/rayfin-core/experimentalwhile Storage remains experimental. - Give every folder at least one authenticated permission decorator; configuration apply rejects folders with no rules, and anonymous Storage permissions are unsupported.
- Treat authorization policies as the security boundary; prefixes organize paths but do not grant access.
- Omit
prefixby default. Add it only when the user explicitly requires path partitioning or the existing application design establishes one; never derive a user-ID prefix merely because authentication is available. If the requirement is unclear, keep the object at the folder root and tell the user that no prefix was added. - Keep an explicit
@blob({ name })value aligned with its Storage schema key. - Send decorated application metadata through
upload({ fields }); intrinsic object fields are server-managed. - Access listed custom fields at the top level because the SDK flattens the service's
fieldsenvelope. - Use the typed Storage client rather than constructing Storage HTTP or SAS requests directly.
Commands
npm install @microsoft/rayfin-storage # Install the SDK separately
npx rayfin dev storage apply # Apply folder configuration locally
npx rayfin up # Deploy and apply enabled services
npx rayfin up storage apply # Re-apply cloud Storage configuration only
Use --force only after reviewing and accepting destructive configuration changes.
04 同仓库更多 Skills
rayfin-getting-started
Use when starting or creating a NEW Rayfin app, or when a Rayfin task comes up and you are not yet inside a Rayfin project. Gets you into a project with the Rayfin CLI, then hands off to the authoritative, version-locked in-project rayfin skill/docs that own all in-project work. Triggers: build a Rayfin app, start a Rayfin project, create a new Rayfin app, create-rayfin, npm create @microsoft/rayfin, rayfin init, scaffold rayfin, rayfin CLI, rayfin template, universal app, awesome-rayfin gallery, get started with Rayfin
visuals
Use when user wants to incorporate charts, graphs, data grid, or other visual representations of data into their project. Use VegaVisual and DataGrid components to create these visuals, utilizing the shared DataTable input, formatting, theme, and interactivity. Covers the onInteraction selection/click events host apps consume, named multi-table data input for layered overlays and reference lines, and Vega-Lite native selections. Triggers: chart, graph, plot, dashboard, KPI, metric, trend, scorecard, data grid, visualize.
schema-discovery
Explore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.
query-design
Separates DAX data-fetching from TypeScript presentation. Guides when to use DAX vs. TypeScript vs. Vega-Lite for aggregation, total rows, FORMAT(), SELECTCOLUMNS, BLANK handling, filtering, multi-grain queries, cross-filtering and cross-highlight subset/overlay queries, and format strings.
functions-capability
Apply and build the Universal App functions capability. Use for trusted server-side logic, secrets, external APIs, custom model endpoints, published Fabric data agents, webhooks, or privileged operations.
fabric-sdk
How to query Fabric data from a running app through the Rayfin connectors client. Use getRayfinClient().connectors.<name>.executeQuery to run DAX against a semantic model, and toQueryResult to normalize the response.