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
# config/contracts/predicates.rb
require "dry/validation"
Dry::Validation.register_macro(:email_format) do
key.failure("must be a valid email") unless value.match?(URI::MailTo::EMAIL_REGEXP)
end
# Usage
rule(:email) { key.email_format }class OrderContract < Dry::Validation::Contract
schema do
required(:customer).hash do
required(:name).filled(:string)
required(:email).filled(:string)
end
required(:items).array(:hash) do
required(:product_id).filled(:integer)
required(:quantity).filled(:integer, gt?: 0)
end
end
endmodule Shared
class PaginationContract < Dry::Validation::Contract
schema do
optional(:page).filled(:integer, gt?: 0)
optional(:per_page).filled(:integer, gt?: 0, lteq?: 100)
end
end
end
class Users::IndexContract < Dry::Validation::Contract
# Compose shared contracts
config.messages.namespace = :users
schema do
optional(:role).filled(:string)
end
# Merge pagination schema
schema do
import(Shared::PaginationContract.schema)
end
endRSpec.describe Users::CreateContract do
subject(:contract) { described_class.new }
context "with valid input" do
let(:input) { { email: "test@example.com", name: "Test User" } }
it "is valid" do
expect(contract.call(input)).to be_success
end
end
context "with missing email" do
let(:input) { { name: "Test User" } }
it "has error on email" do
result = contract.call(input)
expect(result).to be_failure
expect(result.errors.to_h).to include(email: ["is missing"])
end
end
context "with invalid email" do
let(:input) { { email: "not-an-email", name: "Test" } }
it "has email format error" do
result = contract.call(input)
expect(result.errors.to_h).to include(email: ["must be a valid 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