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
Use this skill when registering external dependencies (database, mailer, cache, third-party APIs) in the Hanami 2.x DI container.
Core principle: Providers bridge external libraries into the DI container. They handle initialization, configuration, and lifecycle.
| Scenario | Approach |
|---|---|
| Create a provider | bundle exec hanami generate provider <name> |
| Register a database | Use the built-in database provider or custom provider |
| Register a mailer | Create config/providers/mailer.rb |
| Register a cache | Create config/providers/cache.rb |
| Register a third-party API client | Create config/providers/<service>.rb |
| Access the provided component | include Deps["<provider_name>.<component>"] |
| Configure the provider | Use the prepare and start lifecycle hooks |
Generate a provider using the Hanami CLI:
hanami generate provider mailerThis creates config/providers/mailer.rb.
Implement the provider using lifecycle hooks:
Use prepare for requiring dependencies and start for component initialization. Keep providers focused on a single external dependency or library.
# config/providers/mailer.rb
# frozen_string_literal: true
Hanami.app.register_provider(:mailer) do
prepare do
require "mail"
end
start do
client = Mail.new do
delivery_method :smtp, {
address: target[:settings].smtp_host,
port: target[:settings].smtp_port
}
end
register("mailer.client", client)
end
endAccess provided components via Deps:
# app/mailers/welcome.rb
module MyApp
module Mailers
class Welcome
include Deps["mailer.client"]
def deliver(user)
client.deliver do
to user.email
subject "Welcome!"
end
end
end
end
endUse the built-in database provider: The ROM container is automatically registered at boot by the framework:
include Deps["db.rom"]Register third-party API clients using settings:
Always load keys and URLs through target[:settings]. Do not reference raw environment variables via ENV in providers.
# config/providers/logger.rb
Hanami.app.register_provider(:logger) do
start do
require "logger"
logger = Logger.new(target[:settings].log_file)
register("logger.client", logger)
end
endTest components that depend on providers by stubbing the provided dependency:
stub_mailer = double("mailer", deliver: true)
welcome = MyApp::Mailers::Welcome.new(mailer__client: stub_mailer)Verify a provider is correctly registered using the Hanami console or a smoke test:
[WARNING] Rescue and log errors in
start. A failed provider should not crash the app boot.
# In `hanami console`
Hanami.app["mailer.client"] # => returns the registered instance
Hanami.app["logger.client"] # => returns LoggerFor a lightweight smoke test in specs:
it "registers the mailer client" do
expect(Hanami.app["mailer.client"]).to be_a(Mail::Message)
end| Related Skill | When to chain |
|---|---|
| inject-dependencies | Provided components are injected via Deps[]. Understand Deps before writing providers. |
| manage-settings | Providers read configuration from target[:settings]. Define settings before writing providers. |
| create-action | Actions inject provided services via Deps[]. |
| create-repository | The database provider registers ROM, which Repositories depend on. |
| integrate-api-client | Complex API clients may need a dedicated skill for auth/patterns. |
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