[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699W9NF3M9NQH7D74F5H8ZN":3,"skill-same:01M699W9NF3M9NQH7D74F5H8ZN":60},{"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":23,"publishedAt":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M699W9NF3M9NQH7D74F5H8ZN","rayfin-cli-ux",null,"Mandatory for Rayfin CLI UX work. Load before designing, speccing, implementing, or reviewing CLI commands, flags, output, or errors.","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\u002Frayfin-cli-ux\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[24,25],"cli","rayfin cli ux","2026-11-10 10:12:30",false,"---\nname: rayfin-cli-ux\ndescription: >-\n  Mandatory for Rayfin CLI UX work. Load before designing, speccing,\n  implementing, or reviewing CLI commands, flags, output, or errors.\n---\n\n# Rayfin CLI UX Guidelines\n\nStandards for consistent, high-quality CLI experiences in `@microsoft\u002Frayfin-cli`.\n\n**Full reference**: [references\u002Fcli-ux-guidelines.md](.\u002Freferences\u002Fcli-ux-guidelines.md) — load on demand for depth, examples, and rationale.\n\n## Architecture Status\n\nThese rules define *what* a good CLI experience must deliver — they stay in force regardless of wiring.\n*How* output is wired is mid-migration to the workflow + adapter architecture ([`docs\u002Frfc\u002Frayfin-tools-architecture.md`](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture.md), tracked in [`rayfin-tools-architecture-migration.md`](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture-migration.md)).\n\n- **New or migrated commands** use a `common\u002Fsrc\u002Fworkflows\u002F\u003Cname>\u002F` workflow returning a typed `Result\u003CT>`, with a thin Layer-1 Commander wrapper rendering via `Logger`\u002F`Progress` adapters selected from `--output \u003Cmode>`. Do **not** import `output-mode.ts`, branch on raw `--json`\u002F`--verbose`, or use `CliHandledError`\u002F`process.exit`.\n- **Legacy (un-migrated) commands** use `output-mode.ts` (`modeLog`\u002F`emitJson`\u002F`resolveOutputMode`). This machinery is scheduled for removal in Phase 6.\n- When this skill and the architecture RFC disagree, the RFC wins.\n\n## Constitutional Rules\n\nNon-negotiable for every CLI command. Each rule has a stable ID (R1–R12) for cross-referencing.\n\n| ID | Rule | One-liner |\n|----|------|-----------|\n| R1 | Three output modes | Every command supports `interactive`, `plain`, and `json`. See [reference §1](.\u002Freferences\u002Fcli-ux-guidelines.md). |\n| R2 | No `console.log` | All output goes through mode-aware utilities (or v2 `Logger`\u002F`Progress` adapters). |\n| R3 | Recovery hints | Every `❌` error includes an indented next-step action. |\n| R4 | `--force` for destructive ops | Operations risking data loss fail by default; `--force` opts in. |\n| R5 | Respect non-interactive | No prompts when `--yes`, non-TTY stdin, or `CI=true`. |\n| R6 | Valid JSON output | `--json` → exactly one JSON object on stdout, no ANSI\u002Femoji. `--verbose` + `--json` → reject with error. |\n| R7 | Standard flags | `--output \u003Cmode>` (canonical), `--json` (shorthand), `-y\u002F--yes`, `--verbose`, `--dry-run`, `--force`, `--env-file \u003Cpath>`. |\n| R8 | Clear progress text | Every step uses `ProgressIndicator` with action-oriented text. |\n| R9 | No credentials\u002FPII | Truncate tokens, use boolean indicators, never log emails\u002FOIDs. |\n| R10 | `--dry-run` explains | Lists planned ops without mutations; viable previews exit `0`, validation failures exit nonzero. |\n| R11 | `--help` everywhere | `.description()` on every command\u002Foption\u002Fargument. See [reference §5](.\u002Freferences\u002Fcli-ux-guidelines.md) for canonical descriptions. |\n| R12 | Semantic exit codes | `0` = success, `1` = error, `2` = cancelled. |\n\n## Decision Shortcuts\n\n- \"Command or flag?\" → Changes **what** = command. Changes **how** = flag.\n- \"`dev` or `up`?\" → Local Docker \u002F no auth → `dev`. Authenticated cloud → `up`.\n- \"Child service or connector?\" → Owned\u002Fdeployed with app → `rayfin \u003Cservice> init`. External → `rayfin connector add`.\n- \"`init` create this?\" → Only minimal base app (auth, data, static). Otherwise explicit follow-up command.\n- \"Implicit?\" → Only required system actions in `dev`\u002F`up`. User-facing = explicit.\n\n## Common Patterns (keep — action-oriented)\n\n### Standard action handler (legacy path)\n\n```typescript\n.action(async (cmdOptions) => {\n  const mode = resolveOutputMode({ json: cmdOptions.json });\n  const interactive = isInteractive({ yes: cmdOptions.yes });\n  const verbose = createVerboseLogger(cmdOptions.verbose);\n\n  try {\n    \u002F\u002F ...work...\n    if (mode === 'json') {\n      emitJson({ status: 'success', ...result });\n    }\n  } catch (err) {\n    if (mode === 'json') {\n      emitJsonError(mode, (err as Error).message);\n    }\n    modeError(mode, `❌ ${(err as Error).message}`);\n    modeError(mode, '   \u003Crecovery hint>');\n    throw new CliHandledError(err);\n  }\n})\n```\n\n### Error with recovery hint\n\n```typescript\nmodeError(mode, '❌ Project name not found in rayfin.yml configuration');\nmodeError(mode, \"   Run 'rayfin init' to create a new project configuration\");\nthrow new CliHandledError(new Error('...'));\n```\n\n### Progress step\n\n```typescript\nconst spinner = showProgress('Deploying configuration', '?', mode);\ntry {\n  await doWork();\n  spinner.succeed('Configuration deployed');\n} catch (err) {\n  spinner.fail('Configuration deployment failed');\n  throw err;\n}\n```\n\n## Implementing a New Command\n\n> **First decide: v2 workflow or legacy path?** New commands target the workflow + adapter architecture (see [migration plan](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture-migration.md)).\n> The legacy steps below are for un-migrated commands only.\n\n**V2 command** (preferred): orchestration in `common\u002Fsrc\u002Fworkflows\u002F\u003Cname>\u002F`, Commander `.action()` is a thin wrapper that parses → builds deps → calls workflow → renders `Result` via adapters → maps exit code.\n\n**Legacy path** (un-migrated commands):\n\n1. Create command file in `packages\u002Ftools\u002Fcli\u002Fsrc\u002Fcommands\u002F`.\n2. Import utilities from `..\u002Futils\u002Foutput-mode.js`.\n3. Add `--json`, `-y\u002F--yes`, `--verbose` options.\n4. Add `--dry-run`\u002F`--force` when applicable.\n5. Wrap progress in `ProgressIndicator`.\n6. Follow the standard action handler skeleton above.\n7. Register in parent `index.ts`.\n\n## Reviewing a Command (checklist by rule ID)\n\n- [ ] R1 — supports interactive, plain, json modes\n- [ ] R2 — no bare `console.log`\n- [ ] R3 — every `❌` has a recovery hint\n- [ ] R6 — `--json` emits valid JSON only; no ANSI\u002Femoji\n- [ ] R4 — destructive ops gated on `--force`\n- [ ] R5 — prompts respect `isInteractive()`\n- [ ] R8 — progress uses `ProgressIndicator` with action text\n- [ ] R10 — `--dry-run` lists ops without mutations and uses a semantic exit code\n- [ ] R9 — no PII in verbose output\n- [ ] R11 — `--help` descriptions present, canonical wording for standard flags\n- [ ] R12 — exit codes are semantic\n- [ ] Spec includes user intent, behavior contract, validation\u002Ffailures, error wording, examples, cross-cutting impacts\n\n## Command Topology: `dev` vs `up`\n\nSee [reference §12](.\u002Freferences\u002Fcli-ux-guidelines.md) for full rationale and patterns.\n\nKey rules:\n\n1. Mirror nouns under both `dev` and `up` when capability exists in both worlds.\n2. `dev` = local Docker, offline, single env, lifecycle via flags (`--stop`, `--down`, etc.).\n3. `up` = Fabric cloud, requires auth (except inspection), multi-env via subcommands.\n4. `dev` never authenticates. Inspection commands (`status`, `list`) never block on auth.\n5. `--force` means \"allow destructive schema changes\" — not \"skip prompt\" (that's `--yes`).\n\n## Pre-flight Checklist (OpenSpec CLI changes)\n\nEvery `tasks.md` for a CLI-touching OpenSpec change MUST begin with this block:\n\n```markdown\n## Pre-flight\n\n- [ ] Loaded `.github\u002Fskills\u002Frayfin-cli-ux\u002FSKILL.md`. Cite one rule applied: \u003CID and restatement>.\n- [ ] Loaded `.github\u002Fskills\u002Frayfin-cli-ux\u002Freferences\u002Fcli-ux-guidelines.md`. Cite one section: \u003Cname>.\n- [ ] Every new\u002Fchanged command, option, argument has a `.description()` (R11).\n- [ ] Every `❌` error has a recovery hint (R3).\n- [ ] All three output modes covered in scenarios (R1).\n- [ ] Destructive ops gated on `--force` (R4).\n- [ ] Non-interactive behavior preserved (R5).\n- [ ] `dev` vs `up` topology rules respected if adding lifecycle commands.\n```\n\n## Final Scan (Guardrails)\n\nBefore submitting, verify none of the NEVER\u002FALWAYS rules are violated:\n\n- NEVER: bare `console.log` (R2), prompt when non-interactive (R5), partial\u002Fmultiple JSON (R6), error without recovery (R3), destructive without `--force` (R4), PII in logs (R9), emoji outside interactive (R1), mutating API calls in dry-run (R10), auth in `dev` commands.\n- ALWAYS: action-oriented progress text (R8), standard flag names (R7), mirror `dev`\u002F`up` nouns, regenerate `.env.local` after lifecycle commands.\n\nDry-run reads require an explicit documented contract.\n`rayfin up` authenticates and reads workspace metadata so its preview can identify the resolved target; it validates local static inputs first and never runs builds or deployment writes.\nSee reference section 7 for this exception to the otherwise offline dry-run contract.\n","# Rayfin CLI UX Guidelines\n\nStandards for consistent, high-quality CLI experiences in `@microsoft\u002Frayfin-cli`.\n\n**Full reference**: [references\u002Fcli-ux-guidelines.md](.\u002Freferences\u002Fcli-ux-guidelines.md) — load on demand for depth, examples, and rationale.\n\n## Architecture Status\n\nThese rules define *what* a good CLI experience must deliver — they stay in force regardless of wiring.\n*How* output is wired is mid-migration to the workflow + adapter architecture ([`docs\u002Frfc\u002Frayfin-tools-architecture.md`](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture.md), tracked in [`rayfin-tools-architecture-migration.md`](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture-migration.md)).\n\n- **New or migrated commands** use a `common\u002Fsrc\u002Fworkflows\u002F\u003Cname>\u002F` workflow returning a typed `Result\u003CT>`, with a thin Layer-1 Commander wrapper rendering via `Logger`\u002F`Progress` adapters selected from `--output \u003Cmode>`. Do **not** import `output-mode.ts`, branch on raw `--json`\u002F`--verbose`, or use `CliHandledError`\u002F`process.exit`.\n- **Legacy (un-migrated) commands** use `output-mode.ts` (`modeLog`\u002F`emitJson`\u002F`resolveOutputMode`). This machinery is scheduled for removal in Phase 6.\n- When this skill and the architecture RFC disagree, the RFC wins.\n\n## Constitutional Rules\n\nNon-negotiable for every CLI command. Each rule has a stable ID (R1–R12) for cross-referencing.\n\n| ID | Rule | One-liner |\n|----|------|-----------|\n| R1 | Three output modes | Every command supports `interactive`, `plain`, and `json`. See [reference §1](.\u002Freferences\u002Fcli-ux-guidelines.md). |\n| R2 | No `console.log` | All output goes through mode-aware utilities (or v2 `Logger`\u002F`Progress` adapters). |\n| R3 | Recovery hints | Every `❌` error includes an indented next-step action. |\n| R4 | `--force` for destructive ops | Operations risking data loss fail by default; `--force` opts in. |\n| R5 | Respect non-interactive | No prompts when `--yes`, non-TTY stdin, or `CI=true`. |\n| R6 | Valid JSON output | `--json` → exactly one JSON object on stdout, no ANSI\u002Femoji. `--verbose` + `--json` → reject with error. |\n| R7 | Standard flags | `--output \u003Cmode>` (canonical), `--json` (shorthand), `-y\u002F--yes`, `--verbose`, `--dry-run`, `--force`, `--env-file \u003Cpath>`. |\n| R8 | Clear progress text | Every step uses `ProgressIndicator` with action-oriented text. |\n| R9 | No credentials\u002FPII | Truncate tokens, use boolean indicators, never log emails\u002FOIDs. |\n| R10 | `--dry-run` explains | Lists planned ops without mutations; viable previews exit `0`, validation failures exit nonzero. |\n| R11 | `--help` everywhere | `.description()` on every command\u002Foption\u002Fargument. See [reference §5](.\u002Freferences\u002Fcli-ux-guidelines.md) for canonical descriptions. |\n| R12 | Semantic exit codes | `0` = success, `1` = error, `2` = cancelled. |\n\n## Decision Shortcuts\n\n- \"Command or flag?\" → Changes **what** = command. Changes **how** = flag.\n- \"`dev` or `up`?\" → Local Docker \u002F no auth → `dev`. Authenticated cloud → `up`.\n- \"Child service or connector?\" → Owned\u002Fdeployed with app → `rayfin \u003Cservice> init`. External → `rayfin connector add`.\n- \"`init` create this?\" → Only minimal base app (auth, data, static). Otherwise explicit follow-up command.\n- \"Implicit?\" → Only required system actions in `dev`\u002F`up`. User-facing = explicit.\n\n## Common Patterns (keep — action-oriented)\n\n### Standard action handler (legacy path)\n\n```typescript\n.action(async (cmdOptions) => {\n  const mode = resolveOutputMode({ json: cmdOptions.json });\n  const interactive = isInteractive({ yes: cmdOptions.yes });\n  const verbose = createVerboseLogger(cmdOptions.verbose);\n\n  try {\n    \u002F\u002F ...work...\n    if (mode === 'json') {\n      emitJson({ status: 'success', ...result });\n    }\n  } catch (err) {\n    if (mode === 'json') {\n      emitJsonError(mode, (err as Error).message);\n    }\n    modeError(mode, `❌ ${(err as Error).message}`);\n    modeError(mode, '   \u003Crecovery hint>');\n    throw new CliHandledError(err);\n  }\n})\n```\n\n### Error with recovery hint\n\n```typescript\nmodeError(mode, '❌ Project name not found in rayfin.yml configuration');\nmodeError(mode, \"   Run 'rayfin init' to create a new project configuration\");\nthrow new CliHandledError(new Error('...'));\n```\n\n### Progress step\n\n```typescript\nconst spinner = showProgress('Deploying configuration', '?', mode);\ntry {\n  await doWork();\n  spinner.succeed('Configuration deployed');\n} catch (err) {\n  spinner.fail('Configuration deployment failed');\n  throw err;\n}\n```\n\n## Implementing a New Command\n\n> **First decide: v2 workflow or legacy path?** New commands target the workflow + adapter architecture (see [migration plan](..\u002F..\u002F..\u002Fdocs\u002Frfc\u002Frayfin-tools-architecture-migration.md)).\n> The legacy steps below are for un-migrated commands only.\n\n**V2 command** (preferred): orchestration in `common\u002Fsrc\u002Fworkflows\u002F\u003Cname>\u002F`, Commander `.action()` is a thin wrapper that parses → builds deps → calls workflow → renders `Result` via adapters → maps exit code.\n\n**Legacy path** (un-migrated commands):\n\n1. Create command file in `packages\u002Ftools\u002Fcli\u002Fsrc\u002Fcommands\u002F`.\n2. Import utilities from `..\u002Futils\u002Foutput-mode.js`.\n3. Add `--json`, `-y\u002F--yes`, `--verbose` options.\n4. Add `--dry-run`\u002F`--force` when applicable.\n5. Wrap progress in `ProgressIndicator`.\n6. Follow the standard action handler skeleton above.\n7. Register in parent `index.ts`.\n\n## Reviewing a Command (checklist by rule ID)\n\n- [ ] R1 — supports interactive, plain, json modes\n- [ ] R2 — no bare `console.log`\n- [ ] R3 — every `❌` has a recovery hint\n- [ ] R6 — `--json` emits valid JSON only; no ANSI\u002Femoji\n- [ ] R4 — destructive ops gated on `--force`\n- [ ] R5 — prompts respect `isInteractive()`\n- [ ] R8 — progress uses `ProgressIndicator` with action text\n- [ ] R10 — `--dry-run` lists ops without mutations and uses a semantic exit code\n- [ ] R9 — no PII in verbose output\n- [ ] R11 — `--help` descriptions present, canonical wording for standard flags\n- [ ] R12 — exit codes are semantic\n- [ ] Spec includes user intent, behavior contract, validation\u002Ffailures, error wording, examples, cross-cutting impacts\n\n## Command Topology: `dev` vs `up`\n\nSee [reference §12](.\u002Freferences\u002Fcli-ux-guidelines.md) for full rationale and patterns.\n\nKey rules:\n\n1. Mirror nouns under both `dev` and `up` when capability exists in both worlds.\n2. `dev` = local Docker, offline, single env, lifecycle via flags (`--stop`, `--down`, etc.).\n3. `up` = Fabric cloud, requires auth (except inspection), multi-env via subcommands.\n4. `dev` never authenticates. Inspection commands (`status`, `list`) never block on auth.\n5. `--force` means \"allow destructive schema changes\" — not \"skip prompt\" (that's `--yes`).\n\n## Pre-flight Checklist (OpenSpec CLI changes)\n\nEvery `tasks.md` for a CLI-touching OpenSpec change MUST begin with this block:\n\n```markdown\n## Pre-flight\n\n- [ ] Loaded `.github\u002Fskills\u002Frayfin-cli-ux\u002FSKILL.md`. Cite one rule applied: \u003CID and restatement>.\n- [ ] Loaded `.github\u002Fskills\u002Frayfin-cli-ux\u002Freferences\u002Fcli-ux-guidelines.md`. Cite one section: \u003Cname>.\n- [ ] Every new\u002Fchanged command, option, argument has a `.description()` (R11).\n- [ ] Every `❌` error has a recovery hint (R3).\n- [ ] All three output modes covered in scenarios (R1).\n- [ ] Destructive ops gated on `--force` (R4).\n- [ ] Non-interactive behavior preserved (R5).\n- [ ] `dev` vs `up` topology rules respected if adding lifecycle commands.\n```\n\n## Final Scan (Guardrails)\n\nBefore submitting, verify none of the NEVER\u002FALWAYS rules are violated:\n\n- NEVER: bare `console.log` (R2), prompt when non-interactive (R5), partial\u002Fmultiple JSON (R6), error without recovery (R3), destructive without `--force` (R4), PII in logs (R9), emoji outside interactive (R1), mutating API calls in dry-run (R10), auth in `dev` commands.\n- ALWAYS: action-oriented progress text (R8), standard flag names (R7), mirror `dev`\u002F`up` nouns, regenerate `.env.local` after lifecycle commands.\n\nDry-run reads require an explicit documented contract.\n`rayfin up` authenticates and reads workspace metadata so its preview can identify the resolved target; it validates local static inputs first and never runs builds or deployment writes.\nSee reference section 7 for this exception to the otherwise offline dry-run contract.\n",{"name":5,"description":7},"main","0979439a7a0806abd0ee48c2619b37f297ae1324",".github\u002Fskills\u002Frayfin-cli-ux",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":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add microsoft\u002Frayfin --skill rayfin-cli-ux",{"tool":46,"command":47},"bunx","bunx skills add microsoft\u002Frayfin --skill rayfin-cli-ux",{"tool":49,"command":50},"pnpm","pnpm dlx skills add microsoft\u002Frayfin --skill rayfin-cli-ux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frayfin-cli-ux\u002FSKILL.md",true,[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcli-ux-guidelines.md","REFERENCE","参考文档",28050,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Frayfin\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Frayfin-cli-ux\u002Freferences\u002Fcli-ux-guidelines.md",[61,73,91,100,117,125],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":26},"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",[],[68,69,70,71,9,72,24],"rayfin getting started","rayfin","scaffold","init","docs",{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":87,"publishedAt":26},"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",[79,84],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[75,88,89,90],"components","dashboard","visualize",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":26},"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",[],[98,99],"schema discovery","dax",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":113,"publishedAt":26},"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",[106,109,112],{"categoryNo":107,"categoryName":108,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":110,"categoryName":111,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,115,99,116],"query design","design","typescript",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":26},"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",[],[124],"functions capability",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":26},"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",[],[132,133,99,134,69,135],"sdk","fabric sdk","rayfin connectors","connectors"]