161건 · 관련도순
Patterns for designing, building, and operating microservices architectures. Covers service decomposition, inter-service communication, resilience patterns, data consistency, and observability in distributed systems. Use when ", " mentioned.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert guide for microservices, message queues, Event Sourcing, and high-scale backend architectures / Panduan ahli untuk arsitektur microservices, antrean pesan, dan backend skala tinggi.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level fullstack development guide covering multi-language (TypeScript, Python, Go, Rust), API design (OpenAPI 3.1, gRPC), microservices, system design patterns, and polyglot architecture / Panduan fullstack tingkat ahli mencakup multi-bahasa, desain API, microservices, dan arsitektur polyglot.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Service-oriented and microservices architecture patterns for cloud-scale systems. Covers service boundaries, API versioning and backward compatibility, eventual consistency at the API layer, idempotency keys, saga and choreography patterns, bulkheads, circuit breakers, service meshes, and the Vogels "you build it, you run it" operating principle. Use when designing service decomposition, API contracts, inter-service communication, or reviewing a proposed microservices architecture for coupling and resilience.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GraphQL, WebSockets, and microservices patterns for NestJS. Apply only when the relevant package is in dependencies (`@nestjs/graphql`, `@nestjs/websockets`, `@nestjs/microservices`). Each section is orientation, not exhaustive — defer to NestJS docs for deep dives. Use this skill to: - Wire a GraphQL resolver (code-first) with class-validator inputs. - Build a WebSocket gateway with auth and room management. - Set up a microservice transport (TCP/RabbitMQ/NATS/Redis/Kafka) and message handlers. Do NOT use this skill for: - REST controllers (see nest-conventions + decorator-patterns). - ORM (see nest-data-layer). - Auth strategies (see security-analyst phase guidance).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration, Java REST API design, or Microservices Java architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems. Invoke for goroutines, channels, Go generics, gRPC integration, CLI tools, benchmarks, or table-driven testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Microservices design expert covering service decomposition, communication patterns, and distributed systems
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration, Java REST API design, or Microservices Java architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
スキルを作成・更新・プロンプト改善するためのメタスキル。 **collaborative**モードでユーザーと対話しながら共創し、 抽象的なアイデアから具体的な実装まで柔軟に対応する。 **orchestrate**モードでタスクの実行エンジン（Claude Code / Codex / 連携）を選択。 Anchors: • Continuous Delivery (Jez Humble) / 適用: 自動化パイプライン / 目的: 決定論的実行 • The Lean Startup (Eric Ries) / 適用: Build-Measure-Learn / 目的: 反復改善 • Domain-Driven Design (Eric Evans) / 適用: ユビキタス言語 / 目的: 一貫した語彙 • Design Thinking (IDEO) / 適用: ユーザー中心設計 / 目的: 共感と共創 • Microservices Patterns (Richardson) / 適用: サービス委譲 / 目的: 疎結合な連携 Trigger: 新規スキルの作成、既存スキルの更新、プロンプト改善を行う場合に使用。 スキル作成, スキル更新, プロンプト改善, skill creation, skill update, improve prompt, Codexに任せて, assign codex, Codexで実行, GPTに依頼, 実行モード選択, どのAIを使う
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design AWS applications that run without managing servers and respond to events. Get guidance on Lambda APIs, asynchronous workflows, retries, monitoring, and scaling, with implementation patterns based on the AWS Well-Architected Framework.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan backend architecture using Clean Architecture, Hexagonal Architecture, or Domain-Driven Design. Clarify business boundaries, choose a suitable structure, define how modules depend on each other, and outline migration steps and validation checks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Integrate cryptocurrency exchanges into Go applications with CCXT. Follow examples for market data, order management, authentication, and error handling, using REST for individual requests and WebSocket streams to monitor prices, order books, balances, and orders.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build Node.js APIs and backend services with Express/Fastify. The skill guides authentication, database integration, error handling, and operational practices such as logging and health checks, which report whether a service is working.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and implement Saga workflows across services, using compensating actions to undo completed work after failures. Define step deadlines, handle repeated messages safely, and monitor stalled order, booking, or other long-running processes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan backend services and APIs, from service responsibilities and interface definitions to authentication, failure handling, monitoring, and rollout. Produces architecture diagrams, API specifications, and documented tradeoffs based on business and operational requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize Node.js, Express, and TypeScript APIs into layers with clear responsibilities. This guide covers request handling, business logic, database access, input validation, error tracking, configuration, and testing to support consistent implementation and refactoring across services.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan Azure infrastructure around application needs, scale, and budget. Generate Bicep templates, files that define cloud resources as code, then review estimated costs, configure deployment pipelines, and check security settings before production.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and implement Google Cloud serverless web apps with separate presentation, application, and data layers. Produces architecture diagrams, Terraform infrastructure code, deployment instructions, and validation scripts for private networking and controlled access between layers.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.