Run any Skill in Manus with one click

bindev

Stars4

Forks0

UpdatedJuly 15, 2026 at 17:25

Start the local development server in a tmux session and open the homepage. Use when the user wants to start development, run the app locally, fire up the dev server, or invokes /bindev.

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

zarpay

zarpay/rails-template

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

File Explorer

2 files

SKILL.md

readonly

name	bindev
description	Start the local development server in a tmux session and open the homepage. Use when the user wants to start development, run the app locally, fire up the dev server, or invokes /bindev.

bindev

Start bin/dev (the Procfile.dev fleet: web + tailwind watcher + Solid Queue worker) in a detached tmux session and open the homepage in the browser.

Workflow

Run the startup script:

bash .claude/skills/bindev/scripts/start_dev.sh

Interpret the output:
- ALREADY_RUNNING + READY — server was already up, open the browser
- STARTED + READY — server started cleanly, open the browser
- STARTED + TIMEOUT — process started but didn't respond in 20s; warn the user and have them tmux attach -t APPNAME-dev to see the logs
Open the homepage:
```
open http://localhost:APPNAME_PORT
```
Confirm to the user that the dev server is up and the homepage is open.

Tmux session

The fleet runs in a tmux session named APPNAME-dev. Useful commands:

Attach: tmux attach -t APPNAME-dev
Kill: tmux kill-session -t APPNAME-dev
List: tmux ls

More from this repository

same repository

37signals-style

zarpay/rails-template

Rails coding patterns derived from analysis of 37signals' Fizzy codebase. Use when writing Rails code in 37signals/Basecamp style or when asked to follow 37signals patterns. Covers controllers, models, views, Hotwire, testing, database, security, and team philosophy.

2026-07-154

design-system

zarpay/rails-template

Machina design system quick reference. Use when discussing design tokens, surfaces, card backgrounds, depth, elevation, typography tokens, color tokens, DaisyUI theming, or applying visual styling to UI components.

2026-07-154

finishing-a-development-branch

zarpay/rails-template

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

2026-07-154

superpowers-ruby-handoff-list

zarpay/rails-template

Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch

2026-07-154

superpowers-ruby-handoff-resume

zarpay/rails-template

Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context

2026-07-154

superpowers-ruby-handoff

zarpay/rails-template

Use when capturing session state before switching context, ending a session, or manually preserving progress — creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly

2026-07-154

name	bindev
description	Start the local development server in a tmux session and open the homepage. Use when the user wants to start development, run the app locally, fire up the dev server, or invokes /bindev.

bindev

Start bin/dev (the Procfile.dev fleet: web + tailwind watcher + Solid Queue worker) in a detached tmux session and open the homepage in the browser.

Workflow

Run the startup script:

bash .claude/skills/bindev/scripts/start_dev.sh

Interpret the output:
- ALREADY_RUNNING + READY — server was already up, open the browser
- STARTED + READY — server started cleanly, open the browser
- STARTED + TIMEOUT — process started but didn't respond in 20s; warn the user and have them tmux attach -t APPNAME-dev to see the logs
Open the homepage:
```
open http://localhost:APPNAME_PORT
```
Confirm to the user that the dev server is up and the homepage is open.

Tmux session

The fleet runs in a tmux session named APPNAME-dev. Useful commands:

Attach: tmux attach -t APPNAME-dev
Kill: tmux kill-session -t APPNAME-dev
List: tmux ls