biome-formatting
Use when formatting JavaScript/TypeScript code with Biome's fast formatter including patterns, options, and code style management.
biome-linting
Use when applying Biome's linting capabilities, rule categories, and code quality enforcement to JavaScript/TypeScript projects.
checkstyle-configuration
Use when configuring Checkstyle for Java projects with XML config, custom checks, properties, and module setup.
checkstyle-custom
Use when developing custom Checkstyle checks, filters, and plugin integrations for project-specific Java code standards.
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
clippy-configuration
Use when configuring Clippy for Rust projects with TOML config, lint groups, attributes, and workspace setup.
clippy-custom
Use when developing custom Clippy lints, implementing lint passes, and contributing to Clippy for Rust code standards.
clippy-lints
Use when applying Clippy lint categories for Rust code including correctness, performance, style, and custom lint configuration.
credo-checks
Use when understanding and fixing common Credo check issues for Elixir code quality and consistency.
credo-configuration
Use when configuring Credo static analysis for Elixir projects requiring customized code quality rules and settings.
credo-custom-checks
Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.
dialyzer-analysis
Use when analyzing and fixing Dialyzer warnings and type discrepancies in Erlang/Elixir code.
dialyzer-configuration
Use when configuring Dialyzer for Erlang/Elixir type checking and static analysis.
dialyzer-integration
Use when integrating Dialyzer into development workflows and CI/CD pipelines for Erlang/Elixir projects.
eslint-configuration
Use when eSLint configuration including config files, extends, plugins, and environment setup.
eslint-custom
Use when custom ESLint rules and plugins including rule development, AST traversal, and publishing.
eslint-rules
Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
markdown-documentation
Use when writing technical documentation, READMEs, or project documentation in markdown. Covers structure, conventions, and best practices.
markdown-syntax-fundamentals
Use when writing or editing markdown files. Covers headings, text formatting, lists, links, images, code blocks, and blockquotes.
markdown-tables
Use when creating or formatting tables in markdown. Covers table syntax, alignment, escaping, and best practices.
markdownlint-configuration
Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.
markdownlint-custom-rules
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.
markdownlint-integration
Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.
prettier-configuration
Use when prettier configuration including options, config files, ignore patterns, and formatting rules.
prettier-integration
Use when prettier integration with editors, pre-commit hooks, ESLint, and CI/CD pipelines.
prettier-plugins
Use when prettier plugins including plugin ecosystem, custom parsers, and plugin development.
pylint-checkers
Use when pylint checkers including built-in checkers, custom checkers, and checker development.
pylint-configuration
Use when pylint configuration including pylintrc, message control, plugins, and scoring system.
pylint-integration
Use when pylint CI integration including plugins, editor integration, and performance tuning.
rubocop-configuration
Use when ruboCop configuration including YAML config, departments, inheritance, and customization.
rubocop-cops
Use when ruboCop cops including built-in cops, configuration, auto-correction, and development.
rubocop-integration
Use when ruboCop CI integration including GitHub Actions, plugins, and performance optimization.
shell-error-handling
Use when implementing error handling, cleanup routines, or debugging in shell scripts. Covers traps, exit codes, and robust error patterns.
shell-portability
Use when writing shell scripts that need to run across different systems, shells, or environments. Covers POSIX compatibility and platform differences.
shell-scripting-fundamentals
Use when writing or modifying Bash/shell scripts. Covers script structure, variables, quoting, conditionals, and loops with modern best practices.
shell-best-practices
Use when writing shell scripts following modern best practices. Covers portable scripting, Bash patterns, error handling, and secure coding.
shfmt-configuration
Use when configuring shfmt for shell script formatting including .shfmt.toml setup, EditorConfig integration, and project-specific settings.
shfmt-formatting
Use when formatting shell scripts with shfmt. Covers consistent formatting patterns, shell dialect support, common issues, and editor integration.
validate
Validate checklist items for a ClickUp task without changing status
figma-analyze-frame
Analyze a Figma frame's structure, properties, and implementation considerations
figma-extract-tokens
Extract design tokens and variables from a Figma file to create or update a design system
figma-generate-component
Generate production-ready code from a Figma component or frame using the Figma MCP server
figma-sync-design-system
Sync design system components between Figma and code using Code Connect mappings
create-issue
Create a new issue in a GitHub repository
professional-honesty
Use when responding to questions or providing information requiring professional honesty and directness over excessive agreeableness.
plugin-development
Use when creating or modifying Han plugins. Covers plugin structure, configuration, hooks, skills, and best practices.
architect
Design system architecture and high-level technical strategy
boy-scout-rule
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
code-review
Code review a pull request
debug
Investigate and diagnose issues without necessarily fixing them
Page 16 of 17 · 803 results