菜单
Start the nvcf-ui development server. Use when asked to run, start, or launch the app, or to verify a change works in the browser.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/NVIDIA/nvcf --skill run命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Install, operate, and tear down self-hosted NVIDIA Cloud Functions (NVCF) deployments with nvcf-cli. Use for control-plane or compute-plane install, status checks, cluster registration, function deploy/invoke, task create/list/cancel/delete, API keys, admin tokens, JWKS rotation, failed-install diagnosis, and uninstall or down workflows. Trigger keywords: nvcf, nvcf-cli, self-hosted nvcf, self-managed nvcf, NVCFBackend, NVCA, NCP, ICMS, helmfile, control plane, compute plane, LLM function, OpenAI-compatible invocation, Responses API, embeddings, batch task, task monitor, cluster rotate, cluster delete, helm task, helm-based task, task secrets, update task secrets, retrieve task results, bulk fetch tasks, task results, NVCT, NVCT task, NVCT batch job.
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
Add a new UI feature to the nvcf-ui app — folder structure, routing, data loading, lazy-loading, testing, and completion checklist. Use when creating a new feature folder, adding a page or view, wiring routes, building a new screen, or deciding whether to extend an existing feature vs create a new one. Also use when the user asks to build something new in the UI, even if they don't say "feature" explicitly.
基于 SOC 职业分类
正在显示 SKILL.md
| name | run |
| description | Start the nvcf-ui development server. Use when asked to run, start, or launch the app, or to verify a change works in the browser. |
| license | Apache-2.0 |
| allowed-tools | ["Bash"] |
There is no local backend — the app either runs against a real cluster or uses MSW mocks.
VITE_MOCK=true task ui:dev
Starts Vite at http://localhost:5173 with MSW intercepting all API requests using the seeded in-memory store. No cluster required. Use this for UI development.
To layer a scenario on top of the baseline store:
VITE_MOCK=true VITE_SCENARIO=functions:empty-list task ui:dev
Multiple scenarios are comma-separated: VITE_SCENARIO=functions:empty-list,tasks:launching-task.
task ui:dev
No VITE_MOCK — requests proxy to the configured upstream. Requires cluster access. Check ui/vite.config.ts for the proxy target.