app-deployment
Validate and remotely deploy a Universal App through the installed, version-matched Rayfin CLI. Use before deploying to run local checks, confirm the target workspace, preview the operation, deploy, and validate the live app. This skill orchestrates existing executables; it does not implement deployment.
- License 许可
- MIT
- 所属仓库
- microsoft/rayfin
- 最近更新
- 2026-11-12
- Stars
- ★ 662
- Forks
- 77
01 前言 Front Matter
- name
- app-deployment
- description
- Validate and remotely deploy a Universal App through the installed, version-matched Rayfin CLI. Use before deploying to run local checks, confirm the target workspace, preview the operation, deploy, and validate the live app. This skill orchestrates existing executables; it does not implement deployment.
03 SKILL.md 正文
App Deployment
This skill orchestrates the installed Rayfin CLI lifecycle. It does not recreate the validation or deployment implementation.
Before a remote write
- Apply every capability pack the app needs.
- Read
app-validationand complete its static gates: typecheck, build, lint, tests, and pack-provided validators. Run pre-deploy browser or persistence checks only when the installed guide and current environment already support a local or deployed runtime. - Obtain the user's confirmation for the target Fabric workspace and remote deployment. Do not select or create a workspace the user did not approve.
Rayfin CLI deployment
- Read the installed package metadata for
@microsoft/rayfin-guide, then read its version-matched deployment guide. The current guide location isnode_modules/@microsoft/rayfin-guide/assets/docs/app-backend/deploy.md; if package metadata points elsewhere, follow that installed location. - Follow that guide's authentication and deployment workflow. For the current
version, preview the remote operation with
npx rayfin up -n, verify the confirmed target, and then runnpx rayfin up --json. JSON mode is non-interactive. On a first deployment with no recorded target, pass the confirmed target explicitly with--workspace-id <id>,--workspace <name>, or--workspace-uri <uri>. - Read the machine-readable deployment result before continuing.
Overall
status: "success"is not enough for a source-backed request. Inspectgeneratestatus first. For every connector declared inrayfin.yml, require one matchinggenerate[]result. A missing result or a result withstatus: "error"is blocking. Only when a result hasstatus: "skipped"should you inspect itsskipReason. Every connector required by the requested deployed experience must complete the generation/apply path its installed type contract requires. A Category Bnon-graphql-connectorskip is acceptable only when the installed type contract documents that path and the connector's deployed behavior was validated separately. Any other skip for a required connector is blocking.skippedConnectorssummarizes skipped results only; it excludes errors and cannot reveal a missinggenerate[]result. Do not useskippedConnectorsor warning wording to decide whether a connector succeeded. If a required connector is missing, errors, or has a blocking skip, report the blocker and stop. Do not continue to browser validation or claim the source-backed request succeeded. - Do not claim the CLI has validation guarantees that its installed guide does not document.
- Use the direct static-hosting link emitted by the CLI for standalone browser validation. Use the actual Fabric or external host when validating embedded capabilities.
- Determine
services.staticHosting.assetAccessbefore choosing the browser checks. LocalautoLogindoes not prove the deployed public signed-out experience.
Do not publish automatically.
Do not add --force unless the user explicitly requests it and the installed
guide documents the consequence for the exact operation.
Never put access tokens, credentials, or secret values in command arguments, chat, source, or logs. Use interactive authentication and masked secret prompts when the installed guide requires them.
Prove the deployed result
After deployment succeeds, read app-validation and validate the deployed app
at its direct hosting URL, confirming that signed-out users must authenticate before app content renders.
Run the browser checks and, for app-owned records, the persistence create,
reload, update, and delete checks against the deployed result.
For public hosting, also open the standalone hosting URL in a clean browser
session and verify signed-out then signed-in behavior. For protected hosting,
verify session restoration and stale-session replacement. For embedded apps,
validate through the actual Fabric or external host.
Do not report deployment complete from a build, dry run, hosting URL, or CLI
success alone.
Report the Fabric app link only after the deployed runtime checks pass, unless
the user explicitly defers runtime validation.
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.