skills/dmitrypogrebnoy/generating-rbs-inline/SKILL.md
Generates RBS-inline type annotations directly in Ruby source files as comments. Triggers when adding inline type signatures, annotating Ruby methods with rbs-inline syntax, or generating type comments without existing inline annotations.
npx skillsauth add aiskillstore/marketplace generating-rbs-inlineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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)
untyped. Infer the proper type instead.bundle exec if the project has Gemfile.# @rbs comment syntax for inline annotations..rbs files in the project.Always perform this step.
Read and understand the Ruby source file:
public, private, protected.Always perform this step.
First, add the magic comment at the top of the Ruby file to enable rbs-inline processing:
# rbs_inline: enabled
Then add type annotations as comments directly in the Ruby source file using rbs-inline syntax:
Example - Before:
class User
attr_reader :name, :age
def initialize(name, age)
@name = name
@age = age
end
def greet(greeting)
"#{greeting}, #{@name}!"
end
end
Example - After:
# rbs_inline: enabled
class User
attr_reader :name #: String
attr_reader :age #: Integer
# @rbs name: String
# @rbs age: Integer
# @rbs return: void
def initialize(name, age)
@name = name
@age = age
end
#: (String) -> String
def greet(greeting)
"#{greeting}, #{@name}!"
end
end
Data and Struct types
untyped Types in AnnotationsAlways perform this step.
untyped with proper types.untyped only as a last resort when type cannot be determined.Always perform this step.
untyped types.Always perform this step.
rbs-inline is a transpiler - it generates RBS files from inline annotations. Validation happens on the generated RBS output.
Generate RBS files from annotations:
rbs-inline --output lib
This generates .rbs files in sig/generated/ directory.
Validate the generated RBS files:
rbs validate
This checks syntax, name resolution, inheritance, and type applications.
Fix any errors in your inline annotations and repeat until validation passes.
Perform this step ONLY if the project Gemfile includes steep gem AND the project has Steepfile.
Steep works on RBS files, not directly on inline annotations. The RBS files must be generated first (step 5).
Ensure RBS files are generated from annotations:
rbs-inline --output lib
Run Steep type checker:
steep check
Fix any errors reported by steep check.
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.