Curated library of atomic AI agent skills for Hanami, dry-rb, and ROM Ruby development. Covers actions, slices, repositories, relations, changesets, providers, DI, operations, TDD, CLI, views, routing, and validation. Shared Ruby process skills have moved to ruby-core-skills. Uses Markdown + Front-matter architecture.
92
94%
Does it follow best practices?
Impact
92%
1.33xAverage score across 35 eval scenarios
Passed
No known issues
Hanami actions and operations receive dependencies through the constructor. In tests, pass test doubles:
# spec/slices/api/actions/users/create_spec.rb
RSpec.describe Api::Actions::Users::Create do
let(:create_user) { instance_double(Users::CreateUser) }
let(:action) { described_class.new(create_user:) }
context "with valid params" do
let(:user) { User.new(id: 1, email: "test@example.com") }
before do
allow(create_user).to receive(:call).and_return(Dry::Monads::Success(user))
end
it "returns 201 with user data" do
response = action.call("email" => "test@example.com")
expect(response.status).to eq(201)
end
end
context "with invalid params" do
before do
allow(create_user).to receive(:call)
.and_return(Dry::Monads::Failure(email: ["is invalid"]))
end
it "returns 422 with errors" do
response = action.call("email" => "invalid")
expect(response.status).to eq(422)
end
end
end# spec/slices/api/operations/users/create_user_spec.rb
RSpec.describe Users::CreateUser do
let(:user_repo) { instance_double(Api::Repositories::UserRepo) }
let(:send_welcome) { instance_double(Notifications::SendWelcome) }
let(:operation) { described_class.new(user_repo:, send_welcome:) }
it "persists the user and sends welcome notification" do
allow(user_repo).to receive(:create).and_return(user)
allow(send_welcome).to receive(:call).and_return(Dry::Monads::Success(true))
result = operation.call(email: "test@example.com", name: "Test")
expect(result).to be_success
expect(user_repo).to have_received(:create).with(email: "test@example.com", name: "Test")
expect(send_welcome).to have_received(:call).with(user)
end
end| Consumer | Typical Deps |
|---|---|
| Action | One operation, sometimes a repository for reads |
| Operation | Repositories, other operations, external service clients |
| Repository | None — auto-registered by ROM |
| View | Repositories for read-only data, presentation helpers |
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
skills
actions
build-json-api
create-action
handle-errors
validate-params
context
load-context
db
create-changeset
create-repository
define-relation
write-migration
dry-monads
handle-result-pattern
dry-rb
create-operation
create-validation-contract
providers
configure-providers
implement-di
review-security
routing
define-routes
slices
configure-slice
create-slice
extract-slice
review-slice-boundaries
test-slice