omgkit 2.12.0 → 2.15.0

package/plugin/workflows/game-dev/content-pipeline.md

@@ -0,0 +1,218 @@
+---
+description: Set up efficient content creation and integration pipeline
+triggers:
+  - manual
+  - game:content
+agents:
+  - game-designer
+  - fullstack-developer
+---
+
+# Content Pipeline Workflow
+
+Create efficient pipeline for game content creation.
+
+## Prerequisites
+- [ ] Art style defined
+- [ ] Content tools selected
+- [ ] Version control configured
+
+## Phase 1: Pipeline Design
+
+### Step 1.1: Identify Content Types
+```yaml
+agent: game-designer
+action: catalog
+content_types:
+  - 2D_assets: Sprites, UI, textures
+  - 3D_assets: Models, animations, rigs
+  - Audio: Music, SFX, voice
+  - Data: Levels, items, enemies
+  - Localization: Text, subtitles
+```
+
+### Step 1.2: Define Pipeline Flow
+```yaml
+agent: game-designer
+action: design
+flow:
+  creation:
+    - Artist creates asset
+    - Export to intermediate format
+    - Commit to version control
+  processing:
+    - Import into engine
+    - Apply processing rules
+    - Generate variants
+  integration:
+    - Create/update prefab
+    - Wire up references
+    - Test in game
+```
+
+## Phase 2: Tool Setup
+
+### Step 2.1: DCC Integration
+```yaml
+agent: fullstack-developer
+action: configure
+tools:
+  - Blender: 3D modeling, animation
+  - Photoshop/GIMP: 2D art
+  - Substance: Texturing
+  - Spine/DragonBones: 2D animation
+export_scripts:
+  - Automated export
+  - Naming validation
+  - Format conversion
+```
+
+### Step 2.2: Engine Import Setup
+```yaml
+agent: fullstack-developer
+action: configure
+import_rules:
+  textures:
+    - Format: PNG/TGA
+    - Compression: Platform-specific
+    - MipMaps: Generate automatically
+  models:
+    - Format: FBX/GLTF
+    - Scale: 1 unit = 1 meter
+    - Materials: Auto-assign
+  animations:
+    - Format: FBX
+    - Compression: Optimal
+    - Root motion: Configure
+```
+
+## Phase 3: Version Control
+
+### Step 3.1: Configure LFS
+```yaml
+agent: fullstack-developer
+action: configure
+git_lfs:
+  - *.png
+  - *.psd
+  - *.fbx
+  - *.wav
+  - *.mp3
+  - *.unity (or engine scenes)
+```
+
+### Step 3.2: Branching Strategy
+```yaml
+agent: fullstack-developer
+action: define
+branches:
+  - main: Stable builds
+  - develop: Integration
+  - feature/*: New content
+  - release/*: Release prep
+content_specific:
+  - content/*: Large content updates
+  - Lock files for binary conflicts
+```
+
+## Phase 4: Automation
+
+### Step 4.1: Asset Validation
+```yaml
+agent: fullstack-developer
+action: implement
+validators:
+  - Naming convention check
+  - Texture size limits
+  - Polygon count limits
+  - Material validation
+  - Reference validation
+triggers:
+  - Pre-commit hook
+  - CI pipeline
+```
+
+### Step 4.2: Asset Processing
+```yaml
+agent: fullstack-developer
+action: implement
+automation:
+  - Texture atlas generation
+  - LOD generation
+  - Animation retargeting
+  - Audio normalization
+  - Localization extraction
+```
+
+### Step 4.3: Build Pipeline
+```yaml
+agent: fullstack-developer
+action: implement
+builds:
+  - Asset bundles creation
+  - Platform-specific builds
+  - DLC packaging
+  - Addressables (Unity)
+  - Pak files (Unreal)
+```
+
+## Phase 5: Content Management
+
+### Step 5.1: Data-Driven Content
+```yaml
+agent: game-designer
+action: design
+systems:
+  - JSON/YAML game data
+  - ScriptableObjects (Unity)
+  - DataAssets (Unreal)
+  - Spreadsheet integration
+tools:
+  - Google Sheets sync
+  - Custom editors
+  - Validation tools
+```
+
+### Step 5.2: Localization Pipeline
+```yaml
+agent: fullstack-developer
+action: implement
+pipeline:
+  - String extraction
+  - Translation management
+  - Import localized assets
+  - Font management
+  - RTL support (if needed)
+tools:
+  - POEditor
+  - Crowdin
+  - Custom tools
+```
+
+## Phase 6: Documentation
+
+### Step 6.1: Content Guidelines
+```yaml
+agent: game-designer
+action: document
+guidelines:
+  - Art style guide
+  - Naming conventions
+  - File formats
+  - Quality requirements
+  - Submission process
+```
+
+## Outputs
+- [ ] DCC tool configurations
+- [ ] Import settings
+- [ ] Validation scripts
+- [ ] Build pipeline
+- [ ] Content guidelines
+
+## Quality Gates
+- All assets pass validation
+- Build succeeds
+- No missing references
+- Performance targets met
+- Guidelines documented

package/plugin/workflows/game-dev/platform-submission.md

@@ -0,0 +1,263 @@
+---
+description: Prepare and submit game builds to platform stores
+triggers:
+  - manual
+  - game:submit
+agents:
+  - game-designer
+  - fullstack-developer
+  - tester
+---
+
+# Platform Submission Workflow
+
+Navigate platform certification and store submission.
+
+## Prerequisites
+- [ ] Game content complete
+- [ ] Developer accounts set up
+- [ ] Platform SDK integrated
+
+## Phase 1: Pre-Submission Checklist
+
+### Step 1.1: Platform Requirements Review
+```yaml
+agent: game-designer
+action: review
+platforms:
+  steam:
+    - Steamworks SDK integrated
+    - Achievements configured
+    - Trading cards (optional)
+    - Cloud saves
+    - Controller support
+  playstation:
+    - TRC compliance
+    - Trophy system
+    - PS Plus features
+    - Activity cards
+  xbox:
+    - XR compliance
+    - Achievements
+    - Smart Delivery
+    - Quick Resume support
+  nintendo:
+    - Lotcheck requirements
+    - Save data handling
+    - Sleep mode handling
+  mobile:
+    - Store guidelines
+    - IAP integration
+    - Privacy policy
+    - Age ratings
+```
+
+### Step 1.2: Content Rating
+```yaml
+agent: game-designer
+action: submit
+rating_boards:
+  - ESRB (North America)
+  - PEGI (Europe)
+  - USK (Germany)
+  - CERO (Japan)
+  - GRAC (Korea)
+  - ClassInd (Brazil)
+process:
+  - Complete questionnaires
+  - Submit content samples
+  - Receive ratings
+  - Display correctly in-game
+```
+
+## Phase 2: Build Preparation
+
+### Step 2.1: Release Build Configuration
+```yaml
+agent: fullstack-developer
+action: configure
+settings:
+  - Remove debug code
+  - Enable optimizations
+  - Strip debug symbols
+  - Configure crash reporting
+  - Set version numbers
+  - Update copyright
+```
+
+### Step 2.2: Platform-Specific Builds
+```yaml
+agent: fullstack-developer
+action: build
+per_platform:
+  steam:
+    - Windows x64
+    - Linux (optional)
+    - macOS (optional)
+    - Steam Deck verified
+  console:
+    - Platform-specific SDK
+    - Certification build flags
+    - Signed packages
+  mobile:
+    - Android APK/AAB
+    - iOS IPA
+    - App bundles
+```
+
+### Step 2.3: DRM and Protection
+```yaml
+agent: fullstack-developer
+action: configure
+protection:
+  - Platform DRM (Steam, console)
+  - Online requirements
+  - License verification
+  - Anti-cheat (if multiplayer)
+```
+
+## Phase 3: Quality Assurance
+
+### Step 3.1: Certification Testing
+```yaml
+agent: tester
+action: test
+test_areas:
+  - First-time user experience
+  - Network disconnection handling
+  - Save data corruption recovery
+  - Suspend/resume behavior
+  - Controller disconnection
+  - Achievement triggering
+  - Localization accuracy
+  - Accessibility features
+```
+
+### Step 3.2: Platform Compliance
+```yaml
+agent: tester
+action: verify
+requirements:
+  - Load times within limits
+  - Frame rate stability
+  - Memory usage
+  - Terminology compliance
+  - Button prompts correct
+  - Legal notices displayed
+```
+
+### Step 3.3: Regression Testing
+```yaml
+agent: tester
+action: test
+scope:
+  - Full playthrough
+  - All features
+  - All platforms
+  - Performance validation
+```
+
+## Phase 4: Store Assets
+
+### Step 4.1: Marketing Materials
+```yaml
+agent: game-designer
+action: prepare
+assets:
+  - Store page screenshots (platform sizes)
+  - Trailer video
+  - Game description
+  - Feature list
+  - System requirements
+  - Developer info
+```
+
+### Step 4.2: Store Configuration
+```yaml
+agent: game-designer
+action: configure
+settings:
+  - Pricing
+  - Release date
+  - Regions
+  - Languages
+  - Age gates
+  - Purchase options
+  - DLC/Bundles
+```
+
+## Phase 5: Submission
+
+### Step 5.1: Upload Build
+```yaml
+agent: fullstack-developer
+action: upload
+per_platform:
+  steam: Upload via SteamPipe
+  playstation: Upload via Partner portal
+  xbox: Upload via Partner Center
+  nintendo: Upload via Partner portal
+  ios: Upload via App Store Connect
+  android: Upload via Play Console
+```
+
+### Step 5.2: Submit for Review
+```yaml
+agent: game-designer
+action: submit
+documentation:
+  - Build notes
+  - Test account credentials
+  - Known issues (if any)
+  - Special instructions
+  - Video walkthrough
+timeline:
+  - Steam: ~3 days review
+  - PlayStation: 1-2 weeks
+  - Xbox: 1-2 weeks
+  - Nintendo: 2-4 weeks
+  - iOS: 1-3 days
+  - Android: 1-7 days
+```
+
+## Phase 6: Post-Submission
+
+### Step 6.1: Handle Feedback
+```yaml
+agent: game-designer
+action: respond
+scenarios:
+  approved:
+    - Schedule release
+    - Prepare launch marketing
+  rejected:
+    - Address issues
+    - Resubmit
+    - Update timeline
+```
+
+### Step 6.2: Launch Preparation
+```yaml
+agent: game-designer
+action: prepare
+launch_checklist:
+  - Press kit ready
+  - Social media scheduled
+  - Support team briefed
+  - Day-one patch ready
+  - Server infrastructure ready
+```
+
+## Outputs
+- [ ] Certified builds
+- [ ] Content ratings
+- [ ] Store pages
+- [ ] Submission documentation
+- [ ] Launch checklist
+
+## Quality Gates
+- All certification tests pass
+- Builds uploaded successfully
+- Store pages complete
+- Ratings received
+- Submission approved

package/plugin/workflows/game-dev/playtesting.md

@@ -0,0 +1,237 @@
+---
+description: Systematic playtesting workflow for game quality
+triggers:
+  - manual
+  - game:playtest
+agents:
+  - game-designer
+  - tester
+---
+
+# Playtesting Workflow
+
+Conduct effective playtesting to improve game quality.
+
+## Prerequisites
+- [ ] Playable build available
+- [ ] Testing environment set up
+- [ ] Playtesters identified
+
+## Phase 1: Playtest Planning
+
+### Step 1.1: Define Objectives
+```yaml
+agent: game-designer
+action: define
+objectives:
+  types:
+    - Usability: Can players figure it out?
+    - Fun: Is it enjoyable?
+    - Balance: Is difficulty appropriate?
+    - Progression: Is pacing good?
+    - Polish: What needs refinement?
+  specific_questions:
+    - List 3-5 specific questions to answer
+```
+
+### Step 1.2: Select Playtesters
+```yaml
+agent: game-designer
+action: select
+criteria:
+  internal:
+    - Fresh eyes (haven't seen game)
+    - Different skill levels
+    - Different gaming preferences
+  external:
+    - Target audience match
+    - Diverse backgrounds
+    - Mix of experienced/casual
+```
+
+### Step 1.3: Prepare Environment
+```yaml
+agent: tester
+action: setup
+environment:
+  - Stable build (no known crashes)
+  - Consistent hardware
+  - Recording setup
+  - Observation setup
+  - Survey tools
+```
+
+## Phase 2: Data Collection Setup
+
+### Step 2.1: Telemetry Implementation
+```yaml
+agent: tester
+action: implement
+metrics:
+  - Play time per session
+  - Deaths/failures per area
+  - Resource usage
+  - Feature usage
+  - Path taken
+  - Time per objective
+tools:
+  - Unity Analytics
+  - GameAnalytics
+  - Custom telemetry
+```
+
+### Step 2.2: Observation Protocol
+```yaml
+agent: game-designer
+action: define
+observation:
+  - Think-aloud protocol
+  - Observer notes template
+  - Video/audio recording
+  - Screen capture
+  - Eye tracking (if available)
+```
+
+### Step 2.3: Survey Preparation
+```yaml
+agent: game-designer
+action: prepare
+surveys:
+  pre_play:
+    - Gaming experience
+    - Genre preferences
+    - Expectations
+  during_play:
+    - Confusion points
+    - Frustration moments
+  post_play:
+    - Overall enjoyment
+    - Difficulty perception
+    - Likelihood to continue
+    - Feature feedback
+```
+
+## Phase 3: Playtest Execution
+
+### Step 3.1: Conduct Sessions
+```yaml
+agent: tester
+action: facilitate
+session_structure:
+  1. Introduction: Explain process, sign consent
+  2. Pre-survey: Background questions
+  3. Free play: Minimal guidance
+  4. Observation: Note behaviors
+  5. Probe questions: Clarify observations
+  6. Post-survey: Collect feedback
+  7. Debrief: Open discussion
+```
+
+### Step 3.2: Documentation
+```yaml
+agent: tester
+action: document
+per_session:
+  - Timestamp key events
+  - Note confusion points
+  - Record quotes
+  - Mark bugs encountered
+  - Note suggestions
+```
+
+## Phase 4: Analysis
+
+### Step 4.1: Quantitative Analysis
+```yaml
+agent: game-designer
+action: analyze
+metrics:
+  - Completion rates
+  - Time distributions
+  - Failure hotspots
+  - Feature adoption
+  - Progression curves
+visualization:
+  - Heat maps
+  - Funnel charts
+  - Time graphs
+```
+
+### Step 4.2: Qualitative Analysis
+```yaml
+agent: game-designer
+action: analyze
+methods:
+  - Affinity mapping
+  - Theme identification
+  - Pain point ranking
+  - Suggestion categorization
+  - Quote compilation
+```
+
+### Step 4.3: Insight Synthesis
+```yaml
+agent: game-designer
+action: synthesize
+outputs:
+  - Key findings summary
+  - Priority issues list
+  - Actionable recommendations
+  - Design questions answered
+  - New questions raised
+```
+
+## Phase 5: Action Planning
+
+### Step 5.1: Prioritize Findings
+```yaml
+agent: game-designer
+action: prioritize
+criteria:
+  - Impact on player experience
+  - Frequency of occurrence
+  - Effort to address
+  - Alignment with vision
+categories:
+  - Critical: Must fix before next test
+  - High: Address this iteration
+  - Medium: Backlog for future
+  - Low: Nice to have
+```
+
+### Step 5.2: Create Action Items
+```yaml
+agent: game-designer
+action: plan
+per_finding:
+  - Issue description
+  - Proposed solution
+  - Assigned owner
+  - Target milestone
+  - Validation criteria
+```
+
+### Step 5.3: Plan Follow-up Testing
+```yaml
+agent: game-designer
+action: plan
+next_playtest:
+  - Verify fixes
+  - Test new content
+  - New questions
+  - Different audience segment
+```
+
+## Outputs
+- [ ] Playtest plan
+- [ ] Data collection setup
+- [ ] Session recordings
+- [ ] Analysis report
+- [ ] Action items
+
+## Quality Gates
+- Objectives answered
+- Representative sample tested
+- Data properly collected
+- Actionable insights generated
+- Follow-up planned