Curated library of atomic skills and personas for Hanami, dry-rb, and ROM Ruby development. Covers actions, slices, repositories, relations, changesets, providers, DI, operations, TDD, CLI, views, routing, validation, and 10 orchestration personas. Shared Ruby process skills have moved to ruby-core-skills. Uses Markdown + Front-matter architecture.
95
95%
Does it follow best practices?
Impact
96%
1.20xAverage score across 45 eval scenarios
Passed
No known issues
Use this workflow when implementing any Hanami 2.x feature using Test-Driven Development.
Core principle: Write a failing test → verify it fails for the right reason → implement → verify it passes → review.
| Step | Skill | Handoff Condition |
|---|---|---|
| 1. Plan tests | test-planning-process (from ruby-core-skills) | Test plan written, right test type chosen |
| 2. Write failing test | write-request-spec or write-action-spec | Test exists and fails for the right reason |
| 3. Implement | — | Test passes |
| 4. Review | review-code | No violations found |
[Plan Tests] — Load skill: test-planning-process (from ruby-core-skills)
[Write Failing Test] — Load skill: write-request-spec or write-action-spec
bundle exec rspec spec/requests/... (request spec) or bundle exec rspec spec/actions/... (action spec)tdd-process (from ruby-core-skills)): Do not proceed until the test fails for the right reason.[Implement] — Write minimal code to make the test pass
bundle exec rspec after each change[Review] — Load skill: review-code
Failing request spec (spec/requests/posts/create_spec.rb):
RSpec.describe "POST /posts", type: :request do
it "creates a post and redirects" do
post "/posts", params: { post: { title: "Hello" } }
expect(last_response.status).to eq(302)
end
endRun: bundle exec rspec spec/requests/posts/create_spec.rb → expect a failure such as ActionNotFound or 404.
Minimal implementation — generate the action and register the route:
# app/actions/posts/create.rb
module MyApp
module Actions
module Posts
class Create < MyApp::Action
def handle(request, response)
response.redirect_to "/posts"
end
end
end
end
endRun: bundle exec rspec spec/requests/posts/create_spec.rb → expect green.
| Mistake / Red Flag | Why it matters |
|---|---|
| Implementation written before any test | TDD means test first. No exceptions. |
| Skipping the HARD-GATE — assuming the test fails without running it | A passing test without running it first doesn't verify the assertion works — run it to confirm RED |
.tessl-plugin
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
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
scenario-45
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
personas
providers
configure-providers
implement-di
review-security
routing
define-routes
slices
configure-slice
create-slice
extract-slice
review-slice-boundaries
test-slice