devtools
Debug json-render Apps with an Inspector Panel
Generative interfaces can make rendering errors, state changes, and streamed updates difficult to trace. This skill guides devtools integration and inspection workflows for json-render apps.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "devtools" from https://skillstore.io/skills/vercel-labs-devtools.md and its manifest at https://skillstore.io/api/skills/vercel-labs-devtools/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„devtools“ wird verwendet. Where should I place devtools in my Vue json-render app?
Erwartetes Ergebnis:
- Install the devtools core package and Vue adapter.
- Place the inspector inside the existing JSONUIProvider beside the renderer.
- Pass the current spec and provide a catalog for catalog browsing.
„devtools“ wird verwendet. My fixed chat composer overlaps the bottom inspector.
Erwartetes Ergebnis:
- Use right docking for a layout with a fixed bottom composer.
- Disable dock toggling when the application supports only that position.
- Use the published CSS offsets for fixed elements that still need space.
„devtools“ wird verwendet. How do I stop state collisions across generated chat turns?
Erwartetes Ergebnis:
- Keep one top-level provider and shared state store.
- Prefix each turn's element keys and state paths with a unique message identifier.
- Pass the latest spec to the Spec panel and all messages to the Stream panel.
Sicherheitsaudit
SicherAll 53 static findings are false positives: Markdown backticks and Solid framework references were misclassified as execution or reconnaissance. No evidence found of prompt injection, credential theft, or unauthorized data transfer in SKILL.md. This review covers integration documentation, not dependency implementations or runtime production safeguards.
Risikofaktoren
⚙️ Externe Befehle (50)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/vercel-labs-devtools/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/vercel-labs-devtools?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/vercel-labs-devtools?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vercel-labs-devtools/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/vercel-labs-devtools.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
vercel-labs. (2026). devtools security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/vercel-labs-devtools/audits/1BibTeX-Zitat
@techreport{vercel-labs-vercel-labs-devtools-2026,
author = {vercel-labs},
title = {devtools security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/vercel-labs-devtools/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "devtools security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "vercel-labs"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/vercel-labs-devtools/audits/1"
identifiers:
- type: other
value: "skillstore:vercel-labs-devtools:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Diagnose Missing UI Elements
Integrate the inspector to examine spec structure, visibility, and validation warnings when a generated component does not appear.
Trace Chat UI Streams
Connect shared providers and message history to inspect stream patches and separate state across generated conversation turns.
Reproduce State and Action Issues
Use runtime state editing and action timelines to investigate unexpected transitions in a development environment.
Diese Prompts ausprobieren
Add json-render devtools to my existing React app. Identify the provider and install the matching adapter before placing the inspector.
Help debug a missing element in my json-render interface. Use the spec tree, validation warnings, visibility settings, and current state.
Configure devtools for my app with a fixed bottom composer. Use right docking and review reserved space and CSS offsets for overlap.
Integrate devtools into my multi-turn json-render chat with one shared provider and namespaced state. Connect message history and a bounded server-side stream tap. Keep sensitive content out of telemetry.
Bewährte Praktiken
- Match the framework adapter to the host renderer and place the inspector inside the existing provider.
- Namespace state paths and element keys for each generated chat turn.
- Use test data, review captured events for sensitive content, and verify production behavior before deployment.
Vermeiden
- Wrapping every chat renderer in a separate state provider when the inspector needs shared state.
- Reusing state paths across generated messages without unique namespaces.
- Forwarding raw state, action parameters, or stream content to telemetry without reviewing sensitive data.
Häufig gestellte Fragen
Which frameworks does the skill cover?
Does the inspector run in production?
Can I edit application state?
Can one inspector cover multiple renderers?
Can I capture events on the server?
What does this skill install by itself?
Entwicklerdetails
Autor
vercel-labsLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Aktualität der Wartung
30.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
📄 SKILL.md