devtools-imports
Skill by ChromeDevTools · updated · ★ 4.1k
Conventions for importing code in Devtools to avoid build errors. Covers cross-module imports, internal imports, and the "import * as" requirement. devtools-imports is published by ChromeDevTools on GitHub.
Last commit in the past day
BSD-3-Clause: permissive, fine for commercial use
Clear description, installs from GitHub, 4,081 stars, original repository
Not checked yet. What we check
Install devtools-imports
Built from the published package, never by AIgit clone --depth 1 https://github.com/ChromeDevTools/devtools-frontend /tmp/devtools-frontend && mkdir -p ~/.claude/skills && cp -r /tmp/devtools-frontend/.agents/skills/devtools-imports ~/.claude/skills/devtools-importsRun in your terminal. Claude Code loads skills from ~/.claude/skills automatically.
git clone --depth 1 https://github.com/ChromeDevTools/devtools-frontend /tmp/devtools-frontend && mkdir -p ~/.gemini/antigravity-cli/skills && cp -r /tmp/devtools-frontend/.agents/skills/devtools-imports ~/.gemini/antigravity-cli/skills/devtools-importsAntigravity CLI loads skills from ~/.gemini/antigravity-cli/skills, or .agents/skills for one project.
Skills can run scripts on your machine. Some need an API key: check the README.
Alternatives to devtools-imports
All alternatives →Version bumping, release workflow, and PyPI publishing process for Visdom
Use when reviewing MobileBuildMCP rendering, streaming fragment, next-step, and CLI output mode changes for boundary violations.
Use when auditing slow page loads, heavy assets, or rendering delays related to Show loading indicators. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when auditing slow page loads, heavy assets, or rendering delays related to Use secure and up-to-date JS libraries. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use a single label for each form field. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Import Shade from layer-specific subpaths (primitives, components, patterns, page-templates, utils), never the root barrel. Trigger when editing TSX/TS in Shade-consuming apps.
devtools-imports: common questions
How do I install devtools-imports?
Run the command above to copy the skill into ~/.claude/skills/. Claude Code picks it up automatically.
Is devtools-imports free?
The code is published under the BSD-3-Clause licence. The service it connects to may have its own pricing.
Is devtools-imports safe to use?
It scores 83 of 100. Grades: maintenance A, licence A, quality A. The security check has not run for it yet. Review the code before you install. How grades work.
What are alternatives to devtools-imports?
Similar skills: release-process, mobilebuildmcp-rendering-streaming-review, loading-indicators, js-libraries.
