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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « devtools ». Where should I place devtools in my Vue json-render app?
Résultat attendu:
- 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.
Utilisation de « devtools ». My fixed chat composer overlaps the bottom inspector.
Résultat attendu:
- 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.
Utilisation de « devtools ». How do I stop state collisions across generated chat turns?
Résultat attendu:
- 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.
Audit de sécurité
SûrAll 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.
Facteurs de risque
⚙️ Commandes externes (50)
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/vercel-labs-devtools/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/vercel-labs-devtools?utm_source=security_passport_badge)Badge HTML
<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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
vercel-labs. (2026). devtools security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/vercel-labs-devtools/audits/1Citation BibTeX
@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"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces prompts
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.
Bonnes pratiques
- 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.
Éviter
- 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.
Foire aux questions
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?
Détails du développeur
Auteur
vercel-labsLicence
MIT
Révision Skillstore
r1
Avis de version
L’auteur n’a déclaré aucune version.
Réf
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Récence de maintenance
30/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đź“„ SKILL.md