dotfiles

Run a bounded multi-provider review and local repair workflow for a pull request, branch, or local diff, using fresh Codex exec threads for fixes and requiring separate authorization for every repository or PR publication action.

Clone and explore external codebases using the btx CLI. Use this skill when: - User wants to explore a GitHub repository (e.g., "explore anthropics/claude-code") - User asks how a library/framework works and you need to read its source - User wants to understand implementation details of an external project - User provides a repo URL or owner/repo and wants you to examine it - You need GitHub repository metadata (ownership, archived, last push) without curl

Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and patch context and the thread-aware prc CLI for review state and inline comments.

Read-only triage and routing for GitHub repositories, pull requests, issues, patches, and review comments through the connected GitHub app and local git. Use for general GitHub orientation or summaries before choosing a mutation, review-fix, CI, or publishing workflow.

Fetch and analyze GitHub PR conversations, review submissions, and thread-aware code feedback using the prc CLI. Use for PR comment summaries, unresolved or outdated thread inspection, requested changes, and code-linked review context. Accepts PR numbers, PR URLs, or owner/repo format.

Create or revise a guarded, auditable implementation spec for Codex or another agent. Use only when the user explicitly invokes $goal-ready-spec or specifically asks to make a spec goal-ready.

Helper for delegating coding work or read-only analysis to OpenCode with Z.ai Coding Plan GLM 5.2.

Helper for delegating coding work or read-only analysis to the Grok CLI (grok-4.5).

Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), Figma Motion animations (MCP), and shaders (MCP source / native export). Use when the user pastes a figma.com link or asks to bring a Figma design, frame, logo, brand, or animation into a video/composition.

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

Run and troubleshoot the HyperFrames CLI development and rendering loop. Use for init, add, catalog, capture, lint, check, validate, inspect, layout, beats, keyframes, snapshot, compare, grade-compare, preview, play, present, render, publish, feedback, cloud, lambda, cloudrun, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, auth, transcribe, tts, and remove-background commands.

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

Use when a HyperFrames composition needs seek-safe 2D or 3D keyframes, GSAP timelines, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph or draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Do not use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

Discover, install, wire, and contribute HyperFrames registry blocks and components. Use for hyperframes catalog or add, tag-based installs, hyperframes.json paths, block sub-composition wiring, component snippet merging, registry manifests, demos, templates, and upstream registry contributions.

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, slideshow / interactive deck, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

Resolve, generate, transform, catalog, and reuse media for HyperFrames projects. Use for BGM, SFX, images, icons, official brand logos, voiceover, TTS, captions, transcription, background removal, color grades, LUTs, media cuts or reframes, and cross-project media reuse. Produces frozen local assets or paste-ready blocks plus manifest records while keeping search noise out of context.

Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Not a general site tour (/website-to-video). Unclear → /hyperframes.

Search and manage academic literature with the local `aps` CLI across unified Semantic Scholar, OpenAlex, and ChinaRxiv discovery; paper, citation, reference, and author lookup; repeatable scan manifests; PDF download; and a local full-text/vector library. Use for scholarly literature discovery, citation-graph research, paper identifiers, author metrics, systematic update scans, or local paper-corpus work. Do not use for ordinary web search or non-academic sources.

Prepare focused git commits using Praveen Perera's commit workflow and message rules. Use when the user asks Codex to create a commit, split outstanding changes into logical commits, draft a commit message, stage changes, separate unrelated working-tree edits, or verify a commit is ready.

Draft a compact, paste-ready Codex goal prompt with a measurable outcome, evidence surface, constraints, boundaries, iteration policy, and honest blocker handling. Use only when the user explicitly invokes $goal-prompt or /goal-prompt.

Create a concise, durable handoff document that lets a fresh agent resume the current work without relying on conversation history.

Plan and execute Jujutsu (jj) version-control workflows, including inspecting repository state, splitting or updating changes, arranging stacked, independent, or hybrid PR graphs, syncing after merges, and publishing bookmarks. Use for jj commands, change IDs, revsets, bookmarks, history rewriting, Git interoperability, or preparing commits and pull requests in a jj repository.

Integrate MoneyDevKit's `@moneydevkit/nextjs` package into Next.js App Router applications for hosted or custom Lightning checkout, amount and product payments, server-only MDK operations, and payment verification. Use when a Next.js project mentions MoneyDevKit/MDK, Lightning checkout, Bitcoin sats, product checkout, payment polling, or server-side fulfillment. Do not use for non-Next.js MDK integrations or generic Bitcoin wallet code.

Refine an implementation plan or spec through evidence-first investigation and focused user decisions until no material ambiguity remains or the user ends the refinement.

Turn a feature idea, rough plan, spec, or implementation direction into a standalone Planport visual plan with evidence-backed decisions, diagrams, file maps, annotated code, open questions, and UI or prototype review when useful. Use to create a new reviewable plan or deeply refine an existing one.

Turn a PR, branch, commit, git diff, or completed work unit into a local interactive Planport recap with mechanically grounded diagrams, file maps, API/schema summaries, UI states, annotated diffs, and focused review notes.

Add captions to a talking-head video. ONE catalog (CATALOG.md) of 36 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Runs locally end-to-end (transcribes and mattes the subject itself, no API key). Requires hyperframes and a single-subject clip (multi-shot clips are s

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a product promo (/product-launch-video) or a site tour (/website-to-video). Unclear → /hyperframes.

The fallback workflow for authoring or editing any custom HyperFrames composition at any length or format — longer / multi-scene pieces, brand and sizzle reels, montages, title cards, static loops, freeform builds. Use only when no specialized workflow fits the input; routing table at /hyperframes.

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.

Turn a music track (an audio file, a video to pull audio from, or a track generated from a mood brief) into a beat-synced video — lyric video, slideshow, or kinetic promo. The music drives all pacing; any user-supplied images/videos are cut onto the same beat grid, and a complete video needs zero assets. Narrated pieces → the input-matched workflow (see /hyperframes). Unclear → /hyperframes.

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

Port an existing Remotion (React) composition's source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing Remotion mention, reference-only code, or "make something like my Remotion video" is a fresh build (/general-video). Unclear → /hyperframes.

Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

Package an existing talking-head / interview / podcast video with timed, designed GRAPHIC OVERLAY cards — kinetic titles, lower-thirds, data callouts, quotes, side panels, picture-in-picture — synced to the transcript, on a 16:9 / 9:16 / 4:5 canvas of your choice; the clip plays untouched underneath. Trigger on "graphic overlays", "on-screen graphics", "package / dress up my video". Not plain subtitles (/embedded-captions). Unclear → /hyperframes.

Capture a general website/URL and turn it into a video OF the site — tour, showcase, or social clip built from captured screenshots and the site's own brand assets. Use for portfolio / blog / docs / landing-page showcases. Not a product launch or promo, even from a URL (/product-launch-video). Unclear → /hyperframes.

Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.

Refactor TypeScript code for clarity, structure, and maintainability. Splits large modules, reduces nesting, improves domain models, then applies style conventions. Use when asked to "refactor this TypeScript", "clean up this TS module", "split this file", "simplify this TypeScript code", or `/refactor-typescript`.

Comprehensive Cloudflare platform skill covering development, deployment, hosting, publishing, setup, and troubleshooting for Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum, canonical redirects), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development or deployment task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.