TheBushidoCollective/han - Page 9

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.

architect

Design system architecture and high-level technical strategy

baseline-restorer

Use when multiple fix attempts fail and you need to systematically restore to a working baseline and reimplement instead of fixing broken code.

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

document

Generate or update documentation for code, APIs, or systems

explain

Explain code, concepts, or technical decisions in clear, understandable terms

fix

Debug and fix bugs, errors, or unexpected behavior

legacy-code-safety

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

optimize

Optimize code for performance, readability, or efficiency

orthogonality-principle

Use when designing modules, APIs, and system architecture requiring independent, non-overlapping components where changes in one don't affect others.

plan

Create tactical implementation plan for a feature or task

professional-honesty

Use when responding to questions or providing information requiring professional honesty and directness over excessive agreeableness.

project-memory

Use when setting up or organizing Claude Code project memory (CLAUDE.md, .claude/rules/) for better context awareness, consistent behavior, and project-specific instructions.

proof-of-work

Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.

refactor

Restructure code to improve quality without changing behavior

review

Multi-agent code review with confidence-based filtering

simplicity-principles

Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.

solid-principles

Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.

structural-design-principles

Use when designing modules and components requiring Composition Over Inheritance, Law of Demeter, Tell Don't Ask, and Encapsulation principles that transcend programming paradigms.

test

Write tests for code using test-driven development principles

git-storytelling-commit-strategy

Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.

create-sop

Create a new Standard Operating Procedure (SOP) file with proper structure

update-sop

Update an existing SOP to reflect changes in tools, processes, or best practices

comment

Add a comment to a ClickUp task

complete

Mark a ClickUp task as complete after validating checklist

create

Create a new ClickUp task interactively