Run any Skill in Manus with one click

run-development

Stars0

Forks0

UpdatedJune 2, 2026 at 01:04

Use when running Hanami 2.x development commands — `hanami dev` with code reloading though config files require server restart, verify server responds via `curl http://localhost:2300` and recover from port conflicts and config syntax errors, `hanami console` requiring DATABASE_URL set with HANAMI_ENV awareness before destructive operations, using the container to explore slices/relations/repos, and `hanami routes`/`hanami middleware` for stack inspection. Covers hanami dev (starting the development server with code reloading), hanami console (REPL with full container loaded for exploring the app, accessing slices, inspecting registered components, querying relations, and testing repository methods), hanami routes (listing all routes), and hanami middleware (inspecting the middleware stack).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

igmarin

igmarin/hanakai-yaku

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	run-development
license	MIT
type	atomic
description	Use when running Hanami 2.x development commands — `hanami dev` with code reloading though config files require server restart, verify server responds via `curl http://localhost:2300` and recover from port conflicts and config syntax errors, `hanami console` requiring DATABASE_URL set with HANAMI_ENV awareness before destructive operations, using the container to explore slices/relations/repos, and `hanami routes`/`hanami middleware` for stack inspection. Covers hanami dev (starting the development server with code reloading), hanami console (REPL with full container loaded for exploring the app, accessing slices, inspecting registered components, querying relations, and testing repository methods), hanami routes (listing all routes), and hanami middleware (inspecting the middleware stack).
metadata	{"version":"1.0.0","ecosystem_sources":["hanami/hanami-cli"],"tags":["cli","development","server","console"]}

run-development

Use this skill when running Hanami 2.x development commands.

Quick Reference

Command	Purpose
`hanami dev`	Start development server with code reloading
`hanami console`	Start interactive REPL with full container loaded
`hanami routes`	List all routes
`hanami middleware`	List middleware stack
`hanami version`	Show Hanami version

Core Rules

Start the development server:
```
hanami dev
```
Verify: Once started, confirm the server is responding:
```
curl http://localhost:2300
```
Error recovery:
- Port already in use: lsof -ti:2300 | xargs kill -9 or change port in config/app.rb
- Server fails to start: Check config/app.rb and config/routes.rb for syntax errors
- Does not reload configuration files (requires restart after editing config/app.rb or config/routes.rb)
Start the console:

Before starting, ensure DATABASE_URL is set if your app uses a database:
```
echo $DATABASE_URL
```
Then start the console:
```
hanami console
```
Uses development environment by default; override with HANAMI_ENV=test hanami console.

Access components directly:
```
app = Hanami.app
rom = app["db.rom"]
users = rom.relations[:users]
users.insert(email: "test@example.com")
```
Error recovery:
- Database connection refused: Verify DATABASE_URL is set and database server is running
- Boot errors: Check config/providers/ for missing dependencies or configuration issues

Use the console for exploration:

# Query the database
Hanami.app["db.rom"].relations[:users].to_a

# Access a Repository
Hanami.app["repos.user_repo"].all

# Access settings
Hanami.app[:settings].database_url

# Test a Relation query
Hanami.app["relations.users"].active.to_a

List routes and middleware:
```
hanami routes
hanami middleware
```

Common Mistakes

Config files don't reload: hanami dev reloads Ruby code only. Restart the server after editing configuration files.
Environment awareness: Always verify HANAMI_ENV before running destructive operations in the console — it defaults to development but is easy to misconfigure.

Integration

Related Skill	When to chain
create-app	Development commands are used after creating the app.
manage-database	Database commands may be needed before starting the dev server.

More from this repository

same repository

hanakai-yaku

igmarin/hanakai-yaku

Master orchestrator for hanakai-yaku, a curated library of 35 atomic skills and 10 personas for Hanami, dry-rb, and ROM Ruby development. Covers actions, slices, repositories, relations, providers, DI, CLI, testing, views, routing, and TDD automation. Enforces Hanami conventions and TDD discipline. hanami, dry-rb, rom, ruby, tdd, slices, repositories, operations, providers, di, actions, views, routing, cli, testing.

2026-06-120

tdd-loop

igmarin/hanakai-yaku

Use when implementing a Hanami 2.x feature, Hanami action, Hanami slice, or any Hanami controller logic using test-driven development (TDD / red-green-refactor). Orchestrates test planning, generates request specs or action unit specs, drives the implementation of Hanami action classes and route configurations, and performs a final code review. Use when starting a new Hanami feature from scratch, adding integration tests for an existing Hanami action, or following a red-green-refactor cycle for any Hanami 2.x component.

2026-06-020

hanami-setup

igmarin/hanakai-yaku

Orchestrates Hanami project onboarding: loads application context, configures providers, implements dependency injection patterns, and verifies the setup. Use when setting up a new Hanami project, onboarding a developer, configuring services and DI, or wiring up dry-container, dry-system, IoC containers, or Hanami app configuration with providers and dependency injection.

2026-06-020

slice-lifecycle

igmarin/hanakai-yaku

Orchestrates the full Hanami slice lifecycle: creates the slice, tests it in isolation, reviews boundary design, and supports extraction from the app module. Use when building a new Hanami slice, auditing existing slices for bounded context violations, extracting monolithic code into a modular architecture, or enforcing slice generator conventions. Trigger terms: bounded context, Hanami module, modular architecture, slice boundaries, slice extraction, slice generator.

2026-06-020

build-json-api

igmarin/hanakai-yaku

Use when building JSON API endpoints in Hanami 2.x Actions — set `response.format = :json`, use dedicated serializers to encode response bodies, write round-trip serialize→parse tests asserting fields match with `.iso8601` timestamps, include pagination metadata with `{data:, meta:}` shape, return consistent error shapes across endpoints, and rescue `JSON::ParserError` with 400 status. Covers setting content-type headers, serializing Ruby objects to JSON, parsing incoming JSON request bodies, content negotiation, and round-trip parse → serialize → parse verification. Use when you need to render JSON, build a JSON endpoint, create an API controller action, or handle JSON request/response cycles in Hanami 2.x.

2026-06-020

create-action

igmarin/hanakai-yaku

Use when creating, generating, or reviewing Hanami 2.x Action classes (route handlers, request handling, hanami controller equivalents). Generates Action classes with proper handle method signatures, configures dependency injection via Deps[], renders views with exposures, validates params, redirects, returns JSON responses, sets HTTP status codes, and implements halt-based error handling. Use when building a hanami action, wiring a new endpoint, handling params, or structuring request/response logic in a Hanami 2.x app.

2026-06-020

name	run-development
license	MIT
type	atomic
description	Use when running Hanami 2.x development commands — `hanami dev` with code reloading though config files require server restart, verify server responds via `curl http://localhost:2300` and recover from port conflicts and config syntax errors, `hanami console` requiring DATABASE_URL set with HANAMI_ENV awareness before destructive operations, using the container to explore slices/relations/repos, and `hanami routes`/`hanami middleware` for stack inspection. Covers hanami dev (starting the development server with code reloading), hanami console (REPL with full container loaded for exploring the app, accessing slices, inspecting registered components, querying relations, and testing repository methods), hanami routes (listing all routes), and hanami middleware (inspecting the middleware stack).
metadata	{"version":"1.0.0","ecosystem_sources":["hanami/hanami-cli"],"tags":["cli","development","server","console"]}

run-development

Use this skill when running Hanami 2.x development commands.

Quick Reference

Command	Purpose
`hanami dev`	Start development server with code reloading
`hanami console`	Start interactive REPL with full container loaded
`hanami routes`	List all routes
`hanami middleware`	List middleware stack
`hanami version`	Show Hanami version

Core Rules

Start the development server:
```
hanami dev
```
Verify: Once started, confirm the server is responding:
```
curl http://localhost:2300
```
Error recovery:
- Port already in use: lsof -ti:2300 | xargs kill -9 or change port in config/app.rb
- Server fails to start: Check config/app.rb and config/routes.rb for syntax errors
- Does not reload configuration files (requires restart after editing config/app.rb or config/routes.rb)
Start the console:

Before starting, ensure DATABASE_URL is set if your app uses a database:
```
echo $DATABASE_URL
```
Then start the console:
```
hanami console
```
Uses development environment by default; override with HANAMI_ENV=test hanami console.

Access components directly:
```
app = Hanami.app
rom = app["db.rom"]
users = rom.relations[:users]
users.insert(email: "test@example.com")
```
Error recovery:
- Database connection refused: Verify DATABASE_URL is set and database server is running
- Boot errors: Check config/providers/ for missing dependencies or configuration issues

Use the console for exploration:

# Query the database
Hanami.app["db.rom"].relations[:users].to_a

# Access a Repository
Hanami.app["repos.user_repo"].all

# Access settings
Hanami.app[:settings].database_url

# Test a Relation query
Hanami.app["relations.users"].active.to_a

List routes and middleware:
```
hanami routes
hanami middleware
```

Common Mistakes

Config files don't reload: hanami dev reloads Ruby code only. Restart the server after editing configuration files.
Environment awareness: Always verify HANAMI_ENV before running destructive operations in the console — it defaults to development but is easy to misconfigure.

Integration

Related Skill	When to chain
create-app	Development commands are used after creating the app.
manage-database	Database commands may be needed before starting the dev server.