{
  "markdown": "# NVIDIA Elements\n\nNVIDIA Design System and UI Agent Harness for AI/ML Factories, Robotics, and Autonomous Vehicles.\n\n- **Agent-ready tooling:** CLI and MCP expose component APIs, tokens, examples, imports, validation, and setup to terminals and AI assistants.\n- **Framework agnostic:** Web Components run in React, Angular, Vue, Svelte, Lit, plain HTML, server-rendered templates, and mixed stacks.\n- **Built for AI infrastructure:** Operational UI for AI/ML workloads, autonomous vehicle tools, and robotics consoles.\n- **Stable API contracts:** Skills and lint guide authoring best practices, common UI patterns, and automated static analysis.\n\n## Requests and Contributions\n\n- [NVIDIA Elements Documentation](https://NVIDIA.github.io/elements/)\n- [Contribution Guidelines](https://NVIDIA.github.io/elements/docs/about/contributions/)\n- [Feature request](https://github.com/NVIDIA/elements/issues/new?issuable_template=feature)\n- [Bug report](https://github.com/NVIDIA/elements/issues/new?issuable_template=default)\n- [Official NVIDIA Elements DESIGN.md](https://NVIDIA.github.io/elements/docs/design-md/)\n\n## Organization\n\nThe repository uses a top-level **repository** with individual **project** directories.\n\nProject directories have their own `package.json` and commands. Run CI and development setup at the root **repository** level.\n\nExamples of projects include:\n\n- `/projects/starters` - Suite of standardized starter apps for Elements and Patterns\n- `/projects/core` - Elements library: curated UI maintained by the Elements team\n- `/projects/themes` - Elements Theme library: provides a set of supported themes for Element based projects\n- `/projects/styles` - Elements Styles library: provides a set of CSS utilities for layout and typography\n\n## Development\n\n### Setup\n\nTo set up repository dependencies and run the full build, run the following commands at the **root** of the repository:\n\nThe CI pipeline also builds Go starters. Install [Go 1.26.x](https://go.dev/doc/install) before running the full local CI pipeline.\n\n```shell\n# install dependencies https://mise.en.dev/getting-started.html\ncurl https://mise.run | sh\n~/.local/bin/mise run setup\n```\n\n#### Troubleshooting\n\nIf you are coming from development from a different repository, you may need to refresh the repository toolchain with mise. Run `mise run install` at the root of the project to install the Node.js, pnpm, Vale, Go, Git LFS, and package versions from `mise.toml` and `pnpm-lock.yaml`.\n\nIf you actively switch between different repositories, run commands through `mise exec --` or activate mise in your shell so it switches tools automatically.\n\n### Building\n\nBoth the top-level repository and each project have a set of standardized npm scripts. To build and test all projects, run `mise exec -- pnpm run ci` at the root of the repository.\n\n#### Top-Level Repository\n\n- `ci`: run full build/lint/test\n- `ci:all`: entire CI process: build, lint, unit/lighthouse/visual tests\n- `ci:reset`: clear all caches/dependencies then reinstall dependencies\n\n#### Individual Projects\n\nCommon project scripts include:\n\n- `dev`: run in watch mode\n- `build`: run project/library build\n- `test`: run unit tests\n- `test:lighthouse`: run lighthouse performance tests\n- `test:visual`: run playwright visual regression tests\n- `test:axe`: run axe tests for a11y\n\nThe available scripts vary by project. Check the project's `package.json` before running project-specific commands.\n\nFor details about the repository build and runtime flow, see the [build system documentation](https://github.com/NVIDIA/elements/blob/main/projects/internals/BUILD.md).\n\n## Workflow\n\nBefore creating a branch or pull request, make a [new issue or feature request](https://github.com/NVIDIA/elements/issues/new) first so the team can check alignment and avoid duplicate work.\n\n### Create a Branch\n\nUse a descriptive branch name with the `topic/` prefix. Example `topic/bug-fix`.\n\n```shell\ngit checkout -b topic/bug-fix\n```\n\nAfter creating your branch, make your source code changes. After you complete them, run `mise exec -- pnpm run ci` in the root of the repo to run all the builds and tests. If all tests pass, you are ready to create a PR.\n\n### Commit Messages\n\nThe repo uses [Semantic Release](https://semantic-release.gitbook.io/semantic-release/) to manage package changes. Commit messages determine the release on merge. [Commit Lint](https://commitlint.js.org/) enforces commit formatting.\n\n```shell\ngit commit -a -s -m \"fix(core): disable multi-select\"\n```\n\n[Example Commit](https://github.com/NVIDIA/elements/commit/990d8f43a4a055c2f1ca1a6aa0af39f099d04649)\n\n| Types   | Description                                                     |\n| ------- | --------------------------------------------------------------- |\n| `fix`   | bug fixes, performance fixes                                    |\n| `feat`  | new features, components, APIs                                  |\n| `chore` | non production code modifications, build tooling, documentation |\n\n| Scopes      | Description                    |\n| ----------- | ------------------------------ |\n| `ci`        | CI and release automation      |\n| `cli`       | `/projects/cli`                |\n| `code`      | `/projects/code`               |\n| `core`      | `/projects/core`               |\n| `create`    | `/projects/create`             |\n| `deps`      | dependency updates             |\n| `docs`      | documentation and site content |\n| `forms`     | `/projects/forms`              |\n| `internals` | `/projects/internals`          |\n| `lint`      | `/projects/lint`               |\n| `markdown`  | `/projects/markdown`           |\n| `media`     | `/projects/media`              |\n| `monaco`    | `/projects/monaco`             |\n| `pages`     | `/projects/pages`              |\n| `starters`  | `/projects/starters`           |\n| `styles`    | `/projects/styles`             |\n| `themes`    | `/projects/themes`             |\n\nKeep commit names focused on your changes. The release process uses the commit message to determine the next release and generated changelog notes.\n\n### Opening a Pull Request\n\nOnce you have committed your changes to your branch locally, push them to the remote GitHub repository.\n\n```bash\ngit push --set-upstream origin topic/bug-fix\n```\n\nOpen a new [Pull Request](https://github.com/NVIDIA/elements/pulls) in GitHub. Request review from the team members and apply the appropriate labels in the GitHub UI, for example, `type:fix` and `scope(core)`.\n\n#### Amending Commit\n\n**If there are changes requested**, make the requested changes locally and amend the commit.\n\n```shell\ngit commit -a --amend --no-edit\n```\n\nThis adds the changes to your existing commit. Then push the updated commit back to the remote branch for review.\n\n```shell\ngit push --force origin topic/bug-fix\n```\n\n#### Rebasing Commit\n\nIf main changes before PR approval, rebase your local branch to include the latest changes from main.\n\n```shell\ngit checkout main # Switch to main branch\ngit pull # Pull down any new changes\ngit checkout topic/bug-fix # Switch back to your topic branch\ngit rebase main # Rebase your branch onto the latest main\n```\n\nYou may have to resolve any merge conflicts that arise from this process. Once complete, push the updated branch back to the remote repository for review.\n\n### New Project\n\nWhen creating a new project, ex: `./projects/code`, make sure to add the project to the `pnpm-workspace.yaml` located at the root directory.\n\n### Release\n\nAfter approval, merge your Pull Request into `main` through the GitHub UI. GitHub Actions triggers a [new release](https://github.com/NVIDIA/elements/releases) automatically. Semantic Release calculates the version from the commit type. The [changelog](https://NVIDIA.github.io/elements/docs/changelog/) also includes the commits from the PR.\n",
  "bytes": 7834,
  "sha": "1117e93f40c3df70dd3c6c396aaf0cbd4cf469a047e47203a077065ad6e87644",
  "repo_slug": "nvidia/elements",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_nvidia_elements_06d307a3/readme"
}