How does this skill handle Ruby type checking?

It implements a parallel directory structure where RBS files in the sig/ folder define types for source code in lib/, using Steep to perform static analysis and ensure type consistency.

Is rbenv required for this skill?

The skill assumes the use of rbenv for Ruby version management and looks for a .ruby-version file to ensure environment consistency across development teams.

Does it include code style enforcement?

Yes, it uses Rubocop with auto-fix enabled, enforcing a 120-character line limit, specific block syntaxes, and method lengths under 10 lines for better readability.

What testing frameworks are supported?

The skill specifically configures RSpec for unit and integration testing, requiring describe/context blocks and a minimum of 80% code coverage tracked by SimpleCov.

Ruby 3.2 with RBS & Steep

Name: Ruby 3.2 with RBS & Steep
Author: kreuzberg-dev

bykreuzberg-dev

•

480

Developer Tools

Implements type-safe Ruby 3.2 development patterns using RBS type definitions, Steep checking, and rigorous testing standards.

About

This skill optimizes Claude for modern Ruby 3.2 development, prioritizing type safety and high-quality code architecture. It enforces the use of RBS for type definitions within a dedicated sig/ directory and utilizes Steep for static type analysis to minimize runtime errors. Beyond typing, the skill establishes strict standards for testing with RSpec, linting with Rubocop, and project management using rbenv, ensuring that Ruby projects are maintainable, performant, and follow the latest industry best practices for modular design.

Key Features

Steep type checking configuration to avoid 'Any' types
480 GitHub stars
Standardized naming conventions and modular code architecture patterns
Comprehensive RSpec testing standards with 80%+ coverage requirements
Integration of RBS type definitions for robust static analysis
Automated linting and formatting via Rubocop with specific style rules

Use Cases

Migrating legacy Ruby projects to a type-safe Ruby 3.2 environment
Implementing complex value objects and mixins using Dry::Struct and RBS
Bootstrapping new Ruby services with built-in CI/CD quality gates

About

Key Features

Steep type checking configuration to avoid 'Any' types
480 GitHub stars
Standardized naming conventions and modular code architecture patterns
Comprehensive RSpec testing standards with 80%+ coverage requirements
Integration of RBS type definitions for robust static analysis
Automated linting and formatting via Rubocop with specific style rules

Use Cases

Migrating legacy Ruby projects to a type-safe Ruby 3.2 environment
Implementing complex value objects and mixins using Dry::Struct and RBS
Bootstrapping new Ruby services with built-in CI/CD quality gates