fabric-appslisted

Build data-driven applications on Microsoft Fabric Apps (the preview workload that turns TypeScript data models into a SQL database, GraphQL APIs, auth, and static hosting via the Rayfin CLI). Use this skill whenever the user is working with Fabric Apps, the Rayfin CLI (`rayfin`, `npx rayfin up`, `npm create @microsoft/rayfin`), the `@microsoft/rayfin-core` or `@microsoft/rayfin-client` packages, `RayfinClient`, `rayfin.yml`, the `rayfin/data/` folder, or `@entity()`/`@role()` decorators — even if they only say "build an app on Fabric", "scaffold a Fabric app", "add a table/entity to my Fabric app", "query my Fabric data with GraphQL", "deploy to Fabric with rayfin", or describe an internal tool/dashboard/prototype backed by Fabric capacity. Do NOT use this for Azure Service Fabric, Fabric data engineering (notebooks, lakehouses, pipelines, Spark), or Power BI — those are unrelated to Fabric Apps.
NikolajUnserRichter/fabric-apps-skill · ★ 0 · API & Backend · score 72

Install: claude install-skill NikolajUnserRichter/fabric-apps-skill

# Microsoft Fabric Apps (Rayfin) ## What this is Fabric Apps (preview) is a Microsoft Fabric workload for building full-stack, data-driven web apps. You write **TypeScript entity classes decorated with `@entity()`, `@text()`, `@role()`, etc.**, and the **Rayfin CLI** compiles them into a managed **SQL database in Fabric**, a **GraphQL Data API**, **row-level authorization**, and **static hosting** — all behind a single app endpoint with **Microsoft Entra SSO**. The whole platform is the "Rayfin" toolchain. Three pieces show up constantly: - `@microsoft/rayfin-core` — decorators you use to define data models (`@entity`, `@text`, `@role`, …). - `@microsoft/rayfin-client` — the type-safe `RayfinClient` your frontend uses to read/write data. - `@microsoft/rayfin-cli` (`rayfin` / `npx rayfin`) — scaffold, run locally, apply schema, deploy. Mental model of the data flow — keep this in mind, because every "how do I…" question maps to one stage: ``` TypeScript entity classes (rayfin/data/*.ts) → decorators (@entity, @text, @one, @role …) → CLI compiles to → SQL schema + GraphQL API + auth policies → RayfinClient (generated, type-safe) → your frontend (React/Vue/Svelte/…) ``` ## When to reach for it (and when not) Good fit: rapid prototypes, internal tools/dashboards, data-exploration UIs, and structured backends for AI/agent apps — anything where you want a live, authenticated, data-backed app without writing backend boilerplate. Bad fit (tell the user up front,