generating-sorbet-inlinelisted

# Sorbet Inline Generation Skill Generate Sorbet type signatures using `sig {}` blocks directly in Ruby source files. Sorbet signatures are valid Ruby code that enable both static and runtime type checking. # Instructions When generating Sorbet inline signatures, always follow these steps. Copy this checklist and track your progress: ``` Sorbet Inline Generation Progress: - [ ] Step 1: Analyze the Ruby source - [ ] Step 2: Add Sorbet signatures - [ ] Step 3: Eliminate `T.untyped` in signatures - [ ] Step 4: Review and refine signatures - [ ] Step 5: Validate signatures with Sorbet ``` ## Rules - You MUST NOT run Ruby code of the project. - You MUST NOT use `T.untyped`. Infer the proper type instead. - You MUST NOT use `T.unsafe` - it bypasses type checking entirely. - You MUST NOT use `T.cast` - it forces types without verification. - 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 `sig { }` block syntax for method signatures. - You MUST add `extend T::Sig` to classes/modules before using `sig`. - You MUST focus on method signatures only. Skip local variables, intermediate expressions, and other non-method annotations. - You MUST NOT use or generate `.rbi` files. This skill is for inline signatures only. - You MUST preserve the existing `# typed:` sigil level if one exists. Do not upgrade or change strictness without explicit user consent. ## 1. Analyz