Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在 rove 仓库内跑 auto-motion——把 transcription.srt 拆成多段 MG 动画镜头并拼接成竖屏视频(storyboard 分镜 + theme.md 全片主题 + 逐镜头 claude -p 子进程 + ffmpeg 拼接)。本 skill 是薄 wrapper:解析 auto-motion 模板根,继承 rove 品牌 theme,执行逻辑以 auto-motion 仓库的 canonical SKILL.md 为准。当用户说"跑 auto-motion"、"把这个字幕稿/口播稿做成视频"、"给 rove 做一条 MG 宣传片"时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, beat planning, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-motion`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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, 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 topic guides, 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, or brand-reel pieces (use general-video), topic explainers (faceless-explainer), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer treatment, see /hyperframes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Autonomously cut a Rove (`@sma1lboy/rove`) release end-to-end — detect the semver bump from pending changesets (flagging an upstream `minor` you didn't intend), run the release gates, dispatch the Changesets workflow (or run `scripts/release.sh` locally), then poll the GitHub Actions Release workflow with `gh` until npm publish completes, diagnosing CI failures (npm token, registry 404, lint, branch mismatch) instead of leaving them silent. Use when the user says "cut a release", "ship a version", "release Rove", "release rove", "发版", "release.sh", or "bump the version". Never force-pushes; always verifies the release landed on `main`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices for Remotion - Video creation in React
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
已并入 brand-video(兼容别名)。参考录屏→真机捕获→Remotion 重建的方法(storyboard 纪律、捕获管线、舞台相机权重算法、speed cut)现在是 brand-video 的分析+捕获模块。触发本 skill 时直接加载 brand-video 及其 references/replay-capture.md。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — `rove api send`, never a peer/MCP side channel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. Use why for motivation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from independent angles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.