1,484 件 ・ 関連度順
概要と使いどころ
Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines. Use PROACTIVELY for content review.
日本語の概要は準備中です。原文の説明を表示しています。
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
日本語の概要は準備中です。原文の説明を表示しています。
.NET testing fundamentals overview and navigation center. Triggered when users ask about "how to write .NET tests", ".NET testing getting started", "required testing tools", "testing best practices", "learn testing from scratch", and other general testing needs. Recommends appropriate sub-skills based on specific requirements, covering testing fundamentals, test data, assertions, mocking, special scenarios, and other 19 fundamental skills. Keywords: dotnet testing, .NET testing, testing getting started, how to write tests, testing best practices, unit test, unit test, xunit, 3A pattern, FIRST principle, assertion, assertion, mock, stub, NSubstitute, test data, AutoFixture, Bogus, validator, FluentValidation, TimeProvider, IFileSystem, code coverage, ITestOutputHelper, test naming
日本語の概要は準備中です。原文の説明を表示しています。
.NET advanced testing skills overview and navigation center. Triggered when users ask about "integration testing", "API testing", "containerized testing", "microservice testing", "test framework migration", "Testcontainers", "Aspire testing", and other advanced testing needs. Recommends appropriate sub-skills based on specific requirements, covering integration testing, Testcontainers, Aspire testing, framework upgrades, and other 8 advanced skills. Keywords: integration testing, integration testing, API testing, advanced testing, advanced testing, testcontainers, aspire testing, WebApplicationFactory, TestServer, database test, database testing, EF Core test, MongoDB test, Redis test, Docker test, container testing, microservice test, microservice testing, .NET Aspire, xUnit upgrade, TUnit, framework migration
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Build a minimal context pack and recommend the correct specialist path for token-efficient execution. Use when the task is non-trivial, spans multiple domains, or should reduce token usage before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
日本語の概要は準備中です。原文の説明を表示しています。
Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.
日本語の概要は準備中です。原文の説明を表示しています。
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and improve the internal link structure of an AEM Edge Delivery Services site. Builds a link graph from the query index and page content, identifies orphan pages, hub pages, and content silos, and generates specific linking recommendations with suggested anchor text and placement. Use when improving site navigation, fixing orphan pages, strengthening topical authority, or auditing link equity distribution.
日本語の概要は準備中です。原文の説明を表示しています。
Structure source-grounded consulting-style analysis for strategy, market, product, operations, or decision memos. Use for MECE problem framing, hypotheses, options, tradeoffs, executive recommendations, or "consulting analysis" requests; do not use for legal/financial advice, implementation, data computation, chart rendering, or unsourced business claims.
日本語の概要は準備中です。原文の説明を表示しています。
PR test analysis routing. Use for pull request or diff test impact, changed-test review, CI failure interpretation, and focused test matrix recommendations; do not use for general code review or editing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes and optimizes SQL queries using EXPLAIN plans, index recommendations, query rewrites, and performance benchmarking. Use for "query optimization", "slow queries", "database performance", or "EXPLAIN analysis".
日本語の概要は準備中です。原文の説明を表示しています。
Audits database schemas for naming conventions, type consistency, nullability patterns, and missing constraints. Provides violations report with recommended fixes. Use for "schema validation", "database linting", "schema standards", or "consistency checks".
日本語の概要は準備中です。原文の説明を表示しています。
Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns. Provides state machine approach recommendations, loading skeletons, error boundaries, and empty state components. Use when implementing "loading states", "error handling", "empty states", or "state machines".
日本語の概要は準備中です。原文の説明を表示しています。
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
日本語の概要は準備中です。原文の説明を表示しています。
Audits project dependencies for outdated packages, duplicates, heavy/problematic libraries, security vulnerabilities, and risky version combinations. Generates prioritized reports with security, performance, and maintainability insights, upgrade paths, and safe pinning recommendations. Use when users request dependency audits, package updates, security checks, or dependency optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Identifies domain modules, ownership boundaries, dependencies, and interfaces using Domain-Driven Design principles. Provides domain maps, bounded contexts, refactor recommendations. Use for "DDD", "domain modeling", "bounded contexts", or "service boundaries".
日本語の概要は準備中です。原文の説明を表示しています。
Reduces LLM costs and improves response times through caching, model selection, batching, and prompt optimization. Provides cost breakdowns, latency hotspots, and configuration recommendations. Use for "cost reduction", "performance optimization", "latency improvement", or "efficiency".
日本語の概要は準備中です。原文の説明を表示しています。
Estimates infrastructure needs based on traffic forecasts, workload analysis, and performance requirements with sizing recommendations and cost trade-offs. Use for "capacity planning", "infrastructure sizing", "resource estimation", or "scalability planning".
日本語の概要は準備中です。原文の説明を表示しています。
Reviews authentication and authorization implementation for session management, CSRF, cookie security, and auth flow vulnerabilities with findings, severity assessment, and fix recommendations. Use for "auth review", "session security", "CSRF protection", or "authentication audit".
日本語の概要は準備中です。原文の説明を表示しています。
Installs and configures Prettier, ESLint, EditorConfig, and other code quality tools to enforce consistent code style across the team. Generates config files, npm scripts, editor settings recommendations, and CI integration suggestions. Use when users request "setup prettier", "add eslint", "configure code formatting", or "enforce code style".
日本語の概要は準備中です。原文の説明を表示しています。
Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is 'external red team for an enterprise client' (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.
日本語の概要は準備中です。原文の説明を表示しています。