Menu
Use when viewing available handoff documents โ lists active and archived handoffs with their status, date, topic, and branch
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.
Based on SOC occupation classification
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.
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.
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 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 | superpowers-ruby:handoff-list |
| description | Use when viewing available handoff documents โ lists active and archived handoffs with their status, date, topic, and branch |
Display all available handoff documents, both active (unrestored) and archived (consumed). Helps you decide which handoff to resume or review.
Announce at start: "I'm using the handoff-list skill to show available handoffs."
superpowers-ruby:handoff-resume to see what's available# Active handoffs
ls docs/handoffs/*.md 2>/dev/null
# Archived handoffs
ls docs/handoffs/_archive/*.md 2>/dev/null
For each file found, read the YAML frontmatter to extract: created, topic, branch, trigger, restored.
Present results with active (unrestored) handoffs first, then archived, sorted by date descending:
## Active Handoffs
| Date | Topic | Branch | Trigger |
|------|-------|--------|---------|
| 2026-04-14 | handoff-skill | lg/handoff | manual |
## Archived Handoffs
| Date | Topic | Branch | Trigger | Restored At |
|------|-------|--------|---------|-------------|
| 2026-04-13 | auth-refactor | fix/auth | compact | 2026-04-13T15:30:00 |
If no handoffs exist:
No handoff documents found in docs/handoffs/ or docs/handoffs/_archive/.
Use `/superpowers-ruby:handoff` to create one.
If active handoffs exist, offer:
"Would you like to resume from one of the active handoffs? Use
/superpowers-ruby:handoff-resume."