Yandex Games Dev

# Yandex Games: integration and evidence-based release checks

Support the game's existing engine and scope. Prefer its current JavaScript/Three.js/R3F stack; use Unity/Godot bridges only for existing projects using them. Do not migrate engines to fit an example. This skill handles platform integration and release validation, not art direction.

## Start with the actual project

Inspect repository instructions, entry HTML, package scripts, SDK wrapper, engine boot, build output, and any rejection message. Identify declared devices/orientations/languages and whether ads, progress, IAP, and leaderboards actually exist. Inspect code first; ask only for console settings or credentials that cannot be inferred. Never add monetization just to satisfy an optional check.

Read [rules and sources](references/rules-and-requirements.md), then fetch the current official pages relevant to the task. For submission, review the complete current requirements and moderation pages. Record retrieval date and relevant clauses. If unavailable, use the pinned guidance but label rule verification incomplete. Official rules override this skill and the unofficial checker.

## Choose the workflow

| Task | Read and use |
|---|---|
| Integrate or repair SDK behavior | [SDK](references/yandex-sdk.md), then the engine guide below |
| Run a pre-submission audit or investigate checker output | [Checker runbook](references/debug-checker.md), [fix guide](references/check-remediation.md) |