CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/hanakai-yaku

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

1.33x
Quality

94%

Does it follow best practices?

Impact

92%

1.33x

Average score across 35 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

skill-catalog.mddocs/reference/

Skill Catalog — hanakai-yaku

Catalog of Hanami, dry-rb, and ROM development skills. 3 skills and 1 agent available now; 15 skills and 2 agents planned.

Quick Navigation

Skills: load-context · configure-providers · implement-di Agents: hanami-setup

Skills

load-context

| Path | skills/context/load-context/SKILL.md | | Category | Context | | Description | Load Hanami app structure before any code work | | Trigger Words | "load context", "before I code", "what does this app use", "discover structure" |

What it does: Discovers all slices, providers, settings, routes, relations, and established patterns in a Hanami app. The non-negotiable first step before any implementation.

HARD-GATE: Do not propose code without completing load-context.

Next after use: configure-providers (after context, to set up providers) or hanami-setup (first step in onboarding).

configure-providers

| Path | skills/providers/configure-providers/SKILL.md | | Category | Providers | | Description | Configure Hanami providers for services and databases | | Trigger Words | "provider", "configure", "ROM setup", "external service", "register component" |

What it does: Creates provider files for external services, database connections, and application components. Integrates with Hanami settings for environment configuration.

HARD-GATE: Never hardcode credentials. Use settings for all environment values.

Next after use: implement-di (inject the provider into consumers).

implement-di

| Path | skills/providers/implement-di/SKILL.md | | Category | Providers | | Description | Implement dependency injection with dry-system auto_inject | | Trigger Words | "dependency injection", "DI", "auto_inject", "Deps", "inject" |

What it does: Adds include Deps[...] to actions, operations, and repositories. Ensures dependencies are injected through the constructor. Provides testing patterns for DI.

HARD-GATE: Never call the container directly. Always inject through the constructor.

Next after use: Write tests with injected test doubles; proceed to implementation.

Agents

hanami-setup Agent

| Path | agents/hanami-setup/SKILL.md | | Description | Project onboarding lifecycle |

Phases: Context Loading → Provider Configuration → DI Implementation → Verification

Hard Gates: Context Loaded, Providers Verified

Dependencies: load-context, configure-providers, implement-di

Planned (Future Groups)

Skill/AgentCategoryGroup
create-actionActionsGroup 2
test-actionActionsGroup 2
create-repositoryPersistenceGroup 2
create-relationPersistenceGroup 2
create-changesetPersistenceGroup 2
create-operationdry-rbGroup 2
create-validation-contractdry-rbGroup 2
write-testsTestingGroup 2
plan-testsTestingGroup 2
hanami-tdd (agent)AgentsGroup 2
create-sliceSlicesGroup 3
test-sliceSlicesGroup 3
extract-sliceSlicesGroup 3
review-slice-boundariesSlicesGroup 3
create-viewViewsGroup 3
design-routesActionsGroup 3
review-migrationPersistenceGroup 3
slice-lifecycle (agent)AgentsGroup 3

See Also

  • Integration Matrix — How skills chain together
  • Agent Guide — Agent workflows with Mermaid diagrams
  • Architecture — Repository layout and conventions

docs

reference

integration-matrix.md

skill-catalog.md

agent-guide.md

architecture.md

calling-skills.md

index.md

README.md

tile.json