generating-rbs-inlinelisted

# RBS-Inline Generation Skill Generate RBS-inline type annotations as comments directly in Ruby source files. Unlike pure RBS which uses separate `.rbs` files, rbs-inline embeds type information as structured comments within Ruby code. # Instructions When generating RBS-inline annotations, always follow these steps. Copy this checklist and track your progress: ``` RBS-Inline Generation Progress: - [ ] Step 1: Analyze the Ruby source - [ ] Step 2: Add RBS-inline annotations - [ ] Step 3: Eliminate `untyped` types in annotations - [ ] Step 4: Review and refine annotations - [ ] Step 5: Validate annotations - [ ] Step 6: Ensure type safety (only if steep is configured) ``` ## Rules - You MUST NOT run Ruby code of the project. - You MUST NOT use `untyped`. Infer the proper type instead. - You MUST ask the user to provide more details if something is not clear. - You MUST prepend any command with `bundle exec` if the project has Gemfile. - You MUST use `# @rbs` comment syntax for inline annotations. - You MUST NOT use regular RBS signatures and `.rbs` files in the project. ## 1. Analyze the Ruby Source Always perform this step. Read and understand the Ruby source file: - Identify all classes, modules, methods, constants and instance variables. - Note inheritance, module inclusion and definitions based on metaprogramming. - Note visibility modifiers - `public`, `private`, `protected`. - Note type parameters for generic classes. ## 2. Add RBS-Inline Annotations Always pe