universo-platformo-react

Universo-specific complement to the OntoIndex code-intelligence tool. Use alongside the generated `.claude/skills/ontoindex/*` skills when querying the code graph in this monorepo. Adds the three things those generated skills do NOT cover — the namespace-collision caveat (this is code intelligence over source, NOT OWL/RDF/SPARQL), this repo's pnpm wrapper and golden queries, and the SQL-first edge-quality limitation.

Use when the user needs to run OntoIndex CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"

Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow"

Use when the user asks about OntoIndex itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What OntoIndex tools are available?", "How do I use OntoIndex?"

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

Use when working with the PlayCanvas Editor API, realtime sync protocols, WebSocket endpoints, ShareDB, Operational Transformation (OT), or document collections.

Use when working with the PlayCanvas Editor asset import pipeline, texture conversion, model ingestion, audio files, materials, or asset metadata attributes.

Use when planning, implementing, or reviewing work that touches PlayCanvas Editor authoring, the Editor/Engine boundary, vendored upstream artifacts, Editor boot contract, or Editor package routing. Applies to @universo-react/playcanvas-editor-frontend vendoring playcanvas/editor v2.24.2 with playcanvas@2.19.5; does NOT cover playcanvas-engine-runtime (playcanvas@2.18.1) or PlayCanvas Cloud parity.

Use when working with the PlayCanvas Editor interface panels, inspectors, toolbar actions, layout configurations, PCUI components, viewport settings, or keyboard shortcuts.

Use when working with the PlayCanvas Editor scene graph, Entity Component System (ECS), entity hierarchy, templates, prefabs, or scene setting configurations.

Use when working with the PlayCanvas Editor scripting system, script attributes, Monaco editor integrations, ESM scripts, hot reloading, or editor scripts compilation.

Use when working with PlayCanvas Editor project settings, rendering configurations, physics settings, audio properties, publishing workflows, or launch page configs.

Use when working with the PlayCanvas Editor version control system (VCS), managing checkpoints, handling branches, merging histories, or resolving document conflicts.

Use when running a structured closeout code review for local changes, branch diffs, commit diffs, final QA after non-trivial edits, second-model review, or an explicit autoreview request. Provides the project-local `.agents/skills/autoreview/scripts/autoreview` helper for bundle-driven advisory review.

Use when working with the PlayCanvas Editor wrapper boundary inside the Universo platform, security sandboxing (iframes), window.config injection, bridge messages, and metahub storage.

Use for maintainability and code quality reviews. Covers file size limitations, abstraction quality, code structure simplification, naming conventions, test coverage, and documentation quality.

Use for deep correctness and security review of code changes. Covers critical bugs, security vulnerabilities, breaking changes, data safety, concurrency, and UUID v7 validation.

Use as the Thermos review orchestrator. Synthesizes findings from both the correctness/security and maintainability review rubrics, presenting a unified review report.

Use when planning, implementing, or reviewing a browser 3D/game runtime surface inside Universo published applications, especially PlayCanvas canvas widgets, Colyseus realtime clients, game HUDs, lazy-loaded engine widgets, input ownership, game loops, cleanup, or Playwright proof in `apps-template-mui`. Requires the Runtime UI UX Quality Gate for any user-facing screen, dialog, card, table, HUD, widget, or canvas surface.

Use when QA-reviewing implemented browser game, WebGL, PlayCanvas canvas, Colyseus realtime, reconnect, multi-client, or MMOOMM runtime UI surfaces. Checks canvas rendering, movement, responsive layout, no page overflow, keyboard/focus behavior, localized states, no raw IDs/JSON/protocol leakage, and Playwright evidence inside Universo `apps-template-mui`.

Use when planning, implementing, or QA-reviewing MMOOMM realtime multiplayer with Colyseus rooms, server-authoritative simulation, room authentication, Schema state, fixed tick processing, client interpolation or reconciliation, reconnection, or MVP scaling. Applies to `@universo-react/colyseus-server` wrapping `@colyseus/core@0.17.43` and `@universo-react/colyseus-client` wrapping `@colyseus/sdk@0.17.42`.

Use when planning, implementing, or QA-reviewing MMOOMM or browser 3D work that uses the Universo PlayCanvas wrapper, PlayCanvas Engine runtime scenes, WebGL canvas lifecycle, camera/light setup, procedural geometry, asset readiness, resize behavior, or cleanup. Applies to `@universo-react/playcanvas-engine` wrapping `playcanvas@2.18.1`; does not cover PlayCanvas Editor, PCUI, PCUI Graph, React Three Fiber, or heavy glTF/Draco/texture pipelines.

Use when planning, implementing, or reviewing MUI runtime screens, apps-template MUI dashboards, metahub template metadata, CRUD dialogs, DataGrid/table/card displays, relation builders, resource-source fields, or UI E2E flows. Enforces user-friendly runtime UI contracts: no raw user-facing IDs, no raw JSON/object cells, multiline long-text fields, localized validation, and reuse of existing dashboard primitives.

Use when QA-reviewing plans, implementations, screenshots, Playwright specs, or runtime MUI application flows for real user usability. Checks whether a normal user can complete the workflow without raw IDs, raw JSON/object cells, single-line long text, untranslated/internal validation, page-level overflow, inaccessible controls, or hidden product knowledge.

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.

Use when planning, implementing, or reviewing work that touches metahub configurations, the metahub→application→workspace placement of behavior, the platform-level entity type presets (Hub, Object, Page, Set, Enumeration, Ledger, Constants Library), the Entity Type Constructor, metahub templates (basic, basic-demo, empty, lms), LMS-style configurations, the legacy feature packages (metahubs-*, applications-*, admin-*, profile-*, start-*) being migrated to applications, the apps-template-mui transition, the pseudo-app bootstrap pattern, the planned first-run Setup Wizard and marketplace, or the platform DB layer status (Knex + raw SQL through DbExecutor, three-tier executors, @universo-react/schema-ddl, the post-TypeORM transitional state). Encodes the two-level type system, the `recordBehavior` mechanism that lets Object cover Catalog/Document/Register-style behavior, the strengthen-existing-type rule, and the practical rules for development during the architectural transition.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Use this skill when designing, generating an MVP blueprint for, auditing, refactoring, or explaining an agentic harness for any domain. Covers provider-neutral agent architecture for OpenAI, Anthropic, and OpenAI-compatible APIs: agent loops, tool design, permissions, system prompts, planning, goals, context compaction, memory, skills, MCP/external connectors, observability, evals, prompt caching, agent-legible environments, feedback loops, and safety.

Use when a task includes external links, current information, architecture discovery, or the user asks to research around planning. Produces a cited Memory Bank research document before or during PLAN mode.

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

Build production-ready Express.js servers with middleware, authentication, routing, and database integration. Use when creating REST APIs, managing requests/responses, implementing middleware chains, and handling server logic.