Essential command-line tools and system utilities.
Build CLI tools using Go with Cobra and Viper. Use for implementing agentctl commands, interactive prompts, configuration management, and output formatting. Triggers on "CLI", "agentctl", "command line", "cobra", "terminal application", "interactive prompt", or when implementing spec/009-developer-experience.md CLI section.
CLIツール開発ガイド。Node.js（Commander、Inquirer）、Python（Click、Typer）、Go（Cobra）、引数パース、インタラクティブUI、アーキテクチャ設計、テスト、配布方法など、プロフェッショナルなCLIツール開発のベストプラクティス。
Renders structured data to terminal with optimal formatting. Use when presenting agent results, displaying data to users, formatting command output, or showing validation reports. Transforms raw data into clear, scannable terminal output.
Creates a new custom slash command file. Use when: user wants to create a new command, add a slash command, or define a custom command.
Capture PNG screenshots of dex TUI commands for debugging UI layout issues. Use when iterating on CLI interface code or debugging rendering problems.
This skill should generate classes for scrcpy CLI arguments. This skill should be used when adding support for new scrcpy CLI arguments to the app.
Display directory structure as a formatted tree. Use when the user needs to visualize a directory structure, analyze folder organization, or share a file tree view. Supports custom paths via the /tree command.
Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.
You are a meticulous and performance-obsessed Performance Benchmarker. You are an expert at designing and executing rigorous performance tests to measure the speed, scalability, and resource consumption of software. You are proficient with load testing tools (like k6, JMeter, or Locust) and profiling tools.
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling. Use PROACTIVELY for any TypeScript/JavaScript issues including complex type gymnastics, build performance, debugging, and architectural decisions. If a specialized expert is a better fit, I will recommend switching and stop.
Code coverage for Rust using LLVM instrumentation with support for multiple output formats and CI integration. Use when measuring test coverage, generating coverage reports, enforcing coverage thresholds, or integrating with codecov/coveralls. Trigger terms: coverage, llvm-cov, code coverage, test coverage, coverage report, codecov, coveralls, branch coverage.
Analyze system performance using throttle statistics, query logs, and resource metrics to identify bottlenecks and optimization opportunities
Get download statistics for an npm package over time. Use when the user asks for package download counts, popularity metrics, or usage statistics.
Analyze code structure, patterns, and complexity without making modifications. Use when reviewing code, planning refactoring, or conducting read-only code analysis.
Semantic code chunking and search patterns for codebase exploration
Use when researching features in jellyfin-web (the Jellyfin server's web UI rendered in CEF) or jellyfin-desktop (old Qt app) for reference during implementation
Analyzes HTML files for SEO issues using static analysis with cheerio. Checks meta tags, Open Graph, Twitter Cards, heading structure, and JSON-LD structured data. Use when user mentions "SEO check", "meta tags", "og tags", "structured data validation", "SEO audit", or wants to analyze HTML/JSX for SEO compliance.
4-phase debugging process (Observe, Hypothesize, Test, Fix) for complex issues. Use when debugging fails, investigating flaky tests, tracking root causes, or facing mysterious bugs.
