Files
skill-seekers-reference/spyke_confluence_analysis.md
YusufKaraaslanSpyke b8b5e9d6ef perf: Optimize LOCAL mode AI enhancement with parallel execution
- Increase default batch size from 5 to 20 patterns per CLI call
- Add parallel execution with 3 concurrent workers (configurable)
- Add ai_enhancement settings to config_manager:
  - local_batch_size: patterns per Claude CLI call (default: 20)
  - local_parallel_workers: concurrent CLI calls (default: 3)
- Expected speedup: 6-12x faster for large codebases

Config settings can be changed via:
  skill-seekers config (coming soon) or editing ~/.config/skill-seekers/config.json

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-30 14:07:20 +03:00

12 KiB
Raw Blame History

Spyke Games Confluence Documentation Analysis & Skill Generation Plan

Executive Summary

Total Pages: 147 Usable Content: 127 pages (86%) Empty/Container: 20 pages (14%) Legacy/Deprecated: 17 pages (12%) Active & Valid: ~110 pages (75%)


Document Hierarchy Overview

Engineering (root)
├── R&D/
│   ├── Backend Architecture/ (5 docs)
│   ├── Client Architecture/ (9 docs + Addressables/5)
│   ├── Cloud Services/AWS notes/ (4 docs)
│   ├── Graphics/ (4 docs)
│   ├── Network Messaging/ (3 docs)
│   └── Tools/ (1 doc)
├── Backend Design/ (7 docs)
├── Team/ (4 docs)
├── Team Backend Notes/ (3 docs)
├── Cheatsheets/ (4 docs)
├── Tech Talks/ (3 docs)
├── Feature Flags/LiveOps Tooling/ (5+ docs)
├── Game Retrospectives/ (4 docs - legacy)
├── Reverse Engineering/ (7 docs - legacy)
├── Third Party SDKs/ (3 docs)
├── How To Add New Special Day Theme Assets/ (8 docs)
└── ~30 standalone pages

Issues Found:

  • 3 orphaned docs (parent outside space)
  • 20 empty container pages
  • Inconsistent nesting (some topics deeply nested, others flat)
  • Mixed languages (English + Turkish titles)

Skill Generation Recommendations

Based on content depth, code examples, and practical value:


1. SKILL: "spyke-unity-client" (HIGH VALUE)

Content Sources: 25 pages | ~59,000 chars | 12 with code

Topics to Include:

  • UI Panel Transitions
  • Screen Scaling for mobile
  • Addressables (caching, bundles, catalog structure)
  • Scriptable Objects as Architecture
  • MVCVM Architecture pattern
  • Fast Generic Observers (SignalBus alternative)
  • Persistent Data management
  • Animation & Particle Performance
  • Shader development (MultiLayerText, Blur)
  • URP vs Legacy Render Pipeline

Why Generate:

  • Core Unity development patterns used across all games
  • Reusable regardless of which game is active
  • Good mix of code examples and explanations

Improvements Needed Before Generating:

  1. Finalize "Slot Game X - Architecture (MVCVM) - (Draft)"
  2. Add code examples to "Scriptable Objects as Architecture"
  3. Update "Built-in (Legacy) Render Pipeline vs URP" - mark Legacy as deprecated
  4. Consolidate Addressables docs into cohesive guide

2. SKILL: "spyke-backend" (HIGH VALUE)

Content Sources: 16 pages | ~36,000 chars | 5 with code

Topics to Include:

  • Database Version Control/Migration (Flyway)
  • Database Access Layer patterns
  • Spring/Gradle architecture
  • Game Server architecture
  • Load testing approaches
  • Security measures
  • MySQL/Aurora patterns
  • Chat backend implementation

Why Generate:

  • Backend patterns are game-agnostic
  • Critical for onboarding backend devs
  • Contains production-tested patterns

Improvements Needed Before Generating:

  1. Finalize "Backend Code Structure (draft)"
  2. Finalize "Chat Mysql (draft)"
  3. Finalize "Help Call Backend Notes (Draft)"
  4. Translate Turkish content: "bonanza ve lucky spin..." → English
  5. Add more code examples to architecture docs

3. SKILL: "spyke-aws" (MEDIUM VALUE)

Content Sources: 9 pages | ~22,000 chars | 3 with code

Topics to Include:

  • AWS account/users/groups/policies
  • Elastic Beanstalk setup
  • Gateway and ALB configuration
  • Aurora database notes
  • Performance testing with k6
  • AWS CLI access (secure)
  • AWS Evidently for feature flags
  • Cost saving strategies

Why Generate:

  • Infrastructure knowledge critical for ops
  • k6 performance testing guide is excellent
  • AWS patterns are reusable

Improvements Needed Before Generating:

  1. Finalize "Secure AWS CLI Access (DRAFT)"
  2. Update AWS notes - verify if still using EB or migrated
  3. Add more practical examples to account setup docs

4. SKILL: "spyke-onboarding" (MEDIUM VALUE)

Content Sources: 13 pages | ~26,000 chars | 4 with code

Topics to Include:

  • Welcome To The Team
  • Buddy System
  • Code Review (How To)
  • Release Manager responsibilities
  • Git Submodule management
  • New Project Setup from Bootstrap
  • Unit Test Integration to Pipeline
  • Mock Web Service Tool

Why Generate:

  • Essential for new engineer onboarding
  • Process documentation is evergreen
  • Reduces tribal knowledge

Improvements Needed Before Generating:

  1. Update "Welcome To The Team" with current tools/processes
  2. Add current team structure to Team docs
  3. Verify pipeline docs match current CI/CD

5. SKILL: "spyke-sdks" (LOW VALUE - CONSIDER SKIP)

Content Sources: 7 pages | ~7,000 chars | 5 with code

Topics to Include:

  • MAX SDK integration
  • OneSignal push notifications
  • Braze platform notes
  • AppsFlyer (if still used)
  • i2 localization
  • Huawei App Gallery

Why Generate: SDK integration guides save time

Issues:

  • Most are version-specific and may be outdated
  • Low content depth
  • Better to link to official SDK docs

Recommendation: Skip or merge into onboarding skill


6. SKILL: "spyke-liveops" (LOW VALUE - NEEDS WORK)

Content Sources: ~10 pages | Content scattered

Topics to Include:

  • Feature Flags overview
  • Split.io vs Unleash vs AWS Evidently comparison
  • A/B Test Infrastructure
  • Configuration Management

Issues:

  • Content is fragmented
  • Many empty placeholder pages
  • "The Choice and Things to Consider" has no conclusion

Recommendation: Consolidate before generating


Legacy/Deprecated (17 pages)

  • Coin Master, Tile Busters, Royal Riches, Island King, Pirate King docs
  • Action: Archive in Confluence, do NOT include in skills
  • Exception: "Learnings From X" docs have reusable insights - extract generic patterns

Empty Containers (20 pages)

  • Engineering, R&D, Client, Backend, etc.
  • Action: Either delete or add meaningful overview content

Game-Specific Workflows

  • "How to add new Endless Offers (Tile Busters)" - deprecated
  • "Tile Busters Particle Optimizations" - game-specific
  • Action: Generalize or archive

Individual Document Improvements

HIGH PRIORITY (Block skill generation)

Document Issue Action
Slot Game X - Architecture (MVCVM) - (Draft) Still draft Finalize or remove draft label
Backend Code Structure (draft) Still draft Finalize with current structure
Chat Mysql (draft) Still draft Finalize or archive
Secure AWS CLI Access (DRAFT) Still draft Finalize - important for security
Help Call Backend Notes (Draft) Still draft Finalize or archive
Submodule [Draft] Still draft Merge with Git Submodule doc
Creating New Team Event (DRAFT) Still draft Finalize
bonanza ve lucky spin... Turkish title Translate to English

MEDIUM PRIORITY (Improve quality)

Document Issue Action
Scriptable Objects as Architecture No code examples Add Unity C# examples
Built-in (Legacy) vs URP Doesn't say which to use Add clear recommendation: "Use URP"
Feature Flag System No conclusion Add recommendation on which system
The Choice and Things to Consider Incomplete Add final decision/recommendation
AWS notes (container) Empty Add overview or delete
Third Party SDKs (container) Empty Add overview or delete
All 20 empty containers No content Add overview content or delete

LOW PRIORITY (Nice to have)

Document Issue Action
Addressables (5 docs) Scattered Consolidate into single comprehensive guide
Animation Performance (2 docs) Overlap Merge benchmarks with tips
LiveOps Tools (5 docs) Fragmented Create summary comparison table
Game Retrospectives Deprecated games Extract generic learnings, archive rest

  1. spyke-unity-client (most value, good content)
  2. spyke-backend (after drafts finalized)
  3. spyke-aws (after drafts finalized)
  4. spyke-onboarding (after process docs updated)
  5. spyke-sdks (skip or merge)
  6. spyke-liveops (needs consolidation first)

Implementation Steps

Phase 1: Content Cleanup

  1. Finalize all 8 draft documents
  2. Translate Turkish content to English
  3. Delete or populate 20 empty container pages
  4. Archive 17 legacy game docs

Phase 2: Generate Skills

  1. Create unified config for each skill
  2. Use Skill Seekers with Confluence scraper (to be built)
  3. Generate and package skills

Phase 3: Ongoing Maintenance

  1. Set up review schedule for docs
  2. Add "Last Reviewed" date to each doc
  3. Create Confluence template for new docs

Confluence Scraper Feature (New Development)

To generate skills from Confluence, need to add:

src/skill_seekers/cli/confluence_scraper.py

Config format:

{
  "name": "spyke-unity-client",
  "type": "confluence",
  "domain": "spykegames.atlassian.net",
  "space_key": "EN",
  "page_ids": ["70811737", "8880129", ...],
  "exclude_patterns": ["coin master", "tile busters"],
  "auth": {
    "email": "$CONFLUENCE_EMAIL",
    "token": "$CONFLUENCE_TOKEN"
  }
}

Summary

Metric Count
Total Pages 147
Ready for Skills ~80
Need Improvement ~30
Archive/Delete ~37
Recommended Skills 4
Drafts to Finalize 8
Empty to Fix 20

ACTION CHECKLIST FOR DOC CLEANUP

1. Finalize Drafts (8 docs)

2. Translate to English (1 doc)

3. Delete or Populate Empty Containers (20 docs)

  • Engineering (root page - add overview)
  • R&D (add overview)
  • Client (add overview or delete)
  • Backend (add overview or delete)
  • AWS notes (add overview or delete)
  • Network Messaging (add overview or delete)
  • Tools (add overview or delete)
  • Cloud Services (add overview or delete)
  • Graphics (add overview or delete)
  • Client Architecture (add overview or delete)
  • Backend Architecture (add overview or delete)
  • Backend Design (add overview or delete)
  • Third Party SDKs (add overview or delete)
  • Tech Talks (add overview or delete)
  • Cheatsheets (add overview or delete)
  • Team (add overview or delete)
  • Game Retrospectives (add overview or delete)
  • Feature Flags / LiveOps Tooling (add overview or delete)
  • How To Add New Special Day Theme Assets (add overview)
  • Replacing Active App Icon On Player Settings (add content - only has link)

4. Archive Legacy Game Docs (17 docs)

Move to "Archive" or "Legacy" section:

  • Coin Master
  • Coin Master Notes
  • Bot - Coin Master
  • Coin Trip Notes
  • Island King
  • Pirate King
  • Learnings From Royal Riches - Client
  • Learnings From Royal Riches - Backend
  • Learnings From Tile Busters - Client
  • Learnings From Tile Busters - Backend
  • How to add new Endless Offers (Tile Busters)
  • Tile Busters Level/AB Update Flow
  • Tile Busters Backend Git Branch/Deployment Cycle
  • Tile Busters Backend Git Branch/Deployment Cycle (v2)
  • Tile Busters Particle Optimizations
  • Automated Play Test for Tile Busters
  • Automated Purchase Testing for Tile Busters
  • Add code examples to "Scriptable Objects as Architecture"
  • Add URP recommendation to "Built-in (Legacy) vs URP"
  • Consolidate 5 Addressables docs into 1
  • Add conclusion to "Feature Flag System"
  • Create comparison table in LiveOps Tools

AFTER CLEANUP: Come back and run skill generation

Once the above items are addressed, return and I will:

  1. Build a Confluence scraper for Skill Seekers
  2. Generate the 4 recommended skills
  3. Package and upload them