studio-dev
Skill138 starsChanged 20 days agoApache-2.0View on GitHub
Switch into Studio development mode for working on the NeMo Studio frontend in web/. Use when starting frontend work, building UI features, or working on React components.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- remotion-dev/remotiontheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- remotion-dev/remotion★ 72ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- .cursor/rules/dot-files.mdcCursor rule
- .cursor/rules/nemo-helix.mdcCursor rule
- .cursor/rules/uv.mdcCursor rule
- .cursor/rules/writing-docs.mdcCursor rule
- add-studio-feature-flagSkill
- contributor-create-prSkill
- create-release-notesSkill
- data-designer-skill-refreshSkill
- data-designer-version-bumpSkill
- nhx-cliSkill
- release-test-scopeSkill
- nemo-data-designer-pluginSkill
- nemo-evals-pluginSkill
The file
Files
Studio Development Mode
You are now in Studio development mode. Read the Studio project instructions to load full context:
@web/CLAUDE.md
What This Means
- Most changes will be in
web/— this is a React + TypeScript monorepo for NeMo Studio - The rest of the repo is useful for understanding backend APIs, data models, and SDK types, but changes should generally stay within
web/ - Studio-specific skills are now available — use
/unit-test,/e2e-test, and/visual-devfor testing and development workflows - Run frontend commands from
web/— pnpm, vitest, and other Node.js tooling lives there
Quick Reference
| What | Where |
| Main app | web/packages/studio/ |
| Shared code | web/packages/common/ |
| API SDK | web/packages/sdk/ |
| Storybook | web/packages/storybook/ |
| Dev tools | web/packages/sandbox/ |
| Backend APIs | services/ (read-only context) |
| OpenAPI spec | openapi/openapi.yaml (read-only context) |
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
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.