[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699WQR9CDD56R4HNQ7JTCA2":3,"skill-same:01M699WQR9CDD56R4HNQ7JTCA2":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M699WQR9CDD56R4HNQ7JTCA2","vscode-webview-trpc-messaging",null,"Implements tRPC-based communication between the Rayfin VS Code extension host and React webviews (packages\u002Ftools\u002Fvscode). Use when creating new webview procedures (queries, mutations, subscriptions), adding a new webview router, wiring up a webview controller, using the tRPC client from React components, applying telemetry middleware (trpcToTelemetry), or supporting AbortSignal-based cancellation in webview operations.","microsoft\u002Frayfin","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699VK9NEV8GH0Y5JKT1G8XG",662,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvscode-webview-trpc-messaging\u002FSKILL.md",[],[19,20,21,22,23,24],"vscode","vscode webview trpc messaging","components","react","react components","telemetry","2026-11-10 10:12:30",false,"---\nname: vscode-webview-trpc-messaging\ndescription: Implements tRPC-based communication between the Rayfin VS Code extension host and React webviews (packages\u002Ftools\u002Fvscode). Use when creating new webview procedures (queries, mutations, subscriptions), adding a new webview router, wiring up a webview controller, using the tRPC client from React components, applying telemetry middleware (trpcToTelemetry), or supporting AbortSignal-based cancellation in webview operations.\n---\n\n# Webview tRPC Messaging\n\nType-safe RPC communication between the VS Code extension host (server) and React webviews (client) using tRPC.\n\n## Architecture Overview\n\n```\nReact Webview (client)                    Extension Host (server)\n─────────────────────                     ──────────────────────\nuseTrpcClient() hook                      WebviewController\n  └─ createTRPCClient                       └─ setupTrpc()\n       └─ vscodeLink ──── postMessage ────►     ├─ callerFactory(appRouter)\n            (send\u002FonReceive)              ◄─────┤   └─ procedure(input)\n                                                └─ abort\u002Fsubscription.stop\n```\n\n**Key files** (read as needed for implementation details):\n\n| File                                                                          | Purpose                                                                                    |\n| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fextension-server\u002Ftrpc.ts`            | tRPC init, `publicProcedure`, `publicProcedureWithTelemetry`                               |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FappRouter.ts`          | Root router bundling all view routers + `commonRouter`                                     |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fextension-server\u002FWebviewController.ts` | WebviewPanel lifecycle, tRPC message dispatcher (queries, mutations, subscriptions, abort) |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fwebview-client\u002FuseTrpcClient.ts`     | React hook providing the tRPC client                                                       |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fwebview-client\u002FvscodeLink.ts`        | Custom tRPC link bridging `postMessage` transport                                          |\n\n## Creating a New Router\n\nEach webview maintains its own router. Follow this pattern:\n\n### 1. Define the router context\n\nExtend `BaseRouterContext` with view-specific fields:\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002FmyView\u002FmyViewRouter.ts\nimport { type BaseRouterContext } from '..\u002Fapi\u002Fconfiguration\u002FappRouter';\n\nexport type RouterContext = BaseRouterContext & {\n  clusterId: string;\n  viewId: string;\n  databaseName: string;\n  \u002F\u002F add view-specific fields\n};\n```\n\n### 2. Define procedures\n\n```typescript\nimport { z } from 'zod';\nimport { publicProcedureWithTelemetry, router, type WithTelemetry } from '..\u002F..\u002Fapi\u002Fextension-server\u002Ftrpc';\n\nexport const myViewRouter = router({\n  \u002F\u002F Query with telemetry (preferred for operations that touch external services)\n  getData: publicProcedureWithTelemetry.input(z.object({ id: z.string() })).query(async ({ input, ctx }) => {\n    const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n    \u002F\u002F myCtx.telemetry is guaranteed present\n    \u002F\u002F myCtx.signal is the AbortSignal for cancellation\n    return { data: 'result' };\n  }),\n\n  \u002F\u002F Mutation without telemetry (rare, use for fire-and-forget)\n  doAction: publicProcedure.input(z.string()).mutation(({ input }) => {\n    \u002F\u002F lightweight operation\n  }),\n});\n```\n\n### 3. Register in appRouter\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FappRouter.ts\nimport { myViewRouter } from '..\u002F..\u002FmyView\u002FmyViewRouter';\n\nexport const appRouter = router({\n  common: commonRouter,\n  myView: myViewRouter, \u002F\u002F \u003C-- add here\n});\n```\n\n### 4. Create the controller\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002FmyView\u002FmyViewController.ts\nimport { WebviewController } from '..\u002Fapi\u002Fextension-server\u002FWebviewController';\nimport { type RouterContext } from '.\u002FmyViewRouter';\n\nexport class MyViewController extends WebviewController\u003CMyViewConfig> {\n  constructor(initialData: MyViewConfig) {\n    super(ext.context, title, 'myViewName', initialData);\n\n    const trpcContext: RouterContext = {\n      webviewName: 'myView',\n      clusterId: initialData.clusterId,\n      viewId: initialData.viewId,\n    };\n\n    this.setupTrpc(trpcContext);\n  }\n}\n```\n\n> **Important:** The `webviewName` in the `WebviewController` constructor is the **registry key** (must match a key in `WebviewRegistry`, e.g. `myViewName`). The `webviewName` in the tRPC context is a **telemetry label** used in telemetry event names (e.g. `myView`). These are intentionally different values — do not confuse them.\n\n### 5. Register in WebviewRegistry\n\nAdd your React component to the registry. The key must match the `webviewName` passed to `WebviewController`'s constructor. The `WebviewName` type (exported from the same file) ensures compile-time validation of webview names.\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FWebviewRegistry.ts\nimport { MyView } from '..\u002F..\u002FmyView\u002FMyView';\n\nexport const WebviewRegistry = {\n  myViewName: MyView, \u002F\u002F \u003C-- add your entry\n} as const;\n\nexport type WebviewName = keyof typeof WebviewRegistry;\n```\n\n## Telemetry: `publicProcedure` vs `publicProcedureWithTelemetry`\n\n| Base                           | When to use                                                                  | `ctx.telemetry`                             |\n| ------------------------------ | ---------------------------------------------------------------------------- | ------------------------------------------- |\n| `publicProcedure`              | Fire-and-forget, no external calls, telemetry reported separately            | `undefined`                                 |\n| `publicProcedureWithTelemetry` | **Default choice.** Any procedure touching DB, network, or user-visible work | Guaranteed via `trpcToTelemetry` middleware |\n\n`trpcToTelemetry` (file-local, not exported) wraps the procedure in `callWithTelemetryAndErrorHandling`, auto-generating a telemetry event named `rayfin.rpc.{type}.{path}` and recording errors, duration, and abort status.\n\nAccess telemetry safely:\n\n```typescript\nconst myCtx = ctx as WithTelemetry\u003CRouterContext>;\nmyCtx.telemetry.properties.myCustomProp = 'value';\nmyCtx.telemetry.measurements.itemCount = items.length;\n```\n\n## AbortSignal Support\n\nEvery tRPC operation (query, mutation, subscription) receives its own `AbortController`. Cancellation flows:\n\n```\nClient (React)                              Server (Extension Host)\n──────────────                              ──────────────────────\n\u002F\u002F Queries\u002FMutations:\nac = new AbortController()\ntrpcClient.myProc.query(input,\n  { signal: ac.signal })\nac.abort()  →  sends 'abort' msg  →  abortController.abort()\n                                        → ctx.signal.aborted = true\n\n\u002F\u002F Subscriptions:\nsub = trpcClient.mySub.subscribe(...)\nsub.unsubscribe()  →  'subscription.stop'  →  abortController.abort()\n```\n\n### Using abort in procedures\n\n```typescript\ngetData: publicProcedureWithTelemetry\n    .input(z.object({ filter: z.record(z.unknown()) }))\n    .query(async ({ input, ctx }) => {\n        const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n\n        \u002F\u002F Option 1: Pass to APIs that accept AbortSignal\n        const response = await fetch(url, { signal: myCtx.signal });\n\n        \u002F\u002F Option 2: Manual check in loops\n        for (const item of items) {\n            if (myCtx.signal?.aborted) return;\n            await processItem(item);\n        }\n    }),\n```\n\n### Client-side abort\n\n```tsx\nconst { trpcClient } = useTrpcClient();\nconst abortControllerRef = useRef\u003CAbortController>();\n\nconst runQuery = async () => {\n  abortControllerRef.current?.abort(); \u002F\u002F cancel previous\n  const ac = new AbortController();\n  abortControllerRef.current = ac;\n\n  const result = await trpcClient.myView.myQuery.query(input, { signal: ac.signal });\n};\n```\n\nWhen `trpcToTelemetry` detects an aborted signal, it sets `telemetry.properties.aborted = 'true'` and `result = 'Canceled'` automatically.\n\n## Subscriptions\n\nSubscriptions stream multiple values from server to client using async generators:\n\n```typescript\n\u002F\u002F Server (router)\nstreamData: publicProcedureWithTelemetry\n    .input(z.object({ batchSize: z.number() }))\n    .subscription(async function* ({ input, ctx }) {\n        const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n\n        for (let i = 0; i \u003C total; i += input.batchSize) {\n            if (myCtx.signal?.aborted) return; \u002F\u002F check before each yield\n            const batch = await fetchBatch(i, input.batchSize);\n            yield batch;\n        }\n    }),\n\n\u002F\u002F Client (React)\nconst sub = trpcClient.myView.streamData.subscribe(\n    { batchSize: 100 },\n    {\n        onData(batch) { \u002F* handle each batch *\u002F },\n        onComplete() { \u002F* all done *\u002F },\n        onError(err) { \u002F* handle error *\u002F },\n    },\n);\n\n\u002F\u002F To stop:\nsub.unsubscribe();\n```\n\n## Client-Side Hook Usage\n\n```tsx\nimport { useTrpcClient } from '..\u002Fapi\u002Fwebview-client\u002FuseTrpcClient';\nimport { useConfiguration } from '..\u002Fapi\u002Fwebview-client\u002FuseConfiguration';\n\nexport const MyComponent = () => {\n  const { trpcClient } = useTrpcClient();\n  const config = useConfiguration\u003CMyViewConfig>();\n\n  useEffect(() => {\n    trpcClient.myView.getData.query({ id: config.documentId }).then(setData);\n  }, []);\n};\n```\n\n`useConfiguration\u003CT>()` retrieves the initial config passed to `WebviewController` constructor (serialized via `encodeURIComponent(JSON.stringify(...))`).\n\n## Common Pitfalls\n\n- **Never use `any`** in procedure context casts — use `WithTelemetry\u003CRouterContext>` or `RouterContext`\n- **Always prefer `publicProcedureWithTelemetry`** unless you have a specific reason not to\n- **Always check `myCtx.signal?.aborted`** in long-running loops — not checking causes wasted work after client cancels\n- **Do not mutate the shared `context` object** — `WebviewController` clones it per-operation already, but router code should treat `ctx` as read-only\n- **Input validation uses `zod`** — always define `.input(z.object({...}))` for type safety\n- **The `commonRouter`** handles cross-cutting concerns (error reporting, telemetry events, surveys, URL opening) — do not duplicate these in view-specific routers\n","# Webview tRPC Messaging\n\nType-safe RPC communication between the VS Code extension host (server) and React webviews (client) using tRPC.\n\n## Architecture Overview\n\n```\nReact Webview (client)                    Extension Host (server)\n─────────────────────                     ──────────────────────\nuseTrpcClient() hook                      WebviewController\n  └─ createTRPCClient                       └─ setupTrpc()\n       └─ vscodeLink ──── postMessage ────►     ├─ callerFactory(appRouter)\n            (send\u002FonReceive)              ◄─────┤   └─ procedure(input)\n                                                └─ abort\u002Fsubscription.stop\n```\n\n**Key files** (read as needed for implementation details):\n\n| File                                                                          | Purpose                                                                                    |\n| ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fextension-server\u002Ftrpc.ts`            | tRPC init, `publicProcedure`, `publicProcedureWithTelemetry`                               |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FappRouter.ts`          | Root router bundling all view routers + `commonRouter`                                     |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fextension-server\u002FWebviewController.ts` | WebviewPanel lifecycle, tRPC message dispatcher (queries, mutations, subscriptions, abort) |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fwebview-client\u002FuseTrpcClient.ts`     | React hook providing the tRPC client                                                       |\n| `packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fwebview-client\u002FvscodeLink.ts`        | Custom tRPC link bridging `postMessage` transport                                          |\n\n## Creating a New Router\n\nEach webview maintains its own router. Follow this pattern:\n\n### 1. Define the router context\n\nExtend `BaseRouterContext` with view-specific fields:\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002FmyView\u002FmyViewRouter.ts\nimport { type BaseRouterContext } from '..\u002Fapi\u002Fconfiguration\u002FappRouter';\n\nexport type RouterContext = BaseRouterContext & {\n  clusterId: string;\n  viewId: string;\n  databaseName: string;\n  \u002F\u002F add view-specific fields\n};\n```\n\n### 2. Define procedures\n\n```typescript\nimport { z } from 'zod';\nimport { publicProcedureWithTelemetry, router, type WithTelemetry } from '..\u002F..\u002Fapi\u002Fextension-server\u002Ftrpc';\n\nexport const myViewRouter = router({\n  \u002F\u002F Query with telemetry (preferred for operations that touch external services)\n  getData: publicProcedureWithTelemetry.input(z.object({ id: z.string() })).query(async ({ input, ctx }) => {\n    const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n    \u002F\u002F myCtx.telemetry is guaranteed present\n    \u002F\u002F myCtx.signal is the AbortSignal for cancellation\n    return { data: 'result' };\n  }),\n\n  \u002F\u002F Mutation without telemetry (rare, use for fire-and-forget)\n  doAction: publicProcedure.input(z.string()).mutation(({ input }) => {\n    \u002F\u002F lightweight operation\n  }),\n});\n```\n\n### 3. Register in appRouter\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FappRouter.ts\nimport { myViewRouter } from '..\u002F..\u002FmyView\u002FmyViewRouter';\n\nexport const appRouter = router({\n  common: commonRouter,\n  myView: myViewRouter, \u002F\u002F \u003C-- add here\n});\n```\n\n### 4. Create the controller\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002FmyView\u002FmyViewController.ts\nimport { WebviewController } from '..\u002Fapi\u002Fextension-server\u002FWebviewController';\nimport { type RouterContext } from '.\u002FmyViewRouter';\n\nexport class MyViewController extends WebviewController\u003CMyViewConfig> {\n  constructor(initialData: MyViewConfig) {\n    super(ext.context, title, 'myViewName', initialData);\n\n    const trpcContext: RouterContext = {\n      webviewName: 'myView',\n      clusterId: initialData.clusterId,\n      viewId: initialData.viewId,\n    };\n\n    this.setupTrpc(trpcContext);\n  }\n}\n```\n\n> **Important:** The `webviewName` in the `WebviewController` constructor is the **registry key** (must match a key in `WebviewRegistry`, e.g. `myViewName`). The `webviewName` in the tRPC context is a **telemetry label** used in telemetry event names (e.g. `myView`). These are intentionally different values — do not confuse them.\n\n### 5. Register in WebviewRegistry\n\nAdd your React component to the registry. The key must match the `webviewName` passed to `WebviewController`'s constructor. The `WebviewName` type (exported from the same file) ensures compile-time validation of webview names.\n\n```typescript\n\u002F\u002F packages\u002Ftools\u002Fvscode\u002Fsrc\u002Fwebviews\u002Fapi\u002Fconfiguration\u002FWebviewRegistry.ts\nimport { MyView } from '..\u002F..\u002FmyView\u002FMyView';\n\nexport const WebviewRegistry = {\n  myViewName: MyView, \u002F\u002F \u003C-- add your entry\n} as const;\n\nexport type WebviewName = keyof typeof WebviewRegistry;\n```\n\n## Telemetry: `publicProcedure` vs `publicProcedureWithTelemetry`\n\n| Base                           | When to use                                                                  | `ctx.telemetry`                             |\n| ------------------------------ | ---------------------------------------------------------------------------- | ------------------------------------------- |\n| `publicProcedure`              | Fire-and-forget, no external calls, telemetry reported separately            | `undefined`                                 |\n| `publicProcedureWithTelemetry` | **Default choice.** Any procedure touching DB, network, or user-visible work | Guaranteed via `trpcToTelemetry` middleware |\n\n`trpcToTelemetry` (file-local, not exported) wraps the procedure in `callWithTelemetryAndErrorHandling`, auto-generating a telemetry event named `rayfin.rpc.{type}.{path}` and recording errors, duration, and abort status.\n\nAccess telemetry safely:\n\n```typescript\nconst myCtx = ctx as WithTelemetry\u003CRouterContext>;\nmyCtx.telemetry.properties.myCustomProp = 'value';\nmyCtx.telemetry.measurements.itemCount = items.length;\n```\n\n## AbortSignal Support\n\nEvery tRPC operation (query, mutation, subscription) receives its own `AbortController`. Cancellation flows:\n\n```\nClient (React)                              Server (Extension Host)\n──────────────                              ──────────────────────\n\u002F\u002F Queries\u002FMutations:\nac = new AbortController()\ntrpcClient.myProc.query(input,\n  { signal: ac.signal })\nac.abort()  →  sends 'abort' msg  →  abortController.abort()\n                                        → ctx.signal.aborted = true\n\n\u002F\u002F Subscriptions:\nsub = trpcClient.mySub.subscribe(...)\nsub.unsubscribe()  →  'subscription.stop'  →  abortController.abort()\n```\n\n### Using abort in procedures\n\n```typescript\ngetData: publicProcedureWithTelemetry\n    .input(z.object({ filter: z.record(z.unknown()) }))\n    .query(async ({ input, ctx }) => {\n        const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n\n        \u002F\u002F Option 1: Pass to APIs that accept AbortSignal\n        const response = await fetch(url, { signal: myCtx.signal });\n\n        \u002F\u002F Option 2: Manual check in loops\n        for (const item of items) {\n            if (myCtx.signal?.aborted) return;\n            await processItem(item);\n        }\n    }),\n```\n\n### Client-side abort\n\n```tsx\nconst { trpcClient } = useTrpcClient();\nconst abortControllerRef = useRef\u003CAbortController>();\n\nconst runQuery = async () => {\n  abortControllerRef.current?.abort(); \u002F\u002F cancel previous\n  const ac = new AbortController();\n  abortControllerRef.current = ac;\n\n  const result = await trpcClient.myView.myQuery.query(input, { signal: ac.signal });\n};\n```\n\nWhen `trpcToTelemetry` detects an aborted signal, it sets `telemetry.properties.aborted = 'true'` and `result = 'Canceled'` automatically.\n\n## Subscriptions\n\nSubscriptions stream multiple values from server to client using async generators:\n\n```typescript\n\u002F\u002F Server (router)\nstreamData: publicProcedureWithTelemetry\n    .input(z.object({ batchSize: z.number() }))\n    .subscription(async function* ({ input, ctx }) {\n        const myCtx = ctx as WithTelemetry\u003CRouterContext>;\n\n        for (let i = 0; i \u003C total; i += input.batchSize) {\n            if (myCtx.signal?.aborted) return; \u002F\u002F check before each yield\n            const batch = await fetchBatch(i, input.batchSize);\n            yield batch;\n        }\n    }),\n\n\u002F\u002F Client (React)\nconst sub = trpcClient.myView.streamData.subscribe(\n    { batchSize: 100 },\n    {\n        onData(batch) { \u002F* handle each batch *\u002F },\n        onComplete() { \u002F* all done *\u002F },\n        onError(err) { \u002F* handle error *\u002F },\n    },\n);\n\n\u002F\u002F To stop:\nsub.unsubscribe();\n```\n\n## Client-Side Hook Usage\n\n```tsx\nimport { useTrpcClient } from '..\u002Fapi\u002Fwebview-client\u002FuseTrpcClient';\nimport { useConfiguration } from '..\u002Fapi\u002Fwebview-client\u002FuseConfiguration';\n\nexport const MyComponent = () => {\n  const { trpcClient } = useTrpcClient();\n  const config = useConfiguration\u003CMyViewConfig>();\n\n  useEffect(() => {\n    trpcClient.myView.getData.query({ id: config.documentId }).then(setData);\n  }, []);\n};\n```\n\n`useConfiguration\u003CT>()` retrieves the initial config passed to `WebviewController` constructor (serialized via `encodeURIComponent(JSON.stringify(...))`).\n\n## Common Pitfalls\n\n- **Never use `any`** in procedure context casts — use `WithTelemetry\u003CRouterContext>` or `RouterContext`\n- **Always prefer `publicProcedureWithTelemetry`** unless you have a specific reason not to\n- **Always check `myCtx.signal?.aborted`** in long-running loops — not checking causes wasted work after client cancels\n- **Do not mutate the shared `context` object** — `WebviewController` clones it per-operation already, but router code should treat `ctx` as read-only\n- **Input validation uses `zod`** — always define `.input(z.object({...}))` for type safety\n- **The `commonRouter`** handles cross-cutting concerns (error reporting, telemetry events, surveys, URL opening) — do not duplicate these in view-specific routers\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324",".github\u002Fskills\u002Fvscode-webview-trpc-messaging",77,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 01:21:10",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add microsoft\u002Frayfin --skill vscode-webview-trpc-messaging",{"tool":45,"command":46},"bunx","bunx skills add microsoft\u002Frayfin --skill vscode-webview-trpc-messaging",{"tool":48,"command":49},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill vscode-webview-trpc-messaging","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fvscode-webview-trpc-messaging\u002FSKILL.md",true,[53,59,63,67],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"resources\u002Fintegration-testing.md","REFERENCE","参考文档",12988,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fbackend-development\u002Fskills\u002Ftemporal-python-testing\u002Fresources\u002Fintegration-testing.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"resources\u002Flocal-setup.md",12066,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fbackend-development\u002Fskills\u002Ftemporal-python-testing\u002Fresources\u002Flocal-setup.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"resources\u002Freplay-testing.md",12374,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fbackend-development\u002Fskills\u002Ftemporal-python-testing\u002Fresources\u002Freplay-testing.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"resources\u002Funit-testing.md",8702,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fbackend-development\u002Fskills\u002Ftemporal-python-testing\u002Fresources\u002Funit-testing.md",[72,85,104,113,132,140],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":25},"01M699YEY2QDVPKTZS3HR9AX84","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\u002Fdocs 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\u002Frayfin, rayfin init, scaffold rayfin, rayfin CLI, rayfin template, universal app, awesome-rayfin gallery, get started with Rayfin","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fskills\u002Frayfin-getting-started\u002FSKILL.md",[],[79,80,81,82,9,83,84],"rayfin getting started","rayfin","scaffold","init","docs","cli",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":101,"publishedAt":25},"01M699YCN4ZDW2AMDP4NVJ2QGC","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\u002Fclick 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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fvisuals\u002FSKILL.md",[91,96],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[87,21,102,103],"dashboard","visualize",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":25},"01M699YBEP146MJZJNN8YEBZ2G","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fschema-discovery\u002FSKILL.md",[],[111,112],"schema discovery","dax",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":128,"publishedAt":25},"01M699Y9E80WYFKD1S4MT4B1CS","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\u002Foverlay queries, and format strings.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Fquery-design\u002FSKILL.md",[119,122,125],{"categoryNo":120,"categoryName":121,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":123,"categoryName":124,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":126,"categoryName":127,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000032","设计师",[129,130,112,131],"query design","design","typescript",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":25},"01M699Y7CKZ55QSYFE827RRVJE","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.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffunctions-capability\u002FSKILL.md",[],[139],"functions capability",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":25},"01M699Y5R87YE620T78Z30KQSA","fabric-sdk","How to query Fabric data from a running app through the Rayfin connectors client. Use getRayfinClient().connectors.\u003Cname>.executeQuery to run DAX against a semantic model, and toQueryResult to normalize the response.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002Fsamples\u002Funiversal-app\u002Ftemplate\u002F.agents\u002Fskills\u002Ffabric-sdk\u002FSKILL.md",[],[147,148,112,149,80,150],"sdk","fabric sdk","rayfin connectors","connectors"]