185건 · 관련도순
AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured cross-review protocol between specialized agents. Ensures scope alignment, priority calibration, and domain-aware feedback. Use when one agent reviews another's work, during handoffs, or when validating cross-cutting concerns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a short release note people finish reading. Picks the few changes a user will notice from the pull requests since the last release, names each by what the reader can now do, keeps to a length budget, writes every language from the intent instead of translating, and traces every line to a PR. Use when cutting a release, or filling a GitHub Release body, a store "what's new", a package changelog or an in-app what's new screen. Triggers - "write the release notes", "release notes for 0.4.0", "what's new", "changelog for this release", "notes de version".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review the EF Core migrations a release (or a PR) carries against how Voxt is deployed: a rolling update whose new pods wait for the migration Job, while old pods keep serving. Use before cutting a release branch, before merging a PR that adds a migration, or when the user says "check the migrations", "are the migrations safe to ship", "expand/contract check", "/migration-release-check". Reports risks; never blocks, edits or runs anything on prod.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when cutting a release, writing a CHANGELOG entry, or summarizing what changed since a tag — when the repo's commits follow (or mostly follow) Conventional Commits and a mechanically-accurate section breakdown beats a model's reading of the diff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when opening, merging, or releasing a PR for imp - branching off main, `gh pr create`, enabling auto-merge, writing the PR body or a CHANGELOG entry, cutting a tagged release (version bump + CHANGELOG + tag + GitHub release). Symptoms - "PR stuck BLOCKED", "my last commit didn't land on main", "which check is required", "how do I cut a release", "auto-merge merged too early", "check-release failed", "STALE.md blocks git pull". Do NOT use for build/test mechanics (building-and-testing) or perf measurement / baseline refresh (benchmark-cuda).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Central dispatcher for the canvas/state render fleet. Routes intent to a specialist (`/mycelium:diamond-render`, `/mycelium:ost-render`, `/mycelium:cycle-render`) OR lists what's renderable. Cross-cutting views spanning multiple canvases (opp→sol→cycle traceability, confidence-over-time, cluster-graduation-flow) are research-gated and NOT emitted by default. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update an ADR under `docs/ADR/` for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts. Use when the user asks to write, update, or document an ADR, record a design decision, capture architecture trade-offs, or justify a repo-wide technical policy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Updates a project changelog with entries for changes since the branch diverged from main. Use when about to open a PR, cutting a release, or when the user asks about changelog, release notes, or migration notes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ASP.NET Core web framework conventions: Minimal API vs MVC controllers, Program.cs composition, DI lifetimes (Scoped/Singleton/Transient), Options pattern with IOptions<T>, middleware ordering (HTTPS redirect → routing → authentication → authorization), model binding and validation (FluentValidation / DataAnnotations), ProblemDetails error handling, structured logging with ILogger<T>, configuration layering (appsettings.json + environment variables + User Secrets), and health checks. Works alongside csharp-foundation:csharp-conventions and aspnet-core-plugin:efcore-patterns. Use this skill to: - Compose Program.cs correctly — register services, configure middleware in the right order, map endpoints. - Apply the Options pattern to avoid passing raw IConfiguration into services. - Write Minimal API endpoint groups with typed results and authorization. - Handle cross-cutting errors uniformly with ProblemDetails. - Configure structured logging and health checks for production readiness. Do NOT use this skill for: - EF Core entity configuration and migrations — see aspnet-core-plugin:efcore-patterns. - C# language idioms — see csharp-foundation:csharp-conventions. - Testing — see csharp-foundation:dotnet-testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Polish cut gemstones to final finish using progressive abrasive sequences. Covers pre-polish sanding, polishing compounds, lap selection, and quality assessment for both cabochons and faceted stones. Use when a cabochon or faceted stone has completed cutting and is ready for polishing, selecting the correct compound and lap for a specific species, troubleshooting a polish that will not reach full lustre (orange peel, haze, scratches), or re-polishing a stone with surface wear.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify gemstones using optical properties, physical tests, and inclusion analysis. Covers refractive index, specific gravity, pleochroism, spectroscopy indicators, and common simulant detection. Use when identifying an unknown gemstone, verifying a seller's claim about species identity, distinguishing natural stones from simulants or synthetics, building gemological literacy through structured observation, or identifying rough material before cutting to ensure safe handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when choosing a linker, fixing link order or undefined symbol errors, enabling LTO or ThinLTO, or cutting dead code with --gc-sections. Not for inspecting the linked binary: use elf-inspection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when cutting, debugging, or verifying a pythinker-code (TSC monorepo) release — changesets flow, the ci release-packages version PR, release.yml anatomy, npm Trusted Publishing OIDC, native assets, brew tap, CDN redeploy, and their failure modes. Invoked by /release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding cross-cutting concerns to durable functions — structured logging or tracing across all functions, error tracking with Sentry, payload encryption for sensitive data, dependency injection of clients (DB, Stripe, etc.) into function handlers, custom telemetry, or behavior that should apply uniformly across many functions. Covers Inngest middleware lifecycle, creating custom middleware, dependencyInjectionMiddleware, @inngest/middleware-encryption, @inngest/middleware-sentry, and custom middleware patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master cloud storage: provider choice, sync vs. backup, sharing, storage tiers, and cost control. Use when organizing cloud files, cutting storage costs, or designing team storage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured cross-review protocol between specialized agents. Ensures scope alignment, priority calibration, and domain-aware feedback. Use when one agent reviews another's work, during handoffs, or when validating cross-cutting concerns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Shows you how to use Cowork's parallel workers to run multiple tasks at the same time instead of one after another — dramatically cutting the time on batch work. For processing large batches of files or research tasks, when running multiple independent analyses simultaneously, or during a performance optimization session. Use when the user says "speed up", "parallel workers", "batch task", "process multiple files", "why is cowork so slow", "faster", "do several things at once", or "can cowork multitask".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting concern like error handling, or the whole codebase. This includes requests to "review my changes", "check this code", "audit for best practices", "look for issues", "what's wrong with this", or "flag anything that could bite us". Use it even when the user doesn't say "review" explicitly but is asking you to find problems, inconsistencies, or anti-patterns in existing Rust code. Do NOT use for requests to write, fix, refactor, test, explain, or implement code — only for evaluating existing code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan version scope, verify release integrity (commit↔CHANGELOG, tag↔artifacts), generate changelogs, and run full releases. Use when cutting a release or bumping a version. Trigger on "cut a release", "bump the version", "generate changelog", "release plan", "verify the release".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Holistic project audit across endpoints, versions, docs, security, quality, CI, and library dimensions. Use when checking overall project health or running a periodic cross-cutting audit. Trigger on "project health", "audit the project", "health check", "is this project in good shape".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.