generating-rbs
Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
Best use case
generating-rbs is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "generating-rbs" skill to help with this workflow task. Context: Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/generating-rbs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How generating-rbs Compares
| Feature / Agent | generating-rbs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generates RBS type signatures from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbs files for classes/modules without existing RBS signatures.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# RBS Generate Skill Generate pure RBS signatures for Ruby source files from scratch. Does not handle RBS-inline signatures or updates for existing signatures. # Instructions When generating RBS signatures from scratch, always follow these steps. Copy this checklist and track your progress: ``` RBS Generation Progress: - [ ] Step 1: Analyze the Ruby source - [ ] Step 2: Generate RBS signatures - [ ] Step 3: Eliminate `untyped` types in generated signatures - [ ] Step 4: Review and refine RBS signatures - [ ] Step 5: Validate shape of RBS signatures - [ ] Step 6: Ensure type safety (only if steep is configured) ``` ## Rules There are several rules that you MUST follow while performing this skill: - 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. ## 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. Generate RBS Signatures Always perform this step. - Create necessary `.rbs` files for the target Ruby file. - Place generated RBS files in `sig/` directory mirroring Ruby source structure. - You need to strongly follow RBS syntax conventions to describe types for all declarations - See [syntax.md](reference/syntax.md) for the full list of RBS types. Double-check it in tricky cases. - Take inspiration from RBS signature examples - See [rbs_by_example.md](reference/rbs_by_example.md) for short list of RBS signatures examples - See [core](reference/rbs_examples/core/STRUCTURE.md) for RBS signatures of Ruby core library - See [stdlib](reference/rbs_examples/stdlib/STRUCTURE.md) for RBS signatures of Ruby standard library - Pay extra attention to `Data` and `Struct` types. See [data_and_struct.md](reference/data_and_struct.md) for handling guide - See [gem_rbs_collection](https://github.com/ruby/gem_rbs_collection/tree/main/gems) for RBS signature examples of different Ruby libraries. This link contains only RBS files, Ruby sources are not included. ## 3. Eliminate `untyped` types in generated signatures Always perform this step. - Go through all generated signatures and replace `untyped` with the proper type. - Use assumptions and calls examples in Ruby code and tests to infer the proper type. - If you cannot infer the proper type, leave it as `untyped`. - It is a last resort, use it only when there is no other option. ## 4. Review and refine RBS signatures Always perform this step. - Take a look at the generated signatures and make sure they are correct, coherent and complete. - Try to get rid of any unnecessary `untyped` types. - If you find any errors, please fix them and repeat the process until there are no errors. ## 5. Validate shape of RBS signatures Always perform this step. - Run `rbs validate` to verify that existing and new `.rbs` files are internally consistent. It will check syntax, name resolution, inheritance, method overloading, type variables, etc. - Fix any errors reported by `rbs validate` and repeat the process until there are no errors. ## 6. Ensure type safety of RBS signatures Perform this step ONLY if the project Gemfile includes `steep` gem AND the project has Steepfile. - Run `steep check` to verify that generated RBS signatures are type safe. - Fix any errors reported by `steep check` and repeat the process until there are no errors. - Do not modify Steepfile in an attempt to fix errors. - Roll back to step 4 if you fixed any errors reported by `steep check`. # References - [syntax.md](reference/syntax.md) - The full list of RBS types and syntax - [rbs_by_example.md](reference/rbs_by_example.md) - Short list of RBS signatures examples - [core](reference/rbs_examples/core/STRUCTURE.md) - RBS signatures of Ruby core library - [stdlib](reference/rbs_examples/stdlib/STRUCTURE.md) - RBS signatures of Ruby standard library - [data_and_struct.md](reference/data_and_struct.md) - Explanation on `Data` and `Struct` types handling
Related Skills
generating-solana-projects
Generates complete Solana blockchain projects with Anchor framework (v0.32.1) and Next.js frontend including Rust smart contracts, tests, and wallet integration. Use when creating Solana dApps, NFT marketplaces, token programs, DAOs, DeFi protocols, or when user mentions Solana, Anchor, or blockchain projects.
generating-output-styles
Creates custom output styles for Claude Code that modify system prompts and behavior. Use when the user asks to create output styles, customize Claude's response format, generate output-style files, or mentions output style configuration.
generating-sorbet
Generates Sorbet type signatures in separate RBI files from Ruby source files. Triggers when creating type definitions, adding types to Ruby code, or generating .rbi files for classes/modules without existing Sorbet signatures.
generating-sorbet-inline
Generates Sorbet inline type signatures using sig blocks directly in Ruby source files. Triggers when adding Sorbet types, annotating Ruby methods with sig syntax, or generating type signatures for Sorbet-typed projects.
generating-rbs-inline
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.
azure-quotas
Check/manage Azure quotas and usage across providers. For deployment planning, capacity validation, region selection. WHEN: "check quotas", "service limits", "current usage", "request quota increase", "quota exceeded", "validate capacity", "regional availability", "provisioning limits", "vCPU limit", "how many vCPUs available in my subscription".
raindrop-io
Manage Raindrop.io bookmarks with AI assistance. Save and organize bookmarks, search your collection, manage reading lists, and organize research materials. Use when working with bookmarks, web research, reading lists, or when user mentions Raindrop.io.
zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式,自动转换,一键创建知识库。
discover-skills
当你发现当前可用的技能都不够合适(或用户明确要求你寻找技能)时使用。本技能会基于任务目标和约束,给出一份精简的候选技能清单,帮助你选出最适配当前任务的技能。
web-performance-seo
Fix PageSpeed Insights/Lighthouse accessibility "!" errors caused by contrast audit failures (CSS filters, OKLCH/OKLAB, low opacity, gradient text, image backgrounds). Use for accessibility-driven SEO/performance debugging and remediation.
project-to-obsidian
将代码项目转换为 Obsidian 知识库。当用户提到 obsidian、项目文档、知识库、分析项目、转换项目 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入规则(默认到 00_Inbox/AI/、追加式、统一 Schema) 3. 执行 STEP 0: 使用 AskUserQuestion 询问用户确认 4. 用户确认后才开始 STEP 1 项目扫描 5. 严格按 STEP 0 → 1 → 2 → 3 → 4 顺序执行 【禁止行为】: - 禁止不读 SKILL.md 就开始分析项目 - 禁止跳过 STEP 0 用户确认 - 禁止直接在 30_Resources 创建(先到 00_Inbox/AI/) - 禁止自作主张决定输出位置
obsidian-helper
Obsidian 智能笔记助手。当用户提到 obsidian、日记、笔记、知识库、capture、review 时激活。 【激活后必须执行】: 1. 先完整阅读本 SKILL.md 文件 2. 理解 AI 写入三条硬规矩(00_Inbox/AI/、追加式、白名单字段) 3. 按 STEP 0 → STEP 1 → ... 顺序执行 4. 不要跳过任何步骤,不要自作主张 【禁止行为】: - 禁止不读 SKILL.md 就开始工作 - 禁止跳过用户确认步骤 - 禁止在非 00_Inbox/AI/ 位置创建新笔记(除非用户明确指定)