소설, 시나리오, 블로그, 퇴고, 교정 (1.8천건)
ユーザーが新しい技術を学ぶことを第一目的として、このリポジトリの文体と構成に従い、調査、構成合意、サンプル実装・検証、執筆、レビュー、理解度クイズまでを行って技術ブログ記事の下書きを作成する。ユーザーがブログ記事を書いて、新しい API や機能を紹介して、ハンズオンを作って、技術調査を記事化して、経験や意見を記事にして、と依頼したときに使用する。新しい API・Web 標準の記事では、一次情報と仕様策定の議論を調べ、実行可能なサンプルを作成して実環境で検証する。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
技術ブログ記事、チュートリアル、技術原稿を、技術的正確性、一次情報、現在の API 挙動、コード、再現性、セキュリティ、アクセシビリティ、互換性の観点からレビューする。技術的な主張、コードサンプル、対応バージョン、仕様、公開前の正確性を確認してほしいと依頼されたときに使用する。一般的な文章校正は article-review に任せ、明示的な依頼なしに原稿を変更しない。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
引数で指定した記事のレビューを行います。記事スラッグを引数に渡すと、textlint による自動校正と誤字脱字・文法的な誤りの指摘を行います。/article-review [スラッグ] の形式で呼び出してください。記事を書いた後のチェック、公開前の校正、文章の品質確認にも使用してください。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute approved, bounded work in an isolated implementation conversation and return a structured evidence receipt. Use with inherited history or an explicitly identified source; no particular planning, testing, or review skill is required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing or adapting newly created, downloaded, forked, installed, or community Agent Skills to the user's tools, habits, directories, session history, and preferred workflows, especially when triggers feel wrong, noisy, or too generic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when mining coding-agent session history, archived transcripts, memories, or repeated local work to discover recurring workflows that should become new Agent Skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews and adjusts PRD plans based on research findings. Use after completing research to evaluate story modifications. Triggers on: review plan, adjust stories, update prd based on research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a Hacker News + Reddit launch playbook for developer-tools and community-led products during PRD v0.9 Go-to-Market. Triggers on requests to plan HN/Reddit launch, "Show HN" post, community launch, or when user asks "HN launch", "Show HN", "Reddit launch", "launch on /r/SaaS", "Product Hunt vs HN", "community launch", "developer launch". Outputs GTM-* with Type=Channel-HN / Type=Channel-Reddit entries with timing, title, story angle, and engagement plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish baseline → snapshot → compare → history monitoring for any KPI, config, or metric that can drift during PRD v0.8 Deployment & Ops. Triggers on requests to monitor drift, baseline a value for later comparison, or when user asks "how do we track if X changes?", "baseline this", "config drift", "performance regression", "metric drift", "compare to last week", "is this getting worse?". Outputs MON-DRIFT-* entries with baseline + comparison rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Написание русскоязычной статьи или лонгрида с нуля: бриф, фактура, структура, черновик и самопроверка по методу Людмилы Сарычевой. Use this skill whenever the user asks to write, outline, structure, draft, assemble, or turn notes/interviews/materials into a Russian article, newsletter essay, longread, case, guide, or expert text. Триггеры: «напиши статью», «собери лонгрид», «напиши текст для блога про…», «есть интервью с экспертом, сделай статью», «составь план статьи», «придумай структуру», «собери материал», «сделай черновик», «напиши колонку», «из интервью в статью», «план лонгрида», «текст с нуля», «помоги написать материал». Для коротких постов в соцсети см. skill post; для правки готового текста — redaktura; для текстов интерфейса — ux-copy; для настройки проекта — redpolitika.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for 'why does X work this way', 'why we picked Y', '为什么这么设计', design rationale, regressions, or where a magic number came from. Fans out one investigator per evidence category — in this repo that starts with the local decision record (ADRs, docs/design, the daemon issue store, the changelog, wisp) plus git history, and adds MCP-backed categories when the session has them — then returns a cited read with the gaps named. Use `how` for what the code does at runtime.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在 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 宣传片"时使用。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
已并入 brand-video(兼容别名)。参考录屏→真机捕获→Remotion 重建的方法(storyboard 纪律、捕获管线、舞台相机权重算法、speed cut)现在是 brand-video 的分析+捕获模块。触发本 skill 时直接加载 brand-video 及其 references/replay-capture.md。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
World-class motion graphics expertise combining the animation principles of Disney, the kinetic typography of MK12, and the visual storytelling of studios like Buck and Ordinary Folk. Motion graphics transforms static ideas into dynamic visual experiences. Great motion graphics doesn't just move—it communicates. Every animation should have purpose: to guide attention, reinforce message, create emotion, or clarify concept. The best motion designers understand that restraint is power, that timing is everything, and that the animation should be invisible—viewers should feel the story, not notice the effects. Use when "motion graphics, animation, animate, motion design, kinetic, logo animation, title sequence, lower thirds, animated, after effects, lottie, transitions, motion, motion, graphics, animation, after-effects, lottie, kinetic, typography, design" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in creating rich backstories, fictional universes, and ARGs (Alternate Reality Games). Covers world-building, mystery construction, community-driven storytelling, and transmedia narratives. Knows how to create depth that rewards exploration without overwhelming. Use when "lore, world building, backstory, ARG, mythology, fictional universe, hidden story, deep canon, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in crafting launch narratives - product launches, feature releases, company announcements, and milestone communications. Covers launch timing, narrative arc, channel strategy, and the art of creating buzz. Knows how to turn a release into an event, and when quiet launches are better than splash. Use when "product launch, launch story, announcement, feature release, launch narrative, go live, release announcement, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Most startup ideas are bad. Not because founders lack creativity, but because they're solving invented problems instead of lived ones. Paul Graham's essays reveal a pattern: the best ideas come from living in the future and noticing what's missing. Schlep blindness hides gold. Organic ideas beat brainstormed ones. Frighteningly ambitious ideas are often easier. This skill synthesizes PG's idea-finding wisdom into actionable guidance. Use when "keywords, contexts, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Founders face unique challenges in how they work. Maker vs manager schedule conflicts. Default alive vs dead math. Time and money slowly leaking away. Effective founders develop systems for navigating these challenges. This skill synthesizes PG's essays on founder productivity and decision-making into an operating system for founder effectiveness. Use when "keywords, contexts, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
What makes founders succeed? Paul Graham has observed thousands of founders and distilled patterns. Relentlessly resourceful. Fierce nerds. Earnest. These traits matter more than credentials or connections. This skill synthesizes PG's essays on founder character into actionable guidance for developing the traits that predict success. Use when "keywords, contexts, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge for environment art in games - modular design, visual hierarchy, color scripting, environmental storytelling, optimization, and world-building. From blockout to final art pass, creating immersive, performant, and readable spaces. Use when "environment art, level art, world art, modular kit, kit-bashing, set dressing, prop placement, biome design, visual hierarchy, color script, hero prop, trim sheet, environment composition, skybox, atmosphere, environment, level-art, world-building, modular, kit-bashing, set-dressing, visual-design, game-art, composition, optimization" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memoryUse when "conversation memory, remember, memory persistence, long-term memory, chat history, memory, conversation, persistence, context, llm" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in presenting technical work to non-technical audiences. Covers demo preparation, storytelling for demos, handling failures gracefully, and making work visible and impressive. Understands that perception is reality and great work undemoed is invisible work. Use when "demo, present, show stakeholders, demo day, showcase, walkthrough, show and tell, " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.