「cascade」の検索結果

Use when the user has a video + an SRT and wants the subtitles either burned into the pixels (libass, always-visible) or soft-muxed as a togglable track. Also handles the final composite step for the localization pipeline — burn subs, mix a dub track, and keep the original audio as a low-volume bed, all in ONE ffmpeg encode (no cascade). Verifies libass availability and auto-downloads a static evermeet ffmpeg build when Homebrew's stripped binary lacks it. Triggers — "烧字幕", "硬字幕", "burn subtitles", "burn-in subs", "embed subtitle", "soft mux SRT", "把字幕烧进视频", "做最终合成".

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

Use when the user has one or more video clips and wants to add post-production on top — AI-generated cover as first frame, HTML/CSS captions synced to SRT, kinetic illustration overlays at hook moments, chapter chips, end-card CTA, or any other timed motion graphics. Most often used as the downstream of `/wjs-segmenting-video` — pick up where that skill stopped (raw cropped clip + per-clip SRT) and produce the upload-ready MP4. Backed by HyperFrames so everything compiles to ONE final encode — no cascade of re-encodes. Triggers — "加封面", "加字幕", "加动画", "加 CTA", "做后期", "post-production", "title card", "kinetic captions", "end card".

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

Expert guide for intelligent model cascading and routing — complexity-scored task routing from Flash/Haiku to Sonnet/Opus/Astra, dynamic escalation with quality gates, 40-60% token cost reduction while maintaining output quality / Panduan ahli untuk kaskade dan routing model cerdas — routing tugas berbasis skor kompleksitas dari Flash/Haiku ke Sonnet/Opus/Astra, eskalasi dinamis dengan gerbang kualitas, pengurangan biaya token 40-60% dengan kualitas output terjaga.

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

Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.

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

Launches and configures the standalone presubmit CLI, an API-driven adversarial peer-review pipeline with 30-plus stages, including Red Team finders, Blue Team defence, verification cascade, legal pass, and copyedit, producing one consolidated report on disk. Verifies installation and API key, chooses the output location and smoke, standard, or custom mode, launches the run, and reports the result path. Use when the user asks to run presubmit, wants a deep unattended pre-submission audit, or needs a math or replication-code audit. Everyday self-audits go to paper-review-lite, and external refereeing to journal-review.

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

Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.

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

用户需要预测某个局部问题会如何扩散到其他部分时;当系统中一个环节出了问题需要评估连锁影响时; 当需要提前在传变路径上设防时;当用户说"这个问题会不会引发其他问题"或"如果不处理会怎样"时。 不适用于: 孤立问题不会产生连锁反应的场景;各环节完全独立的松耦合系统。

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

AI pressure redirection — handling conflicting demands, tool failures, and competing constraints by blending with incoming force then reframing. Use when receiving contradictory instructions from different sources, during tool failure cascades where the planned approach becomes unviable, when scope pressure threatens to expand the task beyond what was asked, or when user frustration or correction needs to be absorbed rather than deflected.

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

Use when reducing header bloat and compilation cascades with Include What You Use, interpreting IWYU reports, mapping files, forward declarations, or CMake integration.

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

Doctrine ORM best practices for Symfony: entity mapping as source of truth, repositories, DQL/QueryBuilder with parameters, N+1 prevention with fetch joins, relations (cascade/fetch/orphanRemoval), lifecycle events, batch processing, and generated migrations. Apply when: writing or reviewing Doctrine entities, repositories, and queries. Activated automatically by symfony-plugin/stack.md as a convention skill for the development and database phases. Do NOT use this skill for: - PHP language idioms — see php-foundation:php-conventions. - Controllers/services/forms — see symfony-plugin:symfony-conventions.

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

Entity Framework Core patterns for ASP.NET Core projects: DbContext design, code-first entity configuration (Fluent API via IEntityTypeConfiguration<T>), relations (HasOne/HasMany, cascade/restrict/set-null), indexes and unique constraints, projection to DTOs (Select + AsNoTracking), avoiding N+1 (Include, AsSplitQuery), transactions, parameterized raw SQL (FromSql with FormattableString), and connection string from IConfiguration. Works alongside aspnet-core-plugin:aspnet-conventions. Use this skill to: - Design a clean DbContext with ApplyConfigurationsFromAssembly for scalable entity registration. - Configure entity properties (column types, max length, precision, nullability) via Fluent API. - Avoid N+1 query problems with explicit Include / projection to DTOs. - Use transactions correctly for multi-entity operations. - Write parameterized raw SQL safely when LINQ is not expressive enough. Do NOT use this skill for: - Migration generation commands (that is efcore-specialist's job in the database extra phase). - ASP.NET Core middleware, DI, or validation — see aspnet-core-plugin:aspnet-conventions. - C# language idioms — see csharp-foundation:csharp-conventions.

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

ORM patterns for NestJS: TypeORM, Prisma, Mongoose. Covers entities, repositories, transactions, migrations, common pitfalls (N+1, cascade deletes, transaction boundaries). Use this skill to: - Detect which ORM the project uses and apply matching patterns. - Define entities/schemas with the right decorators. - Inject repositories or Prisma client correctly. - Run transactions at the service boundary. - Write migrations that round-trip cleanly. Do NOT use this skill for: - Module/DI patterns (see nest-conventions). - Decorator usage broadly (see decorator-patterns). - Non-ORM raw SQL (rare; flag in BLOCKERS if needed).

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

Use when writing, reviewing, refactoring, or modernizing CSS/Tailwind. Apply a policy-first approach: semantic tokens, explicit cascade order, static CSS, intrinsic component layouts, accessible state, measured performance, and progressive enhancement backed by current sources.

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

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

Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience. Masters error correlation, cascade prevention, and automated recovery strategies across multi-agent systems with focus on minimizing impact and learning from failures.

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

"Model viral spread dynamics using SIR/SIS/SEIR compartmental models. Use this skill when the user needs to predict content spread patterns, estimate viral thresholds, or model information cascades in social networks — even if they say 'will this go viral', 'epidemic model for content', or 'spread prediction'.".

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

Write and cascade OKRs (Objectives and Key Results) for company, department, team, or project level. Ensure objectives are inspiring and key results are measurable outcomes. Includes weekly check-in template. Use at the start of each quarter or when aligning strategy to execution. Do not use for KPI performance reviews or daily task tracking.

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

Anti-AI-slop design system for distinctive, premium interfaces. Bold typography, dark-first #060610, fluid clamp() type, cascade layers + native nesting + container queries, OKLCH color, @starting-style, View Transitions API, DTCG tokens.

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

Packaging React components as a consumable library — style delivery contracts, sideEffects, cascade layers, "use client" preservation, peer dependency ranges, server-safe vs client entries

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

SCSS Modules - locally scoped component stylesheets, cascade layers, the Sass module system, mixins, and build-time versus runtime values

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

三大闭环日常健检（v2.0）。快速读取系统状态文件（约1分钟），从三个层次输出健康仪表盘：①运营指标层（PENDING-EXPERIENCES/碎片积压/一致性检查日期/cascade/PENDING-SKILLS）②沙盘状态层（sandboxes/目录的 validated/draft/gap-found 分布）③D0覆盖率层（role-* Skills 有多少已有认知根行）。触发词：「三大闭环健康检查」「全系统健康报告」「整体系统健康」「三个闭环都健康吗」「三大闭环状态怎么样」。⚠️ 本 Skill 为快速只读健检，无 Full 模式。深度场景沙盘验证→skill-closure-verifier-meta；生成场景沙盘→scenario-sandbox-builder；单一Loop专项→对应专项Skill。

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

Professional CSS: cascade mastery, modern layout, custom properties, and maintainable architecture. Use when writing, reviewing, or debugging CSS.

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

Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"

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

Designing Lookup vs Master-Detail vs Hierarchical vs External relationships: cascade delete, roll-up summaries, ownership, sharing implications, polymorphic lookups, junction objects, relationship depth limits. NOT for restricting which records a lookup can pick — use admin/lookup-filter-cross-object-patterns. NOT for a roll-up across a plain lookup — use data/roll-up-summary-alternatives.

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