メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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
Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch
Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context
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
| 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. |
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.
Run the startup script:
bash .claude/skills/bindev/scripts/start_dev.sh
Interpret the output:
ALREADY_RUNNING + READY — server was already up, open the browserSTARTED + READY — server started cleanly, open the browserSTARTED + TIMEOUT — process started but didn't respond in 20s; warn
the user and have them tmux attach -t APPNAME-dev to see the logsOpen the homepage:
open http://localhost:APPNAME_PORT
Confirm to the user that the dev server is up and the homepage is open.
The fleet runs in a tmux session named APPNAME-dev. Useful commands:
tmux attach -t APPNAME-devtmux kill-session -t APPNAME-devtmux ls