1.7万 件 ・ 関連度順
概要と使いどころ
Azure App Configuration SDK for Java. Centralized application configuration management with key-value settings, feature flags, and snapshots. Triggers: "ConfigurationClient java", "app configuration java", "feature flag java", "configuration setting java", "azure config java".
日本語の概要は準備中です。原文の説明を表示しています。
Instrument browser/web apps with the Application Insights JavaScript SDK (@microsoft/applicationinsights-web). Use for Real User Monitoring (RUM) — page views, clicks, AJAX/fetch dependencies, exceptions, custom events, and browser-side GenAI agent traces correlated to backend OpenTelemetry traces. Covers SDK Loader Script and npm setup, framework extensions (React, React Native, Angular), Click Analytics, telemetry initializers, and OTel GenAI semantic conventions for agent/tool/model spans emitted from the browser.
日本語の概要は準備中です。原文の説明を表示しています。
Configures AWS Shield Advanced for enhanced Distributed Denial of Service (DDoS) protection: subscribing accounts and adding resource protections, enabling automatic application layer (layer 7) mitigation through AWS WAF, configuring health-based detection with Route 53 health checks, setting up Shield Response Team (SRT) access and proactive engagement, reviewing DDoS events and requesting cost protection credits, and aggregating resources into protection groups. Applicable when the user wants stronger DDoS protection for internet-facing resources (CloudFront, Application or Network Load Balancers, Elastic IP addresses, Global Accelerator, or Route 53 hosted zones), wants expert help during an attack, or wants to recover attack-driven scaling charges. Routes to the right per-task procedure in references. Not applicable for authoring AWS WAF rules (waf skill), creating Route 53 health checks (route53 skill), or org-wide Shield Advanced rollout with Firewall Manager (firewallmanager skill).
日本語の概要は準備中です。原文の説明を表示しています。
Configures AWS WAF to filter web traffic: creating web access control lists (web ACLs) on CloudFront, Application Load Balancers, API Gateway, and AppSync; AWS Managed Rules tuned in Count mode; rate-based rules for HTTP floods; IP set and geographic match rules; Bot Control (Common and Targeted); turning bot labels into a confidence signal; stripping spoofed inbound x-amzn-waf-* headers; recovering the real client IP behind a CDN; Fraud Control (account takeover and account creation fraud prevention); and logging and request sampling. Use when the user wants to protect a web application or API from common exploits, bots, credential stuffing, fake-account creation, or HTTP floods at the application layer (layer 7). Routes to the right per-task procedure in references. Do NOT use for L3/L4 DDoS protection (shieldadvanced skill), multi-account WAF rollout (firewallmanager skill), CloudFront configuration (cloudfront skill), or Route 53 health checks or records (route53 skill).
日本語の概要は準備中です。原文の説明を表示しています。
Guides the end-to-end AWS resilience lifecycle integrating Resilience Hub v2, Fault Injection Service, and Application Recovery Controller. Covers the Define → Test → Operate workflow: from policy creation through failure mode assessment, to FIS experiment validation, to ARC operational controls. Applicable when the user wants a complete resilience strategy, needs to connect findings to experiments to controls, or is planning a resilience program. Also applicable for the meta question of whether marking NGRH findings as resolved is enough, whether they are "done" after resolving findings, or how to validate findings before resolving them. Not applicable for resolving or remediating a specific individual finding (see resilience-hub-failure-mode-assessment), or when a single service is explicitly named (e.g. "what FIS experiment should I run").
日本語の概要は準備中です。原文の説明を表示しています。
Designs a resilience program: how to structure and standardize resilience policies across an organization, team, or portfolio (tiered policy model with availability/RTO/RPO targets and DR approach selection), and how often to run resilience activities (operational cadence). Applies when the user asks how to structure policies org-wide, what tiers/targets to set, which DR approach fits a tier, or how frequently to run assessments, FIS experiments, GameDays, or autoshift practice. Does not apply to creating or configuring a specific policy or resource for a single workload (use resilience-hub-getting-started), to step-by-step lifecycle execution (see aws-resilience-lifecycle), or to service-specific setup.
日本語の概要は準備中です。原文の説明を表示しています。
Configures AWS Application Recovery Controller (ARC) for operational resilience: routing controls with safety rules for cross-Region failover, and zonal shift / zonal autoshift for AZ-impairment recovery. Applies when setting up failover routing, configuring safety rules, enabling zonal shift, or configuring zonal autoshift with practice runs. Also applies when shifting traffic out of a specific Availability Zone (AZ) for an ALB/NLB or other resource. For a broader "an AZ is impaired, what is my response across services" question, see aws-resilience-lifecycle. Does not apply to Resilience Hub setup or FIS experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Provides verified corrections for IAM behaviors that AI agents frequently get wrong — policy evaluation edge cases, trust policy gotchas, STS session limits, Organizations quirks, and SAML/MFA specifics. Also provides structured workflows for IAM role management and baseline policy generation from application source code or a Terraform plan JSON. Covers condition operator safety (ForAnyValue/ForAllValues with Null checks), bucket policy deny patterns (VPC endpoint restrictions, org paths), confused deputy protection, and service role creation for AWS services (Glue, CloudTrail, Lambda, ECS, etc.) with aws:SourceAccount/aws:SourceArn trust conditions. Applies when creating IAM roles, writing IAM or bucket policies, generating policies from application source code or a Terraform plan JSON, working with STS, Organizations, or condition operators, or any task needing a service or execution role. Does not cover non-IAM authorization like Cognito user-pool policies or app-level RBAC.
日本語の概要は準備中です。原文の説明を表示しています。
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run/install/screenshot my app', 'I'm on Linux/Cursor and need an iOS device', 'no sim on this box / headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud/remote/shareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build/Update, web preview, or physical devices.
日本語の概要は準備中です。原文の説明を表示しています。
Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use eas-app-stores.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor Apple Notes changes using file system events and Shortcuts triggers. Trigger: "apple notes events".
日本語の概要は準備中です。原文の説明を表示しています。
Migrate Apple Notes automation scripts between macOS versions. Trigger: "apple notes upgrade migration".
日本語の概要は準備中です。原文の説明を表示しています。
Reference architecture for Apple Notes automation systems. Trigger: "apple notes architecture".
日本語の概要は準備中です。原文の説明を表示しています。
Monitor Apple Notes automation health and performance metrics. Trigger: "apple notes monitoring".
日本語の概要は準備中です。原文の説明を表示しています。
Migrate notes between Apple Notes, Obsidian, Notion, and other platforms. Trigger: "apple notes migration".
日本語の概要は準備中です。原文の説明を表示しています。
Deploy AppFolio integration service to cloud infrastructure. Trigger: "deploy appfolio".
日本語の概要は準備中です。原文の説明を表示しています。
Set up local development for AppFolio property management API integration. Trigger: "appfolio local dev".
日本語の概要は準備中です。原文の説明を表示しています。
Handle AppFolio API rate limits with throttling and backoff. Trigger: "appfolio rate limit".
日本語の概要は準備中です。原文の説明を表示しています。
Optimize Apple Notes automation performance for large note collections. Trigger: "apple notes performance".
日本語の概要は準備中です。原文の説明を表示しています。
Collect AppFolio API debug evidence for support tickets. Trigger: "appfolio debug".
日本語の概要は準備中です。原文の説明を表示しています。
Deploy Apple Notes automation as a local macOS service. Trigger: "apple notes deploy".
日本語の概要は準備中です。原文の説明を表示しています。
Migrate between AppFolio API versions and handle endpoint changes. Trigger: "appfolio upgrade".
日本語の概要は準備中です。原文の説明を表示しています。
Production checklist for Apple Notes automation deployments. Trigger: "apple notes production checklist".
日本語の概要は準備中です。原文の説明を表示しています。
Implement access control for multi-user Apple Notes automation. Trigger: "apple notes access control".
日本語の概要は準備中です。原文の説明を表示しています。