From wicked-garden
Design API contracts, service boundaries, and integration patterns. Define how components and services communicate and interoperate. Use when: "API design", "service integration", "how do these communicate", "API contract", "integration pattern", "REST API", "GraphQL", "event schema"
npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardenThis skill uses the workspace's default tool permissions.
Design robust, well-documented integration points between components and services.
refs/error-handling-best-practices.mdrefs/error-handling-error-classes-typescript.mdrefs/error-handling-error-response-format.mdrefs/error-handling-retry-strategies.mdrefs/event-schemas-best-practices.mdrefs/event-schemas-event-naming-conventions.mdrefs/event-schemas-event-structure.mdrefs/graphql-best-practices.mdrefs/graphql-error-handling.mdrefs/graphql-graphql-basics.mdrefs/graphql-query-examples.mdrefs/graphql-schema-design-patterns.mdrefs/grpc-grpc-overview.mdrefs/grpc-implementation-examples.mdrefs/grpc-metadata-headers.mdrefs/grpc-testing.mdrefs/openapi-template.yamlrefs/resilience-best-practices.mdrefs/resilience-circuit-breaker-pattern.mdrefs/resilience-rate-limiting.mdProvides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Design robust, well-documented integration points between components and services.
Define communication contracts:
Map communication:
Select approach:
Define specifications:
Handle failures:
Creates in phases/design/:
design/
├── integration/
│ ├── overview.md
│ ├── api-specs/
│ │ ├── openapi.yaml
│ │ └── events.json
│ └── patterns.md
Resource-oriented, stateless, HTTP verbs. See REST API Fundamentals and Responses & Security.
Flexible queries, strong typing. See GraphQL guides in refs/ (graphql-graphql-basics.md, graphql-schema-design-patterns.md).
High performance, service-to-service. See gRPC guides in refs/ (grpc-grpc-overview.md, grpc-implementation-examples.md).
Async messaging, pub/sub. See event schema guides in refs/ (event-schemas-event-structure.md, event-schemas-best-practices.md).
Standard HTTP status codes:
See error handling guides in refs/ (error-handling-error-response-format.md, error-handling-best-practices.md).
See resilience guides in refs/ (resilience-circuit-breaker-pattern.md, resilience-best-practices.md).
Common strategies:
/api/v1/resourcesAccept: application/vnd.api+json; version=1See versioning guides in refs/ (versioning-versioning-strategies.md, versioning-migration-strategies.md).
Takes component boundaries and defines:
Coordinates on:
[arch:contract:defined:success] - API contract created[arch:api:validated:success] - API spec validated[arch:event:schema:defined:success] - Event schema documented