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
module Orders
class PlaceOrder < Dry::Operation
include Deps["repositories.order_repo", "repositories.inventory_repo"]
def call(input)
attrs = step validate(input)
order = step persist(attrs)
step reserve_inventory(order)
step notify(order)
order
end
private
def validate(input)
contract = OrderContract.new
result = contract.call(input)
result.success? ? Success(result.to_h) : Failure(result.errors.to_h)
end
def persist(attrs) = Success(order_repo.create(attrs))
def reserve_inventory(order) = # ...
def notify(order) = # ...
end
endmodule Payments
class ProcessPayment < Dry::Transaction
include Deps["repositories.payment_repo", "repositories.ledger_repo"]
map :validate
tee :log_attempt
step :charge
step :record
step :notify
private
def validate(input) = # ...
def log_attempt(input) = # ... (tee: runs but doesn't affect flow)
def charge(input) = # ...
def record(input) = # ...
def notify(input) = # ...
end
endUse dry-transaction when you need:
tee stepsUse dry-operation when you need:
Operations return Failure — never raise exceptions for business errors:
# Good
def charge(amount)
response = payment_gateway.charge(amount)
response.success? ? Success(response) : Failure(payment_failed: response.error)
end
# Bad
def charge(amount)
payment_gateway.charge!(amount) # raises on failure
endRSpec.describe Users::CreateUser do
let(:user_repo) { instance_double(Api::Repositories::UserRepo) }
let(:operation) { described_class.new(user_repo:) }
context "with valid input" do
before { allow(user_repo).to receive(:create).and_return(user) }
it "returns Success with the user" do
result = operation.call(email: "test@example.com")
expect(result).to be_success
expect(result.value!).to eq(user)
end
end
context "with invalid input" do
it "returns Failure with errors" do
result = operation.call(email: "invalid")
expect(result).to be_failure
expect(result.failure).to include(:email)
end
end
enddocs
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