Loading...
Loading...
Found 571 Skills
Design, critique, and revise UML diagrams from a modeling and communication perspective. Use when model is asked to create or improve UML; when the user asks for a graphical representation, diagram, schema, visual model, process map, state view, architecture view, or system representation of software/system behavior or structure; when the user does not explicitly choose UML but needs a model-like visual explanation; when model must autonomously choose the right UML diagram type or split across multiple UML diagrams. Use for reasoning about diagram form, abstraction level, boundaries, grouping, lifecycle/state design, behavior vs structure, interaction design, or diagnosing why a diagram feels wrong at the modeling level. This skill treats notation as the final representation, not as the core task.
Hypothesis-driven debugging with ranked hypotheses, git bisect strategy, instrumentation planning, and minimal reproduction design. Triggers on: "debug this systematically", "root cause analysis", "bisect this bug", "rank hypotheses", "isolate this issue", "minimal reproduction". NOT for general reasoning.
Use when the user wants to teach / learn an English word as a video — turn a single English word into a self-contained HLS "supercut" lesson built from the mira video base. Stitches every season2 clip where the word is spoken (via the search-app API) into one .m3u8, prepended with a Claude-written bilingual word-intro card (word + IPA + 中文 gloss + usage, Volcano TTS) and appended with a 关注王建硕 CTA card. No MP4 burn. Triggers — "teach <word>", "讲讲 <word>", "学英语 <word>", "把 <word> 做成视频", "/wjs-teaching-english <word>".
Use after zanahoria-multi-assumptions has filed N parallel issue variants AND @coderabbitai has responded to all of them — closes the family by extracting the load-bearing assumption, naming a winner, capturing the decision as an ADR, and cleanly closing the rejected variants with cross-referenced reasoning. Triggers on close-the-family, pick-a-winner, commit-the-decision, decide-variants, after-CR-responds, zanahoria-decisions.
12 research methodology skills. Trigger: study design, methodology selection, scientific reasoning, mentoring. Design: rigorous methods frameworks covering qualitative, quantitative, and mixed approaches.
Build and operate a live game using Unity Services. Use when the user needs to implement, connect, or debug backend-driven features — battle passes, achievements, player progression, cloud saves, leaderboards, matchmaking, virtual economies, server-authoritative logic, anti-cheat, player accounts and authentication, remote configuration, feature flags, A/B testing, analytics, or cloud resource deployment. Triggers on live-ops, live service, backend, server authority, cloud code, cloud save, remote config, player data, retention, monetization loop, season pass, ranking, multiplayer sessions, lobbies, or any Unity Services integration.
Design distributed systems using Leslie Lamport's rigorous approach. Emphasizes formal reasoning, logical time, consensus protocols, and state machine replication. Use when building systems where correctness under concurrency and partial failure is critical.
Apply Sherlock Holmes' deductive method to debug code, diagnose system issues, and solve technical puzzles using systematic elimination and logical reasoning
20 "In Market" Bridgebound triggers from Flip The Script - Adjacent Vendors, Competitors, and Time-Based signals. Use when targeting active buyers, building competitive displacement campaigns, or leveraging seasonal/event timing.
Bulk transition products through DRAFT → ACTIVE → ARCHIVED status for seasonal launches and sunsetting.
Quantitative signal scanning and position sizing tool based on the original Turtle Trading method. It retrieves market data for A-shares / Hong Kong stocks / US stocks / Singapore stocks via longbridge CLI, and automatically calculates ATR (N value), breakout signals (System 1 / System 2), stop-loss prices, add-on positions, and Unit position sizes. Trigger this tool when users mention 海龟, turtle, 海龟交易, 海龟信号, turtle signal, turtle trading, or ask about breakout signals, ATR, N value, Unit positions, stop-loss prices, add-on positions, S1/S2 signals, 20-day high/low, 55-day breakout, or request to scan watchlists/indexes for trading signals using the turtle system. It also triggers when users say "扫描突破信号", "帮我算Unit", "海龟止损", "海龟系统分析", or any combination of a stock name/code with "海龟". **Applicable scenarios:** - Scan for breakout signals (20-day/55-day high/low breakouts) after daily market close - Calculate ATR, stop-loss prices, and add-on positions for single stocks or batches of targets - Calculate reasonable Unit position sizes based on account net assets - Determine whether existing positions trigger exit or add-on conditions - Scan turtle signals for watchlist stocks / index components **Not applicable for:** - Fundamental analysis (Turtle system is purely technical) - Predicting price direction - Automatic order placement (only outputs signals; users operate on their own) - Short-selling opening operations for A-shares/Hong Kong stocks/Singapore stocks
Use this skill when a user provides a torrent name or file name and wants to fix recognition issues, or asks to add/manage custom identifiers (自定义识别词). This skill generates identifier rules based on the WordsMatcher preprocessing logic, checks for duplicates against existing rules, and saves them via MCP tools. Because custom identifiers are global, generated rules must default to conservative, sample-specific regex patterns instead of broad matches unless the user explicitly wants global cleanup. Applicable scenarios include: 1) A torrent or file name is incorrectly recognized (wrong title, season, episode, etc.); 2) The user wants to block unwanted keywords from torrent names; 3) The user needs episode offset rules for series with non-standard numbering; 4) The user wants to force recognition of a specific media by TMDB/Douban ID.