クラウド、CI/CD、監視、デプロイ（7,261 件）
Agno AI agent framework - build production-ready agents, multi-agent teams, workflows, MCP integrations, and deploy with AgentOS. Use when building, debugging, or learning about Agno agents.
日本語の概要は準備中です。原文の説明を表示しています。
セッション内容を CSA ペルソナ（日本マイクロソフト Cloud Solution Architect）視点で X 投稿用にフォーマル変換。Microsoft / Azure 中心、絵文字なし、ハッシュタグ付き。ニュース起点の投稿生成は generate-news-x-posts、短文リライトは rewrite-x-post を使う
Guide Maestro's Azure Boards and Repos task/PR identity and connection requirements while identifying Orchestra's currently unavailable Azure DevOps tracker operations.
日本語の概要は準備中です。原文の説明を表示しています。
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
日本語の概要は準備中です。原文の説明を表示しています。
Route Maestro issue-to-task-to-PR work through Orchestra's configured GitHub, Linear, Jira, or Azure DevOps integration and report connection and workflow gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-release checklist for Forge — runs verify, checks version bump, changelog, docs, and docker build. Use before tagging v*.
日本語の概要は準備中です。原文の説明を表示しています。
Keep paperclip-docs in lockstep with the parent paperclipai/paperclip codebase. Detects code-surface changes (CLI, env vars, API routes, adapters, plugin SDK, schemas) and produces friendly-tutorial-voice doc updates. Two modes — `nightly` (tracks parent's default branch (currently `master`), targets the `nightly` branch, preview deploy) and `release` (on parent tag, merges nightly → main, tags, ships live). Trigger phrases: "sync docs", "update docs from paperclip", "/sync-docs", "check for paperclip changes", "is docs current".
日本語の概要は準備中です。原文の説明を表示しています。
One-line-prompt → cinematic, gorgeous, functional, well-tested, deployed website. Pre-hydrated SPA + full PWA kit + JSON-LD rich snippets + third-party integrations. React 19+Vite default (Angular optional). 100 concrete improvements grouped into 10 categories that EVERY single-prompt site build must satisfy before being marked done. Trigger whenever the user says 'make a website for X', 'build a site for X', 'rebuild X.com', or any equivalent one-liner.
日本語の概要は準備中です。原文の説明を表示しています。
Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.
日本語の概要は準備中です。原文の説明を表示しています。
The consolidated, world-class Cloudflare + integrations reference — CF platform/data/AI-edge patterns, media pipeline, observability/growth, payments, and the site-generation pipeline. The non-inferable choices that build the greatest web apps.
日本語の概要は準備中です。原文の説明を表示しています。
Cloudflare-first platform selection. Decision trees for Workers, D1, R2, KV, DO, Queues, Vectorize, Containers, Sandboxes, Flagship, Agent Memory, Workflows v2. Default stack, override conditions, auth, data patterns, reliability.
日本語の概要は準備中です。原文の説明を表示しています。
How every delivered app ships and stays up — Cloudflare-first hosting, prod-only (no staging), the deploy→prod-verify loop, atomic deploy + rollback.
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Break complex work into bounded Codex delegation tasks with clear ownership, expected outputs, and integration checkpoints.
日本語の概要は準備中です。原文の説明を表示しています。
[Alpha] Experimental Azure environment builder for infrastructure and deployment design. Use when building Azure infrastructure, generating Bicep with AVM modules, deploying apps to App Service/AKS/Container Apps, designing Hub-Spoke/AKS/AI Foundry architectures, or creating low-cost Azure operations demos.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate Azure incidents and service degradations with a read-only workflow using Azure CLI, Resource Health, Activity Log, metrics, resource logs, and official Microsoft docs. Use when troubleshooting Azure outages, Resource Health alerts, Azure Firewall or DNS failures, ExpressRoute or BGP instability, VM availability problems, AKS incidents, App Service failures, database connectivity issues, Entra ID sign-in problems, load balancer issues, platform-vs-workload cutover, or drafting a troubleshooting report. Triggers on 'Azure トラブルシューティング', '障害調査', '切り分け', 'Resource Health', '復旧確認', 'Azure Firewall', 'DNS', 'ExpressRoute', 'VPN Gateway', 'BGP', 'AKS', 'App Service', 'SQL', 'PostgreSQL', 'Cosmos DB', 'Entra ID', 'incident', 'degraded', 'unavailable'.
日本語の概要は準備中です。原文の説明を表示しています。
Mosaic environment-sensitive areas (tenant name, user avatar, subscription name / ID, resource group, internal hostnames) on Azure Portal screenshots before publishing to blogs, Qiita, Medium, slides, or demos. Use when sanitizing screenshots, masking env info, or preparing portal captures for public sharing. Keywords: Azure Portal, screenshot, mask, mosaic, sanitize, tenant, subscription, public publishing, blur, redact.
日本語の概要は準備中です。原文の説明を表示しています。
Generate draw.io editable diagrams (.drawio, .drawio.svg) from text, images, or Excel. Orchestrates 3-agent workflow (Analysis → Manifest → SVG generation) with quality gates. Use when creating architecture diagrams, flowcharts, sequence diagrams, or converting existing images to editable format. Supports Azure/AWS cloud icons. Triggers on draw.io, drawio, ダイアグラム, アーキ図, フローチャート, シーケンス図.
日本語の概要は準備中です。原文の説明を表示しています。
Build and validate Azure infrastructure in a lab or sandbox using Azure CLI and official Microsoft docs. Use when creating verification environments, provisioning hub-and-spoke VNets, VPN Gateway or ExpressRoute-adjacent validation labs, checking subscription/tenant access, debugging Azure deployment constraints, comparing before/after route behavior, or cleaning up lab resources. Triggers on 'Azure 検証', '検証環境', 'PoC', 'sandbox', 'lab', 'Azure CLI で構築', 'VPN Gateway', 'VNet peering', 'BGP', 'route validation', 'summarizedGatewayPrefixes', 'デプロイして検証', 'インフラ検証', 'Application Gateway', 'AppGW 書き換え', 'リダイレクト検証', 'NSG が自動付与'.
日本語の概要は準備中です。原文の説明を表示しています。
Build a customer-facing Azure Update PowerPoint from Azure Updates MCP results, including customer classification, Japan region stamps, UPDATE Points, speaker notes, and Verify-Pptx gate checks. Use when creating or updating an Azure Update / Azure アップデート customer deck, bootstrapping a new Azure Update PPTX workspace, reviewing Deploy Region support, or re-applying manifest JSON to an existing deck.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Azure environment monthly report (Markdown + PowerPoint) from Azure Advisor and Cost Management API. Use when creating Advisor recommendations report, cost trend analysis, or security/reliability assessment for a customer subscription. Triggers on 'Advisor report', 'Azure monthly report', 'subscription report', 'Azure環境レポート', '簡易月次レポート'.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy, run, list, or tear down the agents in this repo's .managed-agents/ folder on Anthropic Managed Agents. Use when the user says "deploy my agents", "ship this agent to the cloud", "run the deployed agent", or asks about managed-agent deployment.
日本語の概要は準備中です。原文の説明を表示しています。
houtu-dependencies enterprise-grade Spring Cloud microservice foundational framework complete usage guide. GroupId is io.github.lujiafa, covering unified response, exception handling, parameter parsing, session authentication, permission control, signature verification, anti-replay, distributed lock, rate limiting, database field encryption, config decryption, access logging, canary routing, weighted load balancing, Feign enhancement, Sentinel circuit breaking, service discovery, Swagger documentation, crypto utilities, HTTP client, monitoring metrics, and other enterprise-grade capabilities. When the project build file (pom.xml or build.gradle/build.gradle.kts) contains io.github.lujiafa or houtu-related dependencies, or when the user mentions houtu or houtu-dependencies, this Skill must be read and code must be generated strictly following framework conventions. Even if the user is simply doing regular Spring Boot development (e.g., writing Controller, Service, Feign), as long as the project includes houtu, the houtu approach must be used instead of native Spring. When the user explicitly wants to use the houtu framework and the project has not yet included it, proactively add the BOM and required Starters; when the project already includes it, proactively identify and import required module dependencies based on business scenarios during coding, naturally integrating framework capabilities to enhance business services based on business semantics, rather than waiting for the user to specify each one.
日本語の概要は準備中です。原文の説明を表示しています。
Post-deploy canary monitoring. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。