agentleFS
Sign inStart free
NVIDIAKnown publisherNVIDIA/nvcf/src/uis/nvcf-ui/.agents/skills/run/SKILL.md

run

Skill268 starsChanged 3 days agoApache-2.0View on GitHub

Start the nvcf-ui development server. Use when asked to run, start, or launch the app, or to check a change in the browser.

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use init, report and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    init

    Also in 4 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 5 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • +1 more from microsoft

The file

Create a free account to mount
Files
SKILL.md

Running nvcf-ui

Mock mode (use this for UI work)

task ui:dev MOCK=true

Starts Vite at http://localhost:5173. MSW answers every API request from the seeded in-memory store. No cluster or backend is needed.

Layer a scenario over the store:

task ui:dev MOCK=true SCENARIO=functions:empty-list

Separate several scenarios with commas.

Set MOCK and SCENARIO as task variables as shown. The task sets VITE_MOCK and VITE_SCENARIO itself, so exporting those variables has no effect.

Without mocks

task ui:dev without MOCK=true needs the backend for frontend running locally. The dev server proxies only /api to http://localhost:8080. Other API paths, such as /v2/nvcf/..., are answered with index.html, and the app fails with a JSON parse error. Running the backend against live upstreams needs in-cluster access; see README.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free