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
Conventions and structure for every SKILL.md in this library.
hanakai-yaku/
├── docs/ # Documentation
│ ├── architecture.md
│ ├── agent-guide.md
│ ├── calling-skills.md
│ └── reference/
│ ├── skill-catalog.md
│ └── integration-matrix.md
├── agents/ # Orchestrated agent skills
│ └── hanami-setup/
│ └── SKILL.md
├── skills/ # Categorized skills
│ └── <category>/ # e.g., context, providers, actions
│ └── <skill-name>/ # One directory per skill
│ ├── SKILL.md # Main skill file (required)
│ └── reference.md # Optional companion material
├── SKILL.md # Root orchestrator
├── CONTEXT.md # Domain glossary
├── AGENTS.md # Agent guidance
├── tile.json # Skill registry
├── agents.json # Agent registry
└── README.mdEvery skill follows 6 sections in order:
1. Frontmatter (YAML) — name, description, metadata
2. Quick Reference — scannable for fast lookup
3. HARD-GATE — non-negotiable blocking rules
4. Core Process — step-by-step procedure
5. Output Style — exact shape of artifacts
6. Integration — predecessor/successor skills---
name: skill-name
license: MIT
description: >
Use when [concrete trigger conditions]. Covers [key topics].
Trigger words: comma, separated, discovery, terms.
metadata:
version: 1.0.0
user-invocable: "true"
---Rules:
name equals directory name (kebab-case).description starts with action-oriented trigger language.For code-producing skills, the gate is always:
Write test → Run test → Verify it FAILS → Implement → Verify it PASSESNon-code skills have domain-specific gates.
| Context | Format | Example |
|---|---|---|
tile.json and agents.json | Full path | skills/context/load-context/SKILL.md |
| Agent body (activate calls) | Category-path | context/load-context |
| Integration tables | Short name | load-context |
Load and discover. Do not produce code.
load-contextSet up infrastructure. Produce configuration files.
configure-providersimplement-diFollow TDD gate. Produce implementation code.
create-action, create-repository, create-operation, etc.Defined in: load-context, hanami-setup. Context must be discovered before any code.
Defined in: configure-providers, hanami-setup. All providers must boot without errors.
Defined in: All code-producing skills. Test must exist, run, and fail before implementation.
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