rbs-files

You can add RBS type signatures without modifying source code by placing .rbs files under a sig/ directory. This describes classes, modules, and methods separately, enabling type documentation while keeping Ruby source files untouched.

Standalone Ruby RBS signatures are type definition files that describe method and class types separately from implementation. Use them to progressively adopt static typing in existing Ruby projects or gems without invasive code changes.

Yes, RBS type signatures work with existing Ruby gems and libraries. You write .rbs files under sig/ to describe the gem's classes and methods, maintaining type definitions separately for versioning and cross-project reuse.

Structure RBS signature files by placing them in a sig/ directory next to your lib/ directory, such as sig/person.rbs. Use standard RBS syntax to define classes, modules, and methods, then run RBS tooling to validate against the implementation.

Writing standalone RBS type signatures is an effective approach for progressive static typing adoption in Ruby. By maintaining .rbs files separately from source code, you can introduce type definitions gradually without altering existing implementation logic.