mikeparcewski/integration
skills/engineering/integration/SKILL.md
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"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:27 AM230.1s27 files scanned
SKILL.md
- name:
- integration
- description:
- |
- Use when:
- API design", "service integration", "how do these communicate",
- portability:
- portable
- phase_relevance:
- ["design", "build"]
- archetype_relevance:
- ["*"]
Integration Skill
Design robust, well-documented integration points between components and services.
Purpose
Define communication contracts:
- API design (REST, GraphQL, gRPC)
- Event schema definition
- Integration pattern selection
- Error handling and resilience
Process
1. Identify Integration Points
Map communication:
- Component-to-component
- Service-to-service
- Client-to-server
- External integrations
- Event flows
2. Choose Pattern
Select approach:
- Request/Response - Sync, immediate result
- Publish/Subscribe - Async, one-to-many
- Event Sourcing - Audit trail, replay
- API Gateway - Unified entry point
3. Design Contracts
Define specifications:
- OpenAPI for REST
- GraphQL schemas
- Protocol Buffers for gRPC
- Event schemas (JSON Schema)
4. Plan Resilience
Handle failures:
- Retry strategies
- Circuit breakers
- Timeouts
- Fallback behaviors
Output
Creates in phases/design/:
design/
├── integration/
│ ├── overview.md
│ ├── api-specs/
│ │ ├── openapi.yaml
│ │ └── events.json
│ └── patterns.md
Integration Patterns
REST API
Resource-oriented, stateless, HTTP verbs. See REST API Fundamentals and Responses & Security.
GraphQL
Flexible queries, strong typing. See GraphQL guides in refs/ (graphql-graphql-basics.md, graphql-schema-design-patterns.md).
gRPC
High performance, service-to-service. See gRPC guides in refs/ (grpc-grpc-overview.md, grpc-implementation-examples.md).
Event-Driven
Async messaging, pub/sub. See event schema guides in refs/ (event-schemas-event-structure.md, event-schemas-best-practices.md).
Error Handling
Standard HTTP status codes:
- 2xx: Success (200 OK, 201 Created, 204 No Content)
- 4xx: Client errors (400, 401, 404, 409)
- 5xx: Server errors (500, 503)
See error handling guides in refs/ (error-handling-error-response-format.md, error-handling-best-practices.md).
Resilience Patterns
- Circuit Breaker - Prevent cascading failures
- Retry with Backoff - Exponential retry delays
- Timeouts - Fail fast on slow responses
- Fallbacks - Graceful degradation
See resilience guides in refs/ (resilience-circuit-breaker-pattern.md, resilience-best-practices.md).
Versioning
Common strategies:
- URL versioning:
/api/v1/resources - Header versioning:
Accept: application/vnd.api+json; version=1
See versioning guides in refs/ (versioning-versioning-strategies.md, versioning-migration-strategies.md).
Integration
With System Design
Takes component boundaries and defines:
- Interfaces between components
- Data contracts
- Communication patterns
With Data Architecture
Coordinates on:
- API data models
- Event payloads
- Serialization formats
Events
[arch:contract:defined:success]- API contract created[arch:api:validated:success]- API spec validated[arch:event:schema:defined:success]- Event schema documented
Tips
- API-First Design - Design before implementation
- Version from Start - Plan for evolution
- Document Well - Specs are executable docs
- Error Handling - Comprehensive error responses
- Idempotency - Make operations repeatable safely
- Security - Auth/authz from the beginning
Reference Materials
- REST API:
- Fundamentals
- Responses & Security
- GraphQL:
- Basics
- Query Examples
- Schema Design
- Error Handling
- Best Practices
- gRPC:
- Overview
- Implementation
- Metadata & Headers
- Testing
- Event Schemas:
- Event Structure
- Naming Conventions
- Best Practices
- Error Handling:
- Response Format
- Error Classes (TS)
- Retry Strategies
- Best Practices
- Resilience:
- Circuit Breaker
- Timeout & Bulkhead
- Rate Limiting
- Best Practices
- Versioning:
- Strategies
- Migration
- Breaking Changes
- OpenAPI Template
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026