troubleshooting

Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky tests, screenshot diffs), build errors (Cannot find module, wireit cache issues, stale output), CI/CD failures, Git LFS problems, port conflicts, lighthouse score regressions, SSR errors, or environment setup issues.

Zur Installation springen Dateien prüfen

Repository: NVIDIA/elements
Letzte Quellaktivität: 3. September 2026 um 20:51
Erkannte Sprache von SKILL.md: Englisch
Sterne: 93
Forks: 18

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit einem KI-Assistenten installieren

Diesen Prompt kopieren und in den verwendeten KI-Assistenten einfügen.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/NVIDIA/elements/tree/main/.agents/skills/troubleshooting.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

npx skills add https://github.com/NVIDIA/elements --skill troubleshooting

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

name: troubleshooting
description: Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky tests, screenshot diffs), build errors (Cannot find module, wireit cache issues, stale output), CI/CD failures, Git LFS problems, port conflicts, lighthouse score regressions, SSR errors, or environment setup issues.

# Troubleshooting You MUST review the troubleshooting guideline when diagnosing test failures, build errors, or performance issues. ## When to Use This Skill - Debugging unit test failures or timing issues - Investigating visual regression test differences - Troubleshooting Lighthouse performance scores - Resolving build failures or Wireit cache issues - Fixing Git LFS problems with visual baselines - Diagnosing CI/CD pipeline failures - Resolving development environment setup issues - Investigating performance regressions in tests or builds ## Must Read File Read the [troubleshooting guide](projects/site/src/docs/internal/guidelines/troubleshooting.md) to get critical context for troubleshooting guidance. ## Diagnostic Triage Workflow 1. **Identify the symptom category:** - **Test failure**:unit, axe, visual, SSR, or lighthouse? - **Build failure**:Wireit cache, dependency resolution, TypeScript, or circular imports? - **Environment issue**:Node version, pnpm version, Git LFS, or port conflict? - **Performance regression**:slow tests, slow builds, or large bundles? 2. **Run the relevant diagnostic commands:** - Test failures: `pnpm run test -- src/<component>/<component>.test.ts` (isolate the failing test) - Build failures: `pnpm run ci:reset` then `pnpm run build` (clear caches first) - Environment: `node --version && pnpm --version && git lfs env` (verify toolchain) 3. **Check the matching section** in the troubleshooting guide for the specific symptom/solution pair. 4. **If the issue persists**, compare against a working reference component (badge, button, or card) to spot structural differences. ## References - [Troubleshooting Guide](/projects/site/src/docs/internal/guidelines/troubleshooting.md) - Common issues and solutions - [Testing Guidelines](/projects/site/src/docs/internal/guidelines/testing.md) - Test patterns - [Unit Testing](/projects/site/src/docs/internal/guidelines/testing-unit.md) - Unit test details - [Visual Testing](/projects/site/src/docs/internal/guidelines/testing-visual.md) - Visual regression details - [Lighthouse Testing](/projects/site/src/docs/internal/guidelines/testing-lighthouse.md) - Performance testing - [Build System](/projects/internals/BUILD.md) - Wireit troubleshooting

Auf GitHub ansehen

Zurück zur Suche Zurück zur Installation

summarize-releases

Create a monthly NVIDIA Elements “What’s New” docs page, matching video, and concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language explanation of recent Elements releases.

2026-10-01

summarize-video-releases

Create the 24–36 second marketing video for a monthly NVIDIA Elements “What’s New” post, rendered to projects/site/public/static/video/releases/MM-YYYY.webm from real Elements components, with feature snapshots inserted into the post. Use after the summarize-releases skill creates or updates a post, and whenever someone asks for a release video, what’s new video, monthly recap clip, changelog teaser, social video, or animated summary of Elements releases, even if they do not say “video skill”.

2026-10-01

agent-starters

Verify every starter supported by the stable production NVIDIA Elements CLI from a fresh consumer environment, investigate failures, and prepare at most one focused repair pull request. Use for nightly or scheduled production starter verification and starter availability failures.

2026-09-30

Alle aus diesem Repository ansehen

troubleshooting

Quellinformationen

Installationsoptionen

Mit einem KI-Assistenten installieren

Quelldateien prüfen

Mehr aus diesem Repository

Mit einem KI-Assistenten installieren

Mehr aus diesem Repository