omgkit 2.12.0 → 2.15.0

package/plugin/workflows/game-dev/prototype-to-production.md

@@ -0,0 +1,205 @@
+---
+description: Transform game prototype into production-ready code
+triggers:
+  - manual
+  - game:production
+agents:
+  - game-designer
+  - fullstack-developer
+  - tester
+---
+
+# Prototype to Production Workflow
+
+Convert rapid game prototype into maintainable production code.
+
+## Prerequisites
+- [ ] Working prototype with core mechanics
+- [ ] Game design document
+- [ ] Target platforms defined
+
+## Phase 1: Prototype Assessment
+
+### Step 1.1: Evaluate Prototype
+```yaml
+agent: game-designer
+action: assess
+evaluation:
+  - Core mechanics working
+  - Fun factor validated
+  - Technical feasibility
+  - Performance baseline
+  - Technical debt inventory
+```
+
+### Step 1.2: Define Production Requirements
+```yaml
+agent: game-designer
+action: define
+requirements:
+  - Target frame rate: 60fps
+  - Memory budget: <2GB
+  - Load time: <10s
+  - Platform requirements
+  - Accessibility features
+```
+
+## Phase 2: Architecture Refactoring
+
+### Step 2.1: Design Production Architecture
+```yaml
+agent: game-designer
+action: design
+patterns:
+  - Component system (ECS or composition)
+  - State machine for game states
+  - Event system for decoupling
+  - Object pooling for performance
+  - Asset management system
+```
+
+### Step 2.2: Create Core Systems
+```yaml
+agent: fullstack-developer
+action: implement
+systems:
+  - Game loop manager
+  - Scene management
+  - Input handling
+  - Audio manager
+  - Save/load system
+  - UI framework
+```
+
+## Phase 3: Code Migration
+
+### Step 3.1: Extract Reusable Components
+```yaml
+agent: fullstack-developer
+action: refactor
+from_prototype:
+  - Identify reusable code
+  - Extract to components
+  - Add proper interfaces
+  - Remove hardcoding
+  - Add configuration
+```
+
+### Step 3.2: Implement Production Code
+```yaml
+agent: fullstack-developer
+action: implement
+standards:
+  - Clean code principles
+  - SOLID for game code
+  - Proper error handling
+  - Logging and debugging
+  - Performance considerations
+```
+
+## Phase 4: Asset Pipeline
+
+### Step 4.1: Setup Asset Pipeline
+```yaml
+agent: fullstack-developer
+action: configure
+pipeline:
+  - Asset import settings
+  - Compression configuration
+  - LOD generation
+  - Texture atlasing
+  - Audio compression
+  - Localization support
+```
+
+### Step 4.2: Asset Organization
+```yaml
+agent: fullstack-developer
+action: organize
+structure:
+  - /Assets
+    - /Art
+    - /Audio
+    - /Prefabs
+    - /Scripts
+    - /Scenes
+    - /UI
+  - Naming conventions
+  - Folder structure guidelines
+```
+
+## Phase 5: Testing Infrastructure
+
+### Step 5.1: Unit Testing
+```yaml
+agent: tester
+action: implement
+tests:
+  - Core mechanics
+  - State machines
+  - Calculations
+  - Utility functions
+  - Data validation
+```
+
+### Step 5.2: Integration Testing
+```yaml
+agent: tester
+action: implement
+tests:
+  - Scene loading
+  - Save/load cycle
+  - Input handling
+  - Audio playback
+  - UI navigation
+```
+
+### Step 5.3: Playtest Framework
+```yaml
+agent: tester
+action: configure
+framework:
+  - Automated playthroughs
+  - Metrics collection
+  - Bug reproduction
+  - Performance profiling
+```
+
+## Phase 6: Performance Optimization
+
+### Step 6.1: Profile and Optimize
+```yaml
+agent: fullstack-developer
+action: optimize
+areas:
+  - Draw call batching
+  - Object pooling
+  - Memory management
+  - Physics optimization
+  - Script optimization
+```
+
+### Step 6.2: Platform Optimization
+```yaml
+agent: fullstack-developer
+action: optimize
+per_platform:
+  - PC settings
+  - Console optimizations
+  - Mobile considerations
+  - Quality settings system
+```
+
+## Outputs
+- [ ] Production architecture
+- [ ] Refactored codebase
+- [ ] Asset pipeline
+- [ ] Test suite
+- [ ] Performance profile
+
+## Quality Gates
+- 60fps on target hardware
+- Memory within budget
+- All tests passing
+- No critical bugs
+- Code review passed

package/plugin/workflows/microservices/contract-first.md

@@ -0,0 +1,151 @@
+---
+description: Develop APIs using contract-first methodology with consumer-driven contracts
+triggers:
+  - manual
+  - api:new
+agents:
+  - api-designer
+  - fullstack-developer
+  - tester
+---
+
+# Contract-First Development Workflow
+
+Design and implement APIs starting from contracts.
+
+## Prerequisites
+- [ ] Consumer requirements documented
+- [ ] API style guide established
+- [ ] Contract testing infrastructure
+
+## Phase 1: Contract Design
+
+### Step 1.1: Gather Consumer Needs
+```yaml
+agent: api-designer
+action: gather_requirements
+sources:
+  - consumer_teams
+  - existing_integrations
+  - product_requirements
+outputs:
+  - consumer_expectations
+  - use_case_scenarios
+```
+
+### Step 1.2: Draft Contract
+```yaml
+agent: api-designer
+action: design
+format: openapi_3.1
+sections:
+  - info
+  - servers
+  - paths
+  - components
+  - security
+```
+
+### Step 1.3: Review and Iterate
+```yaml
+agent: api-designer
+action: review
+with:
+  - consumer_teams
+  - security_team
+  - platform_team
+```
+
+## Phase 2: Contract Validation
+
+### Step 2.1: Generate Mock Server
+```yaml
+agent: fullstack-developer
+action: generate_mock
+from: openapi_spec
+tools:
+  - Prism
+  - WireMock
+  - MockServer
+```
+
+### Step 2.2: Consumer Testing
+```yaml
+agent: tester
+action: test_against_mock
+tests:
+  - consumer_expectations
+  - error_scenarios
+  - edge_cases
+```
+
+## Phase 3: Provider Implementation
+
+### Step 3.1: Generate Server Stubs
+```yaml
+agent: fullstack-developer
+action: generate
+from: openapi_spec
+framework: framework_of_choice
+```
+
+### Step 3.2: Implement Handlers
+```yaml
+agent: fullstack-developer
+action: implement
+following:
+  - contract_spec
+  - business_rules
+  - validation_requirements
+```
+
+## Phase 4: Contract Testing
+
+### Step 4.1: Pact Contract Tests
+```yaml
+agent: tester
+action: create_pact_tests
+coverage:
+  - all_endpoints
+  - error_responses
+  - edge_cases
+```
+
+### Step 4.2: Run Provider Verification
+```yaml
+agent: tester
+action: verify_provider
+using: pact_broker
+reports:
+  - verification_results
+  - compatibility_matrix
+```
+
+## Phase 5: Documentation
+
+### Step 5.1: Generate API Docs
+```yaml
+agent: api-designer
+action: generate_docs
+tools:
+  - Redoc
+  - Swagger UI
+  - Stoplight
+outputs:
+  - interactive_docs
+  - sdk_generation
+```
+
+## Outputs
+- [ ] OpenAPI specification
+- [ ] Mock server configuration
+- [ ] Contract tests (Pact)
+- [ ] Provider implementation
+- [ ] API documentation
+
+## Quality Gates
+- Contract passes linting
+- All consumer tests pass against mock
+- Provider verifies all contracts
+- Documentation is accurate
+- Breaking changes detected

package/plugin/workflows/microservices/distributed-tracing.md

@@ -0,0 +1,166 @@
+---
+description: Implement distributed tracing across microservices
+triggers:
+  - manual
+  - observability:tracing
+agents:
+  - site-reliability-engineer
+  - fullstack-developer
+---
+
+# Distributed Tracing Workflow
+
+Set up end-to-end request tracing across services.
+
+## Prerequisites
+- [ ] Services identified for instrumentation
+- [ ] Tracing backend selected
+- [ ] Sampling strategy defined
+
+## Phase 1: Infrastructure Setup
+
+### Step 1.1: Deploy Tracing Backend
+```yaml
+agent: site-reliability-engineer
+action: deploy
+options:
+  - Jaeger
+  - Zipkin
+  - Tempo
+  - AWS X-Ray
+configuration:
+  - collector
+  - storage_backend
+  - query_service
+  - ui
+```
+
+### Step 1.2: Configure Sampling
+```yaml
+agent: site-reliability-engineer
+action: configure
+sampling:
+  type: probabilistic  # or rate_limiting, adaptive
+  rate: 0.1  # 10% of traces
+  rules:
+    - service: payment
+      rate: 1.0  # 100% for critical
+    - path: /health
+      rate: 0.0  # Don't trace health checks
+```
+
+## Phase 2: Service Instrumentation
+
+### Step 2.1: Add Tracing Libraries
+```yaml
+agent: fullstack-developer
+action: instrument
+libraries:
+  - opentelemetry-sdk
+  - opentelemetry-auto-instrumentation
+configuration:
+  - service_name
+  - environment
+  - version
+```
+
+### Step 2.2: Propagate Context
+```yaml
+agent: fullstack-developer
+action: implement
+context_propagation:
+  - HTTP_headers:
+      - traceparent
+      - tracestate
+  - gRPC_metadata
+  - message_queue_headers
+formats:
+  - W3C_Trace_Context
+  - B3
+```
+
+## Phase 3: Custom Instrumentation
+
+### Step 3.1: Add Custom Spans
+```yaml
+agent: fullstack-developer
+action: instrument
+custom_spans:
+  - database_queries
+  - external_api_calls
+  - cache_operations
+  - business_logic
+attributes:
+  - user_id
+  - order_id
+  - operation_type
+```
+
+### Step 3.2: Add Events and Exceptions
+```yaml
+agent: fullstack-developer
+action: instrument
+additions:
+  - span_events: significant_operations
+  - exception_recording: all_errors
+  - baggage: cross_cutting_data
+```
+
+## Phase 4: Correlation
+
+### Step 4.1: Log Correlation
+```yaml
+agent: fullstack-developer
+action: configure
+log_correlation:
+  - inject_trace_id_in_logs
+  - inject_span_id_in_logs
+  - structured_logging_format
+```
+
+### Step 4.2: Metrics Correlation
+```yaml
+agent: site-reliability-engineer
+action: configure
+metrics_correlation:
+  - exemplars: trace_id_in_metrics
+  - dashboards: trace_links
+```
+
+## Phase 5: Analysis and Alerts
+
+### Step 5.1: Create Dashboards
+```yaml
+agent: site-reliability-engineer
+action: create
+dashboards:
+  - service_latency_breakdown
+  - error_trace_analysis
+  - dependency_graph
+  - critical_path_analysis
+```
+
+### Step 5.2: Configure Alerts
+```yaml
+agent: site-reliability-engineer
+action: configure
+alerts:
+  - high_latency_traces
+  - error_rate_spikes
+  - missing_spans
+  - trace_completeness
+```
+
+## Outputs
+- [ ] Tracing backend deployment
+- [ ] Instrumented services
+- [ ] Context propagation
+- [ ] Correlated logs/metrics
+- [ ] Analysis dashboards
+
+## Quality Gates
+- Traces flow end-to-end
+- Context propagated correctly
+- Sampling rate appropriate
+- No performance degradation
+- Alerts configured

package/plugin/workflows/microservices/domain-decomposition.md

@@ -0,0 +1,123 @@
+---
+description: Decompose monolith into bounded contexts using DDD principles
+triggers:
+  - manual
+  - archetype:microservices
+agents:
+  - domain-decomposer
+  - architect
+---
+
+# Domain Decomposition Workflow
+
+Break down a domain into bounded contexts for microservices.
+
+## Prerequisites
+- [ ] Business domain documentation
+- [ ] Existing codebase (if migrating)
+- [ ] Stakeholder access for clarification
+
+## Phase 1: Domain Discovery
+
+### Step 1.1: Gather Domain Knowledge
+```yaml
+agent: domain-decomposer
+action: analyze
+inputs:
+  - business_requirements
+  - existing_codebase
+outputs:
+  - domain_terms_glossary
+  - business_capabilities_map
+```
+
+### Step 1.2: Identify Core Domains
+```yaml
+agent: domain-decomposer
+action: categorize
+criteria:
+  - core: Competitive advantage
+  - supporting: Necessary but not differentiating
+  - generic: Commodity, can buy
+```
+
+## Phase 2: Context Mapping
+
+### Step 2.1: Draw Bounded Contexts
+```yaml
+agent: domain-decomposer
+action: draw_contexts
+patterns:
+  - Shared Kernel
+  - Customer-Supplier
+  - Conformist
+  - Anti-Corruption Layer
+  - Open Host Service
+  - Published Language
+```
+
+### Step 2.2: Define Context Relationships
+```yaml
+agent: architect
+action: define_relationships
+artifacts:
+  - context_map_diagram
+  - integration_contracts
+```
+
+## Phase 3: Aggregate Design
+
+### Step 3.1: Identify Aggregates
+```yaml
+agent: domain-decomposer
+action: identify_aggregates
+rules:
+  - Single transaction boundary
+  - Consistency boundary
+  - Minimal aggregate size
+```
+
+### Step 3.2: Define Aggregate Roots
+```yaml
+agent: domain-decomposer
+action: define_roots
+outputs:
+  - aggregate_specifications
+  - invariant_rules
+```
+
+## Phase 4: Service Boundaries
+
+### Step 4.1: Map Contexts to Services
+```yaml
+agent: architect
+action: map_services
+considerations:
+  - Team ownership
+  - Deployment independence
+  - Data ownership
+  - Communication patterns
+```
+
+### Step 4.2: Define APIs
+```yaml
+agent: architect
+action: define_apis
+style: contract-first
+artifacts:
+  - openapi_specs
+  - async_api_specs
+```
+
+## Outputs
+- [ ] Domain glossary
+- [ ] Context map diagram
+- [ ] Aggregate specifications
+- [ ] Service boundary definitions
+- [ ] API contracts
+
+## Quality Gates
+- All contexts have clear ownership
+- No cyclic dependencies between contexts
+- Aggregates are transaction-consistent
+- APIs follow organization standards