CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/hanakai-yaku

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

1.20x
Quality

95%

Does it follow best practices?

Impact

96%

1.20x

Average score across 45 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-41/

Write Request Spec Task

Problem

A Hanami team needs help with a task in this area:

Write failing RSpec request spec first then use create-action to implement — place at spec/requests/ with type: :request, send JSON bodies with .to_json + CONTENT_TYPE: application/json, assert via last_response.status + json_body, confirm spec fails because action is unimplemented (not syntax error), test 404/422 error shapes, wrap DB specs in "db transaction" with ROM rollback.

The team has asked for a concise implementation artifact that a reviewer can inspect without needing to observe the agent's process.

Output

Create answer.md with:

  • a short plan for the work
  • the concrete Hanami-oriented artifact or recommendation
  • the verification steps or quality gates that should be run
  • any assumptions that affect the result

README.md

tile.json