Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
日本語の概要は準備中です。原文の説明を表示しています。
862 件 ・ 関連度順
概要と使いどころ
Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
日本語の概要は準備中です。原文の説明を表示しています。
Query Datadog APM services, dependencies, performance, and traces with Pup.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse-engineers specifications from existing codebases, maps code dependencies, generates API documentation from source, and identifies undocumented business logic.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze codebase health metrics including complexity and dependencies
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "analyze Helm charts", "validate Helm values", "review chart structure", "check Kubernetes Helm templates", or "audit chart dependencies and configuration".
日本語の概要は準備中です。原文の説明を表示しています。
Discover and recommend **combinations** of agent skills to complete complex, multi-faceted tasks. Provides two recommendation strategies — **Maximum Quality** (best skill per subtask) and **Minimum Dependencies** (fewest installs). Use this skill whenever the user wants to find skills, asks "how do I do X", "find a skill for X", or describes a task that likely requires multiple capabilities working together. Also use when the user mentions composing workflows, building pipelines, or needs help across several domains at once — even if they only say "find me a skill". This skill supersedes simple single-skill search by decomposing the task into subtasks and assembling an optimal skill portfolio.
日本語の概要は準備中です。原文の説明を表示しています。
Convert agreed scope into a structured matter plan — phases, workstreams, milestones, dependencies, owner assignments, and matter setup decisions. Use when planning a new matter, running a kickoff, building a workstream plan, structuring phases, setting up task codes, or producing a plan to drive status reporting. Trigger on: 'build a plan', 'matter plan', 'project plan', 'what are the phases', 'workstream plan', 'how do we sequence this', 'who owns what', 'task codes', 'matter setup', 'workstream plan', 'matter plan', 'rolling wave', 'plan the next phase', 'what comes first', 'kickoff agenda'.
日本語の概要は準備中です。原文の説明を表示しています。
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Godot Expert Analyst: Anara. Visionary project scoring and certification for Godot 4.7+ architecture. Use when evaluating project health, modernity, scalability, dependency graphs, or generating Visionary Certificates. Keywords: analyst, Anara, scoring, certification, architecture audit, ResourceLoader.get_dependencies, typed Dictionary, folder-by-feature, Visionary Certificate, Godot 4.7.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temps savings", "cost comparison", "audit my stack", "am I overpaying", "saas spend", "calculate savings", "is temps cheaper".
日本語の概要は準備中です。原文の説明を表示しています。
Use when managing dependencies between systems — autoloads, service locators, @export injection, and scene injection patterns
日本語の概要は準備中です。原文の説明を表示しています。
topGO package provides tools for testing GO terms while accounting for the topology of the GO graph. Different test statistics and different methods for eliminating local similarities and dependencies between GO terms can be implemented and
日本語の概要は準備中です。原文の説明を表示しています。
SwiftUI's actual mental model — view identity, lifetime, and dependencies (the Demystify canon), state ownership decision rules, Observation's per-property tracking, body-performance discipline, and the main-actor concurrency contract. Use when state resets mysteriously, views re-render too often, animations glitch between branches, choosing @State vs @Bindable vs plain property, or debugging "why did body run."
日本語の概要は準備中です。原文の説明を表示しています。
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
日本語の概要は準備中です。原文の説明を表示しています。
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback.
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
日本語の概要は準備中です。原文の説明を表示しています。
Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review.
日本語の概要は準備中です。原文の説明を表示しています。
Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.
日本語の概要は準備中です。原文の説明を表示しています。
Prevent XSS, secure auth flows, and harden React client-side applications. Use when preventing XSS, securing auth flows, or auditing third-party dependencies in React.
日本語の概要は準備中です。原文の説明を表示しています。
Configure PHP ecosystem tooling, dependency management, and static analysis. Use when managing Composer dependencies, running PHPStan, or configuring PHP build tools.
日本語の概要は準備中です。原文の説明を表示しています。
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx-investigate).
日本語の概要は準備中です。原文の説明を表示しています。
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/skill:phx-investigate).
日本語の概要は準備中です。原文の説明を表示しています。