Skill UI

This skill applies Refactoring.Guru-inspired rules for diagnosing code smells and selecting appropriate refactoring techniques. It helps preserve behavior while avoiding uncontrolled redesign. Before making design or code decisions, read the mini rules first. Use the full guide only as a deeper reference when needed. It ensures targeted cleanup without over-engineering.

Apply Michael T. Nygard-inspired production reliability rules when designing failure handling, timeouts, retries, circuit breakers, observability, or deployment behavior.

This skill helps maintainers verify reported bugs in the mcp-toolbox project. It involves analyzing issue reports, checking versions and configurations, and attempting local reproduction to determine if the bug is real, fixed, or misconfigured. The process requires citing specific evidence like file paths and commit SHAs to support verdicts such as confirmed, already-fixed, or client-side issues. It ensures efficient bug triage without unnecessary infrastructure setup.

Sweeps googleapis/mcp-toolbox for issues and PRs with no real activity in N days, classifies each silence as the author's, maintainer's, or nobody's, and drafts nudge or close comments for maintainer review only.

Apply pragmatic programming rules inspired by Hunt and Thomas to improve engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, and adaptability. Use this skill for design and code decisions requiring pragmatic engineering tradeoffs.

This skill extracts a checklist from planned work, builds the implementation, and verifies every check with an independent verifier. It is used when the user requests to extract a checklist, build a ticket, or implement a spec. It ensures rigorous testing and proof-based assertions, preventing self-reporting of completion. It involves extracting checks, building the code, and proving each one independently to guarantee quality.

This skill implements a spec-driven feature workflow that freezes obligations before coding. It involves creating a human-reviewed plan with EARS criteria, defining checks with proof-backed tests, building the feature, and verifying with an independent agent. It ensures correctness over task breakdown and prevents requirement drift. Use for feature specification and verification, not standalone design docs.

Apply Michael Feathers-inspired rules to safely modify hard-to-test legacy code using characterization tests, seams, sprout methods, or wrap methods. Ideal for risky changes, missing tests, dependency breaking, and incremental risk reduction in software maintenance.

This skill covers essential framework patterns for modern Ruby on Rails applications (Rails 7.1+ and 8.x). It includes directory contracts, skinny controllers, service objects, form objects, query objects, background jobs, ViewComponent, Hotwire, and the Rails 8 Solid stack. Use this when building or reviewing Rails apps, controllers, models, services, jobs, or views to ensure maintainability and best practices.