chromedev-tools

Q: How to install chromedev-tools?

Add a marketplace: /plugin marketplace add . Then add the config to /plugin install chromedev-tools@ . Finally, /plugin in Claude Code.

Q: What is chromedev-tools best for?

chromedev-tools is categorized under General. It covers: frontend, chrome, devtools, debugging, performance, inspection.

1Community RegistryGeneralby Chris Cardoso

Chrome DevTools integration for frontend development - inspect pages, debug console, analyze performance, monitor network

First seen 5/22/2026

View Source

Summary

This skill analyzes, optimizes, and secures your dotfiles by auditing configurations, recommending modern tools, and enforcing best practices.

It helps you maintain a clean, efficient, and secure development environment.

Overview

Personal Claude Code skills — a curated collection used daily across development, knowledge management, writing, and productivity workflows.

Install

Via `npx skills` (recommended — installs globally):

bash

npx skills@latest add kriscard/Skills

Via symlink (local dev — changes take effect immediately):

bash

bash scripts/link-skills.sh

This symlinks each skill directory into ~/.claude/skills/ so Claude Code picks them up without reinstalling.

Skills

Development

Skill	Description
`architect`	System design and architecture decisions — monolith vs services, API protocols, rendering strategy, GoF patterns, code smells
`frontend`	Frontend architecture — component patterns, state management, type system, security, Next.js
`react`	React code review — universal checks for hooks, state, performance, and modern React 19 patterns
`debug`	Root-cause debugging — systematic diagnosis, error tracing, fix verification
`refactor`	Code refactoring — readability, complexity reduction, extract patterns
`review`	Code review — security, performance, correctness, production reliability
`test`	Testing strategy — unit, integration, E2E, Vitest API reference (18 refs)
`commit`	Semantic git commits with conventional commit format
`pr-review`	Pull request review with parallel agent orchestration
`spec`	Turns Linear/GitHub issues or plain text into structured specs
`research`	Documentation research — APIs, frameworks, best practices
`analyze-repo`	Codebase analysis — architecture, dependencies, quality report
`claude-optimizer`	Audits and improves CLAUDE.md files for compliance and token efficiency

Obsidian (Second Brain)

Skill	Description
`vault`	Vault context and Obsidian CLI reference — load before any vault operation
`ingest`	Processes inbox items into synthesized wiki pages in Resources/
`save-note`	Files a session answer as a permanent wiki page
`project`	Creates and updates project notes following PARA methodology
`daily`	Daily note creation and startup workflow
`close-day`	End-of-day capture — wins, blockers, tomorrow's focus
`weekly`	Weekly review and reflection
`goals`	OKR and goal tracking across quarterly/monthly/weekly notes
`ideas`	Captures and develops ideas from the vault
`process-inbox`	Clears the Obsidian inbox — reads, discusses, files, and moves items
`ingest`	Ingests articles, tweets, videos into the knowledge base
`maintain`	Vault maintenance — broken links, orphaned notes, tag hygiene
`audit-para`	Audits vault structure against PARA principles
`memory-recall`	Surfaces relevant notes from past sessions
`spot-drift`	Identifies areas drifting from intention in the vault
`money`	Revenue advisor — scans vault, diagnoses revenue system, surfaces monetization opportunities

Writing & Content

Skill	Description
`blog`	Blog post writing — story structure, post templates, voice, SEO
`talk`	Conference talk builder — narrative arc, iA Presenter slides
`docs`	Technical documentation — ADRs, RFCs, architecture proposals, design docs
`tutorial`	Step-by-step technical tutorials with progressive disclosure

Dotfiles & Shell

Skill	Description
`shell-env`	Shell environment — zsh, tmux, starship, Ghostty, yabai via GNU Stow
`neovim`	Neovim config, performance optimization, and plugin management
`audit`	Dotfiles security audit and modern tool recommendations

Productivity

Skill	Description
`ideation`	Brain dump → contract → PRD → spec pipeline
`standup`	Daily standup generation from git history and notes
`career`	Career tracking, progression, and staff engineer workflow
`check-communication`	Communication quality review — clarity, tone, framing
`prototype`	Rapid prototyping with clear scope and fast feedback loops
`deslopify`	Removes AI slop from text — improves clarity and directness

Learning

Skill	Description
`learn`	Interactive learning sessions with documentation fetching
`til`	Captures session learnings into TIL notes in Obsidian

Local Development

bash

# List all skills
bash scripts/list-skills.sh

# Symlink skills to ~/.claude/skills/
bash scripts/link-skills.sh

License

MIT

Install & Usage

Add a marketplace

/plugin marketplace add <org/repo>

Install the plugin

Add the configuration to /plugin install chromedev-tools@<marketplace>

Manage with /plugin

/plugin

Use Cases

Audit your .zshrc or .bashrc for security vulnerabilities like exposed tokens or unsafe aliases.

Replace outdated shell utilities with modern alternatives like bat, fd, or ripgrep.

Optimize shell startup time by identifying slow-loading plugins or redundant configurations.

Standardize dotfiles across multiple machines with symlink management and version control tips.

Detect deprecated or insecure settings in Git, Vim, or tmux configs and suggest fixes.

Generate a comprehensive report of all dotfiles with recommendations for improvement.

Usage Examples

/dotfiles-optimizer audit ~/.zshrc for security issues and slow commands

Analyze my dotfiles and suggest modern replacements for grep, ls, and cat

Optimize my shell configuration to reduce startup time by 50%

View source on GitHub

frontendchromedevtoolsdebuggingperformanceinspection

Security Audits

LicenseUnknownSourceWarnRepositoryPass

Frequently Asked Questions

What is chromedev-tools?

This skill analyzes, optimizes, and secures your dotfiles by auditing configurations, recommending modern tools, and enforcing best practices. It helps you maintain a clean, efficient, and secure development environment.

How to install chromedev-tools?

To install chromedev-tools: add a marketplace (/plugin marketplace add <org/repo>), then add the config to /plugin install chromedev-tools@<marketplace>. Finally, /plugin in Claude Code.

What is chromedev-tools best for?

chromedev-tools is a plugin categorized under General. It is designed for: frontend, chrome, devtools, debugging, performance, inspection. Created by Chris Cardoso.

What can I use chromedev-tools for?

chromedev-tools is useful for: Audit your .zshrc or .bashrc for security vulnerabilities like exposed tokens or unsafe aliases.; Replace outdated shell utilities with modern alternatives like bat, fd, or ripgrep.; Optimize shell startup time by identifying slow-loading plugins or redundant configurations.; Standardize dotfiles across multiple machines with symlink management and version control tips.; Detect deprecated or insecure settings in Git, Vim, or tmux configs and suggest fixes.; Generate a comprehensive report of all dotfiles with recommendations for improvement..