genie-hacks — Community Hacks & Patterns
Runtime syntax: invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime.
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 a problem-oriented question — "how do I optimize costs?", "how do teams work?"
- User wants to contribute a hack they discovered
- User invokes
genie-hacks with any subcommand (no subcommand → list)
Data Sources
- Registry: Read
references/catalog.md (relative to this skill's directory) before answering any list/search/show/help request — it holds every hack (problem, solution, code, benefit, when-to-use) plus the category table. Never invent a hack that isn't in it.
- Contribute mechanics: Read
references/contributing.md when running contribute — exact fork/branch/PR commands and error recovery.
- Published page: https://docs.automagik.dev/genie/hacks (source
genie/hacks.mdx in automagik-dev/docs).
Commands
| Command |
Behavior |
genie-hacks / list |
Table of all hacks — ID, title, category — then the count and a contribute nudge. |
search <keyword> |
Case-insensitive match over title/problem/solution/code; show ID, title, category, problem snippet per match. None → suggest broader terms or list. |
show <hack-id> |
Full entry: problem, solution, code, benefit, when to use. Unknown ID → suggest the closest IDs. |
help <problem> |
Match the described problem to the top 3 relevant hacks; one-line "why" plus a quick tip each. Prefer a loose match over "no matches". |
contribute |
Guided submission → automated PR to automagik-dev/docs. |
End list and show with a pointer to show <id> and contribute.
Contribute Flow
- Gather — title, problem, solution (with code), category (one from the catalog's category table), benefit, when-to-use. One question at a time; friendly and low-friction.
- Preview — render the hack in the catalog template; confirm: yes → submit, edit → re-prompt that field and re-preview, cancel → abort politely.
- Submit — after the confirmed preview explicitly authorizes external submission, follow
references/contributing.md: preflight GitHub access, fork/clone or use the GitHub connector, branch hack/<slug>, append under the category heading in genie/hacks.mdx, commit hack: <title>, and open the PR against dev.
- Report — lead with the PR URL and what happens next (maintainer review, then it lands on the published page).
If gh is missing/unauthenticated or any GitHub step fails, save the formatted hack to ~/.genie/cache/pending-hacks/<hack-id>.md and relay the manual PR steps — never lose the user's write-up.
Rules
- Hack IDs are lowercase kebab-case and unique — check existing IDs before appending.
- Hacks must be realistic and tested — no aspirational or untested patterns.
- Catalog code must use the live v5 CLI (
genie --help is the source of truth); v4-era entries carry a note with the live replacement.
- PRs always target
dev — never main/master.
- Keep output concise — tables for
list, full format only for show.
- Community discussion: https://discord.gg/automagik
1---2name: genie-hacks3description: Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.4---56# genie-hacks — Community Hacks & Patterns78**Runtime syntax:** invoke the plugin copy through the active runtime's owner-qualified skill selector; use a bare selector only when intentionally selecting a user-tier copy (a separately installed personal copy; Genie no longer seeds this tier). Cross-skill prose below uses bare names as portable semantic routes; the orchestrator resolves the selector for the active runtime.910Browse real-world Genie patterns contributed by the community. Search by problem, explore by category, or contribute your own.1112## When to Use13- User wants to discover Genie tips, tricks, or advanced patterns14- User asks a problem-oriented question — "how do I optimize costs?", "how do teams work?"15- User wants to contribute a hack they discovered16- User invokes `genie-hacks` with any subcommand (no subcommand → `list`)1718## Data Sources19- **Registry:** Read `references/catalog.md` (relative to this skill's directory) before answering any list/search/show/help request — it holds every hack (problem, solution, code, benefit, when-to-use) plus the category table. Never invent a hack that isn't in it.20- **Contribute mechanics:** Read `references/contributing.md` when running `contribute` — exact fork/branch/PR commands and error recovery.21- Published page: https://docs.automagik.dev/genie/hacks (source `genie/hacks.mdx` in automagik-dev/docs).2223## Commands2425| Command | Behavior |26|---------|----------|27| `genie-hacks` / `list` | Table of all hacks — ID, title, category — then the count and a `contribute` nudge. |28| `search <keyword>` | Case-insensitive match over title/problem/solution/code; show ID, title, category, problem snippet per match. None → suggest broader terms or `list`. |29| `show <hack-id>` | Full entry: problem, solution, code, benefit, when to use. Unknown ID → suggest the closest IDs. |30| `help <problem>` | Match the described problem to the top 3 relevant hacks; one-line "why" plus a quick tip each. Prefer a loose match over "no matches". |31| `contribute` | Guided submission → automated PR to automagik-dev/docs. |3233End `list` and `show` with a pointer to `show <id>` and `contribute`.3435## Contribute Flow361. **Gather** — title, problem, solution (with code), category (one from the catalog's category table), benefit, when-to-use. One question at a time; friendly and low-friction.372. **Preview** — render the hack in the catalog template; confirm: yes → submit, edit → re-prompt that field and re-preview, cancel → abort politely.383. **Submit** — after the confirmed preview explicitly authorizes external submission, follow `references/contributing.md`: preflight GitHub access, fork/clone or use the GitHub connector, branch `hack/<slug>`, append under the category heading in `genie/hacks.mdx`, commit `hack: <title>`, and open the PR against `dev`.394. **Report** — lead with the PR URL and what happens next (maintainer review, then it lands on the published page).4041If `gh` is missing/unauthenticated or any GitHub step fails, save the formatted hack to `~/.genie/cache/pending-hacks/<hack-id>.md` and relay the manual PR steps — never lose the user's write-up.4243## Rules44- Hack IDs are lowercase kebab-case and unique — check existing IDs before appending.45- Hacks must be realistic and tested — no aspirational or untested patterns.46- Catalog code must use the live v5 CLI (`genie --help` is the source of truth); v4-era entries carry a note with the live replacement.47- PRs always target `dev` — never `main`/`master`.48- Keep output concise — tables for `list`, full format only for `show`.49- Community discussion: https://discord.gg/automagik
automagik-dev