genie-hacks

# /genie-hacks — Community Hacks & Patterns

Browse real-world Genie patterns contributed by the community. Search by problem, explore by category, or contribute your own.

## When to Use
- User wants to discover Genie tips, tricks, or advanced patterns
- User asks "how do I optimize costs?", "how do teams work?", or similar problem-oriented questions
- User wants to contribute a hack they discovered
- User invokes `/genie-hacks` with any subcommand
- If no subcommand is given, default to `list`

## Commands

| Command | Description |
|---------|-------------|
| `/genie-hacks` | List all hacks (same as `list`) |
| `/genie-hacks list` | List all hacks with title, problem, and category |
| `/genie-hacks search <keyword>` | Search hacks by keyword in title/problem/solution |
| `/genie-hacks show <hack-id>` | Display full hack details |
| `/genie-hacks contribute` | Submit a new hack via automated PR flow |
| `/genie-hacks help <problem>` | Describe a problem, get matched to relevant hacks |

---

## Hacks Registry

The canonical hacks live in the docs at `genie/hacks.mdx`. Below is the embedded registry for `list`, `search`, `show`, and `help` commands. Use this data directly — do not require an external file.

### hack: provider-switching
- **ID:** `provider-switching`
- **Title:** Provider Switching — Right Model for the Job
- **Category:** providers
- **Problem:** You're using one provider for everything, but some tasks need speed (Codex) and others need precision (Claude).
- **Solution:** Use `--provider` flag to switch per-task. Configure provider per agent role in team config.
- **Code:**
  ```bash
  # Fast scaffolding with Codex
  genie agent spawn engineer --provider codex

  # Careful review with Claude
  genie agent spawn reviewer --provider claude

  # Team-level: set default per role
  genie team create my-feature --repo . --wish my-slug
  genie team hire engineer --provider codex
  genie team hire reviewer --provider claude
  ```
- **Benefit:** 2-3x faster scaffolding with Codex, higher-quality reviews with Claude. Match the model to the cognitive demand.
- **When to use:** Teams with mixed workloads — boilerplate generation vs. nuanced code review. When cost or speed matters per task.

### hack: team-coordination
- **ID:** `team-coordination`
- **Title:** Multi-Team Coordination at Scale
- **Category:** teams
- **Problem:** You have multiple wishes that depend on each other, and running them sequentially wastes time.
- **Solution:** Use `/dream` to batch-execute wishes with dependency ordering. Same-layer wishes run in parallel.
- **Code:**
  ```bash
  # Queue wishes for overnight execution
  /dream

  # Or manually create parallel teams
  genie team create auth-refactor --repo . --wish auth-refactor
  genie team create api-v2 --repo . --wish api-v2

  # Monitor both
  genie wish status auth-refactor
  genie wish status api-v2

  # Cross-team messaging
  genie agent send 'auth-refactor is done, you can proceed' --to api-v2-team-lead
  ```
- **Benefit:** Parallel execution of independent wishes. Overnight batch runs that produce PRs by morning.
- **When to use:** Projects with 3+ wishes queued. Sprint planning where multiple features can be parallelized.

### hack: overnight-batch
- **ID:** `overnight-batch`
- **Title:** Overnight Batch Execution with /dream
- **Category:** batch
- **Problem:** You have a backlog of approved wishes but limited daytime hours to supervise execution.
- **Solution:** Use `/dream` to queue SHIP-ready wishes, set dependency order, and let agents execute overnight. Wake up to PRs and a DREAM-REPORT.md.
- **Code:**
  ```bash
  # 1. Ensure wishes are in brainstorm.md under "Poured"
  cat .genie/brainstorm.md

  # 2. Launch dream run
  /dream
  # Select wishes: 1 3 5 (or "all")
  # Confirm DREAM.md execution plan
  # Go to sleep

  # 3. Morning: check results
  cat .genie/DREAM-REPORT.md
  gh pr list --author @me
  ```
- **Benefit:** 8+ hours of unattended execution. Multiple PRs ready for review by morning.
- **When to use:** End of day with 2+ SHIP-ready wishes. Sprint velocity needs a boost without more human hours.

### hack: custom-skills
- **ID:** `custom-skills`
- **Title:** Custom Skills for Repeated Workflows
- **Category:** skills
- **Problem:** You keep typing the same sequence of commands or giving the same instructions repeatedly.
- **Solution:** Create a custom skill in `skills/<name>/SKILL.md` with YAML frontmatter. Claude loads it when invoked via `/<name>`.
- **Code:**
  ```bash
  mkdir -p skills/deploy-check
  cat > skills/deploy-check/SKILL.md << 'EOF'
  ---
  name: deploy-check
  description: "Pre-deploy checklist — tests, migrations, env vars."
  ---
  # /deploy-check
  1. Run `bun test`
  2. Check migrations: `bunx prisma migrate status`
  3. Verify env vars are set
  4. Build: `bun run build`
  5. Report pass/fail table
  EOF

  # Use it
  /deploy-check
  ```
- **Benefit:** Encode tribal knowledge as reusable skills. New team members get instant access to workflows.
- **When to use:** Any workflow you've explained more than twice. CI-like checks you want to run locally before pushing.

### hack: hook-automation
- **ID:** `hook-automation`
- **Title:** Git Hook Automation with Genie Hooks
- **Category:** hooks
- **Problem:** You want agents to automatically react to git events — spawning a reviewer on PR creation, running tests on commit.
- **Solution:** Use Genie's hook system and Claude Code hooks in `.claude/settings.json` to trigger actions on events.
- **Code:**
  ```bash
  # Auto-spawn is built in — set GENIE_AGENT_NAME for dispatch:
  export GENIE_AGENT_NAME=my-agent

  # Claude Code hook example (.claude/settings.json):
  {
    "hooks": {
      "PreToolUse": [{
        "matcher": "Bash",
        "hooks": [{
          "type": "command",
          "command": "echo 'Tool being used: Bash'"
        }]
      }]
    }
  }
  ```
- **Benefit:** Automated reactions to development events. Less manual orchestration.
- **When to use:**