Results for “devtools”

Jwt reference tool. Use when working with jwt in devtools contexts.

Cors reference tool. Use when working with cors in devtools contexts.

Use only for developer-facing products; plan adoption loops, examples, templates, community, and proof artifacts

Use only for developer-facing products; analyze install, quickstart, first success, debugging, and production adoption journeys

Use only for developer-facing products; map users, buyers, champions, contributors, and operational stakeholders

Automates multi-language software builds with Makefiles, dependency management, testing, packaging, and CI/CD integration.

Control browsers via a CLI tool that runs sandboxed JavaScript scripts for automation, testing, and data extraction.

钉钉(DingTalk) MultiSkill 的轻量共享入口。Use when 用户泛称 DWS/钉钉操作但未明确产品、请求跨产品编排、需要 URL 类型预检或产品边界消歧。清晰的单产品操作优先使用对应 dingtalk-* 子 skill；本 skill 只提供全局执行契约和按需 reference 导航，不承载产品命令全集。

Debug Node.js via --inspect + Chrome DevTools Protocol CLI.

钉钉开放平台企业内部应用管理：应用查询/创建/修改/删除/停启、凭证、权限点、成员、安全配置、网页应用、机器人、版本发布。Use when 用户说 开发者后台应用/开放平台应用/企业内部应用/agentId/clientId/appKey/appSecret/customKey/应用权限/权限点/scopeValue/创建机器人/智能体机器人/机器人配置/机器人回调/IP白名单/登录重定向/端内免登/应用版本/版本发布/发布审核/选审批人/把机器人接到本地调试/connect。

Use when working with VCF/BCF variant files for indexing, manipulation, analysis, or variant calling.

Creates pre-configured devcontainers with Claude Code, language-specific tooling (Python, Node, Rust, Go), and persistent volumes for isolated development environments.

Creates, reviews, debugs, and modernizes Python project structure with deterministic tooling including pyproject.toml, uv, Ruff, Pyright, and pytest.

Csrf reference tool. Use when working with csrf in devtools contexts.

Debug Node.js with node inspect, --inspect, breakpoints, CDP, heap, and CPU profiles.

Process and analyze high-throughput sequencing data with deepTools for quality control, normalization, comparison, and publication-quality visualizations of ChIP-seq, RNA-seq, and ATAC-seq experiments.

Learn to combine DeFi protocols safely: Uniswap V4 hooks, Aave flash loans, ERC-4626 vaults, Aerodrome on Base, GMX/Pendle on Arbitrum, and dominant DEX per L2.

Generating and auditing personal dev environment configs (zsh/tmux/neovim/ghostty) and automating the macOS desktop via AppleScript/JXA (Finder, Mail, Safari). Use for dotfiles or Apple Events.

Sets up Pawbytes Tools module in a project. Use when the user requests to 'install paw tools', 'configure Pawbytes Tools', or 'setup utility tools'.

Query and analyze SEC filings using EdgarTools

Use when performing genome arithmetic on interval files (BED, BAM, BEDGRAPH), including intersection, merging, coverage, format conversion, or sequence extraction.

Development with Vhdl: tools and best practices

Build interfaces with UnoCSS using semantic tokens, dark mode parity, and design polish for devtools and landing pages.

Systematically find and fix bugs using proven debugging techniques, tracing from symptoms to root cause, implementing fixes, and preventing regression.

Runs a persistent verification-and-fix loop, executing existing test suites and browser/desktop checks until the requested surface is verified or a real blocker remains.

Trigger: macOS UI, screen recording, simulator UI, desktop app click, capture screen, system dialog, macOS clipboard, menu bar, drag drop. Scope: Automate macOS GUI applications, drive input events, list windows/spaces, and capture visual state via Peekaboo CLI. Boundary: Excludes pure browser-level automation (use chrome-devtools instead) or headless server tasks.

Flutter cross-platform development guide covering widget patterns, Riverpod/Bloc state management, GoRouter navigation, performance optimization, and platform-specific implementations. Includes const optimization, responsive layouts, testing strategies, and DevTools profiling. Use when: building Flutter apps, implementing state management (Riverpod/Bloc), setting up GoRouter navigation, creating custom widgets, optimizing performance, writing widget tests, cross-platform development.

Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.