「common」の検索結果

短视频钩子（开头）类型选择与写法，中文名「钩子」。Use when 起钩子、写钩子、钩子怎么写、钩子没思路、设计前5秒钩子、写视频开头/口播稿开头, or when the user asks 视频开头怎么做、开头模板、hook 类型、帮我起个钩子, including during ra-洗稿 script rewriting and 选题深化. Provides a scenario-based taxonomy of 7 hook types with decision flow, prerequisites, sentence templates, and common mistakes. For diagnosing and optimizing an existing hook draft, use dbs-hook instead; this skill chooses the type, dbs-hook polishes the execution.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.

日本語の概要は準備中です。原文の説明を表示しています。

Write game shaders from cross-engine fundamentals — the vertex→fragment pipeline, coordinate spaces, UV math, and common 2D/3D effects (tint, UV scroll, dissolve, outline, fresnel rim, vignette) in GLSL with HLSL equivalents. Use when the user mentions shaders, fragment/pixel shader, vertex shader, UV, GLSL, HLSL, or effects like dissolve, outline, or rim light.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a promotion defence (晋升答辩) for a level-based promotion process common at Chinese technology companies: the materials, the presentation structure, the evidence for the next level, and a rehearsal of the committee's questions. Use when asked 帮我准备晋升答辩, 晋升述职, 晋升 PPT, how do I prepare for my promotion committee, or 答辩问题. Produces a level-gap analysis against the target level's criteria, the defence presentation outline in Chinese, a timed talk track, and a question bank with answer points, then a mock committee round.

日本語の概要は準備中です。原文の説明を表示しています。

Practise the structured interview (结构化面试) for Chinese civil service and public institution posts (公务员面试 / 事业单位面试): the common question types, a clear answer structure for each, timed mock rounds and feedback on content, structure and delivery. Use when asked 公务员面试怎么准备, 结构化面试题, 帮我模拟面试, 综合分析题怎么答, 应急应变题, or practise the civil service interview. Produces a question-type guide, answer frameworks with worked examples, a timed mock interview asked one question at a time, scored feedback, and a practice plan up to the interview date.

日本語の概要は準備中です。原文の説明を表示しています。

Build a small, coherent opening repertoire that fits your style and level — the few lines actually worth learning, plus the plans and traps behind them. Use when asked what chess opening should I learn, build me a repertoire, help with my openings, or what to play against [opening]. Produces a compact repertoire for White and Black keyed to your rating and style, the main ideas and typical plans (not just moves to memorize), the common traps to know from both sides, and what to study next — kept small enough to actually learn.

日本語の概要は準備中です。原文の説明を表示しています。

Decode an insurance claim denial letter — what the cited reason actually means, whether it's commonly overturnable, and the appeal letter that answers it point by point. Use when someone asks 'my insurance claim was denied what do I do', 'decode this denial letter', 'can I appeal this denial', or 'write my insurance appeal'. Produces the denial decode with overturn-likelihood framing, the evidence checklist, the point-by-point appeal letter, and the escalation ladder past the insurer.

日本語の概要は準備中です。原文の説明を表示しています。

Get a bank fee waived or refunded — overdraft, late, maintenance, ATM, or foreign-transaction — with the ask written and the leverage that works. Use when asked to get a bank fee refunded, waive my overdraft fee, the bank charged me a fee, or how to get charges reversed. Produces a read on which fees are commonly reversible, the script to request a refund (in person, chat, or call), the loyalty/first-time/error leverage to use, and how to prevent the fee recurring — plus when to escalate or switch banks.

日本語の概要は準備中です。原文の説明を表示しています。

Categorized catalog of common Squad operations. Coordinator reads this file and presents it as an interactive menu when the user asks for available commands or help.

日本語の概要は準備中です。原文の説明を表示しています。

Help users design, execute, and analyze product experiments to validate hypotheses and measure true incremental impact while avoiding common statistical pitfalls.

日本語の概要は準備中です。原文の説明を表示しています。

Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission. Use when preparing an app for App Store review, after receiving a rejection from Apple, or when auditing metadata, subscriptions, privacy manifests, entitlements, or design compliance. Integrates with the asc CLI for metadata inspection.

日本語の概要は準備中です。原文の説明を表示しています。

Behavioral guardrails for Codex coding work based on common user complaints. Use when Codex is asked to implement, modify, debug, review, test, or operate on a codebase and should avoid unsafe scope expansion, stale edits, fake completion, brittle edits, shallow debugging, superficial patch-on fixes, one-off special-case code, short-term design choices that hurt maintainability, blindly following incorrect user assumptions, poor dependency choices, generic product or UI output, over-mocked tests, noisy approvals, verbose status reports, or leaking internal reasoning into project artifacts or user-facing UI.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-launch and pre-commit audit for vibe coding projects. Use when asked to check whether a project is ready to ship, deploy, merge, or commit, especially for common AI-built app mistakes: broken project structure, committed secrets or cache files, environment variable hygiene, database migrations, ORM/schema drift, unsafe raw SQL, unused legacy code, dead routes/components, weak auth, missing tests, build failures, and deployment footguns.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow on macOS (Apple Mail, Calendar, Reminders). Powered by LMCP.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks "what's on my plate today", "catch me up", "morning brief", or wants a summary of their day across calendar, reminders and email. The single most common multi-step automation. Powered by LMCP on macOS and Windows.

日本語の概要は準備中です。原文の説明を表示しています。

Hreflang and international SEO audit, validation, and generation. Detects common mistakes, validates language/region codes, and generates correct hreflang implementations. Use when user says "hreflang", "i18n SEO", "international SEO", "multi-language", "multi-region", or "language tags".

日本語の概要は準備中です。原文の説明を表示しています。

Backlink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.

日本語の概要は準備中です。原文の説明を表示しています。

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

日本語の概要は準備中です。原文の説明を表示しています。

Use when running and reporting the statistical analysis for an Academy of Management Journal (AMJ) manuscript — measurement validity, common-method bias, the right estimator (HLM, SEM, panel, experiments), endogeneity, and robustness. Executes and reports the analysis; it does not design the study (amj-methods) or frame the contribution (amj-contribution-framing).

日本語の概要は準備中です。原文の説明を表示しています。

For founders who don't know where to start with paid ads. Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels to start with and provides a 90-day ramp plan. Prevents the common mistake of spreading a small budget across too many platforms.

日本語の概要は準備中です。原文の説明を表示しています。

Entity Framework Core best practices including NoTracking by default, query splitting for navigation collections, migration management, dedicated migration services, and common pitfalls to avoid.

日本語の概要は準備中です。原文の説明を表示しています。

Write UI tests for Blazor applications (Server or WebAssembly) using Playwright. Covers navigation, interaction, authentication, selectors, and common Blazor-specific patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Common steps for building multi-layer system architecture models using System Composer. Use when implementing architecture models or when interacting with interface dictionaries, allocation sets, stereotypes, and requirements for architecture components.

日本語の概要は準備中です。原文の説明を表示しています。

Three modes for CS-conference papers (CVPR/ICCV/ECCV vision, ACL/EMNLP/NAACL NLP, ICLR/NeurIPS/ICML/AAAI ML). DIRECT-EDIT mode (common): the user describes a change in Chinese or English and the manuscript (LaTeX or Markdown) is edited directly through a CS-venue writing toolkit with author sign-off (use for 改这段 / 把中文想法写成 latex / polish / de-AI / translate / compress a passage). REVIEW mode (occasional, pre-submission): harden the paper through an adversarial courtroom review engine (N holistic domain reviewers / contestability routing / two-sided trial / three-way verdict / clerk-converged multi-round loop) with consensus-gated, author-signed revisions (use for review / critique / 审稿 / 评审 / mock-review). AUTO mode (unattended, opt-in via /goal): run the review-revise loop toward a verifiable goal, applying safe fixes under a drift-bounded policy and queueing risky ones. Resolves all inputs at runtime, no hardcoded paths. Not a from-scratch drafter (use ml-paper-writing) and not an official-venue rebuttal.

日本語の概要は準備中です。原文の説明を表示しています。