ruby-skills for rails

Rails conventions,
built into your
coding agent.

Stop re-explaining your stack on every project. Ruby Skills packages Rails engineering knowledge into installable, versioned context your agent actually uses.

gem install ruby-skills

Coming soon — follow development on GitHub

The problem

Your agent doesn't know your Rails app.

And no matter how good the model is, it can't guess your stack, your patterns, or your team's conventions.

Every chat starts from scratch

You spend the first few minutes re-explaining your stack, your gem choices, and your team conventions. Every. Single. Session.

Generic Ruby, not idiomatic Rails

Your agent generates code that works in Ruby but misses Rails conventions — wrong abstractions, wrong patterns, wrong idioms for your version.

No shared setup across the team

Every developer maintains their own system prompts. No standard, no version control, no single source of truth. Ten engineers, ten different agent setups.

Example catalog

This is the shape of a Rails skill catalog.

Names below are fictional examples — not official Rails, RSpec, or gem-maintainer skills. They show how a catalog could look once the registry exists.

example/rails-conventions

Routing, naming, generators, MVC conventions, and Rails 8 patterns

Example
example/secure-defaults

Strong parameters, CSRF, CSP, secure headers, and mass assignment protection

Example
example/request-specs

RSpec + factory_bot conventions, request specs, coverage setup

Example
example/job-queues

Background jobs, idempotency, retries, dead queues, and queue naming

Example
example/hotwire-ui

Turbo Streams, Turbo Frames, Stimulus patterns, and morphing conventions

Concept
example/auth-flows

Auth flows, token strategy, OmniAuth integration, and session management

Concept
In your project

One Skillfile.
All the context.

Drop a Skillfile into the root of your Rails project. Run ruby-skills sync. Your entire team and every supported agent now shares the same engineering context.

  1. 1
    Add a Skillfile to your project root
  2. 2
    Declare the skills your Rails project needs
  3. 3
    Run ruby-skills sync to lock versions
  4. 4
    Commit the Skills.lock with your code
source "https://skills.rubyskills.org"

# Example Skillfile — fictional skills
skill "example/rails-conventions", version: "~> 0.1"
skill "example/secure-defaults",   version: "~> 0.1"
skill "example/request-specs",     version: "~> 0.1"
skill "example/job-queues",        version: "~> 0.1"
$ ruby-skills sync
Resolving skill versions...
✓  example/rails-conventions@0.1.0
✓  example/secure-defaults@0.1.0
✓  example/request-specs@0.1.0
✓  example/job-queues@0.1.0
Skills.lock written — agent ready.
The parallel

Rails made a blog in 15 minutes.
We want 5.

Convention over configuration eliminated boilerplate and made developers productive from day one. Ruby Skills brings the same idea to AI-assisted development — less prompting, more building.

See the full vision
2005
Convention over Configuration
↓ less configuration ↓
Blog in 15 minutes
2026
Convention + Engineering Context
↓ less prompting ↓
Blog in 5 minutes

Stop explaining your Rails
stack from scratch.

Join the early access list and be the first to add ruby-skills to your Rails projects.