Polyhydra Skills

Recap what happened on a project in roughly the last 24 hours (or a stated window), rendered as a visual card with a light "rough morning, here's the highlights" tone, plus a clear list of what's still open and what to do next. Triggers on "what happened while I was out", "catch me up", "back on the horse", "recap the last 24 hours", "get back on track", "morning recap for this project". Not for calendar/personal-schedule briefs — use the morning skill for that.

Route work off the expensive tier -- a Codex CLI worker, a Haiku/Sonnet subagent, or local Ollama -- instead of running it inline. Use for read-only investigation that would flood the transcript (grep sweeps, log trawls, triage) and to dispatch already-specified implementation, on "hand this off", "give it to codex", "use a worker". Code changes still need a GitHub issue first -- route through polyhydra-issue-router, this is not a way to implement without one.

Before scaffolding a "new" idea (tool, automation, script), search the user's own ecosystem and known external projects for prior art so work is not duplicated. Triggers on "new idea", "what if we built", "let's create a", "is there something already for this" -- any moment a fresh tool/automation/skill is about to be proposed. Not for routine bug fixes or well-scoped features in an already-identified codebase.

Use when deciding how to put a choice to the operator, or when a turn is ending for any reason — render real forks as native single-tap pickers, close every handback in selectable options instead of prose, and recognize the cases where asking mid-task is wrong.

Fan out a batch of independent, well-specified housekeeping/recon/mechanical work across several parallel Haiku subagents at once instead of working through it serially. Use on "haiku storm", "storm this", or when there's a pile of low-ambiguity work (close stale issues, clean up merged worktrees, survey a backlog, verify-and-report tasks) that splits cleanly into 3-5 independent lanes. Not for work that needs judgment, touches files another in-flight task is actively editing, or requires a GitHub issue that doesn't exist yet.

Split part of the current conversation into a durable handoff file and launch a fresh session seeded with it, so the old thread can close instead of dragging its context forward. Triggers on "handoff", "hand this off to a new thread", "close this thread and start fresh", "this thread is getting long". Also use when a new session is pointed at a handoff file, to orient before starting work.

Scaffold or extend a ~/projects/<topic> project-home hub that coordinates multiple ~/code repos around one theme (symlinks + workspace.yaml + worktrees/ + README + LOCAL-WORK.md), matching the existing stepmania/rpgs convention. Use when the user wants to "set up a workspace for X", "make a project hub for these repos", "pull related repos together", or asks to replicate the rpgs/stepmania pattern for another topic.

Navigate ~/projects -- list hubs with purpose and health, initialize a new hub (single-repo, or multi-repo via project-home), print a briefing block for a new conversation, recommend what to work on next (git-dirty plus PR plus live-session signal), launch a session in a project, capture a stray idea with no home yet, park or activate backlog entries. Use for "what should I work on", "list my projects", "set me up on X", "start a session in X", "new idea", "jot this down", "note this idea for later", or naming a project under ~/projects.

Generate hero or illustration art (not icons or pixel-art sprites) for a product/landing page via Codex CLI's built-in image tool, authenticated through ChatGPT login rather than API credits. Use when a page needs a hero image or thematic accent art and there is no existing asset to reuse -- e.g. "generate some art for this", "make a hero image". Not for UI icons, pixel-art game sprites, or photorealistic app screenshots.

Mid-chat, draft a quick-learning slide deck (short summary, a few slides, optional images) and push it to the learning-hub display server so it plays on a separate screen -- kiosk device or OBS Browser Source, including live on stream. Use when the user wants to quickly learn or explain a topic visually, especially while streaming, or mentions "learning-hub" or "make a slide deck for this".

Safely inspect and stage ScreenScraper artwork through the local Skyscraper client. Use when a user wants game art or metadata for a catalog, Batocera, or emulation library without exposing credentials or writing directly to a live media library. Ported from a Codex plugin.

Run a fast, local, read-only Codex analysis pass over the current changes and return prioritized recommendations before a pull request is ever opened upstream. Use during a Codex/GitHub review outage or quota gap, and as a routine rapid check before submitting any PR -- advisory only, never a merge gate or a substitute for the real Codex Review Gate.

Send the user a Discord DM via their private bot (SpottieClaw#3956, in the "Polyhydra Games Internal" server) using credentials from ~/.config/secrets/discord.env. Use when a long-running task finishes, something needs the user's attention and they may not be watching the terminal, or they explicitly ask to be pinged/notified/messaged on Discord.

Search Sage's code index before doing an ad-hoc repository sweep. Use when asked "find duplicate logic", "does this pattern exist elsewhere", "what touches X across my repos", or whether code should be reused or consolidated across repositories.

Launch, monitor, and stop the portfolio Burn Console, and run an agent-driven portfolio burn — rank every open issue smallest-first, filter out work that is already done, split it into Codex worker batches, review the resulting PRs, and close verified-complete issues with evidence. Use when the user says "start the burn console", "check burn status", "stop the burn", "codeburn

Plan and execute issue-backed work with Mapped-Frontier Development (MFD), also called STDD. Use when a request mentions MFD, Mapped-Frontier, STDD, Phase 0, a build packet, an approval brief, or when a material product, architecture, security, deployment, or operational change needs durable scope and evidence before implementation. Ported from a Codex plugin — GitHub/issue-based, not tied to any Codex-specific tooling.

Use when the user wants to see GitHub issue progress rendered as a retro text-adventure screen instead of a status report — single-issue quest screens, a multi-issue "dungeon map" overview to answer "where do I need to focus," or optional local-LLM flavor narration layered over real, deterministic issue data.

Define a project's lean V1 from a V0 baseline, including inherited half-built work, then create a GitHub-authoritative epic, feature-story, and QA-validation shape. Use when a project needs its first coherent release definition; when the user mentions V0, V1, a V1 checklist, validation work under an epic, inherited partial code, or post-V1 stabilization.

Safely discover which Infisical project/env/path a secret key lives at, or list what keys exist somewhere -- without ever printing, logging, or writing a secret VALUE. Use before adding a sibling secret next to an existing one, or any time you need to know "where does key X live" without already knowing the value.

Track and advance real-life goals — house work, errands, decisions, recurring obligations — held as files in ~/code/goals. Use when the user asks "what do I need to do", "where are we on the house stuff", wants to add or close a goal, wants a status check or a nudge, or mentions a goal by name (gutters, AC, a subscription to cancel). Also use when the user describes a new real-world obligation in passing that should not be lost.