How do I install the Run Development skill?

Run npx skillmds@latest add igmarin/run-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Run Development safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Run Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Run Development free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Run Development?

igmarin (@igmarin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Run Development by igmarin — Agent Skill

Name: Run Development
Author: igmarin

Run Development

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).

igmarin 3ee4f10 3.4 KB Updated Sep 17, 2026

File contents

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.

---name: run-developmentdescription: 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).license: MIT---# run-developmentUse 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 Rules1. **Start the development server**: ```bash hanami dev ``` **Verify:** Once started, confirm the server is responding: ```bash 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`)2. **Start the console**: **Before starting**, ensure `DATABASE_URL` is set if your app uses a database: ```bash echo $DATABASE_URL ``` Then start the console: ```bash hanami console ``` Uses `development` environment by default; override with `HANAMI_ENV=test hanami console`. Access components directly: ```ruby 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 issues3. **Use the console for exploration**: ```ruby # 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 ```4. **List routes and middleware**: ```bash 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**](../create-app/SKILL.md) | Development commands are used after creating the app. || [**manage-database**](../manage-database/SKILL.md) | Database commands may be needed before starting the dev server. |

Frequently asked questions