Audits SaaS, cloud, payment, and AI spend. Use when analyzing bills, right-sizing plans, sizing Savings Plans or CUDs, cutting payment-processing fees, or LLM self-host breakeven.
日本語の概要は準備中です。原文の説明を表示しています。
171 件 ・ 関連度順
概要と使いどころ
Audits SaaS, cloud, payment, and AI spend. Use when analyzing bills, right-sizing plans, sizing Savings Plans or CUDs, cutting payment-processing fees, or LLM self-host breakeven.
日本語の概要は準備中です。原文の説明を表示しています。
LLM serving for latency, batching, caching, quantization, and routing. Use when tuning vLLM or SGLang, sizing KV cache, adding speculative decoding, or cutting serving cost.
日本語の概要は準備中です。原文の説明を表示しています。
Verifying YAGNI, cutting scope, and proposing complexity reductions. A 'subtraction' agent questioning the justification for every feature, dependency, doc, and config. Does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Detecting unnecessary files, unused code, and orphaned files, and proposing safe deletion. Not for removal execution (Builder), repo structure (Grove), or scope cutting (Void).
日本語の概要は準備中です。原文の説明を表示しています。
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
日本語の概要は準備中です。原文の説明を表示しています。
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist serves.
日本語の概要は準備中です。原文の説明を表示しています。
Idiomatic Go HTTP middleware patterns with context propagation, structured logging via slog, centralized error handling, and panic recovery. Use when writing middleware, adding request tracing, or implementing cross-cutting concerns.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
日本語の概要は準備中です。原文の説明を表示しています。
Expert guide for cutting-edge Native CSS (2026 Standard) — CSS Anchor Positioning, @starting-style, View Transitions Level 2, Container Queries, and :has() / Panduan ahli fitur CSS native modern 2026.
日本語の概要は準備中です。原文の説明を表示しています。
Generates MediatR Pipeline Behaviors for cross-cutting concerns like logging, validation, exception handling, caching, and performance monitoring. Implements the decorator pattern around handlers.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffolds a complete .NET solution following Clean Architecture principles with proper layer separation (API, Application, Domain, Infrastructure). Creates project structure, dependency injection setup, and cross-cutting concerns configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Bump the version, generate release notes, and publish a new skillsaw release to PyPI. Use when cutting a new release.
日本語の概要は準備中です。原文の説明を表示しています。
Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions, independently verify proposed fixes, and ship improvements in clean, focused batches. Use before cutting a release.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。