Browser-based HTML5 game editor and runtime: PixiJS 2D, Three.js 3D, React UI, and a TypeScript engine for multiple games
Cursor rule Cursor
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.
Cursor rule Cursor
Split oversized TypeScript modules and classes. Use when adding features to large files, extracting helpers, reviewing god objects, or a module exceeds 300–500 lines with mixed responsibilities.
Cursor rule Cursor
Critical repository invariants for almost every coding task.
Cursor rule Cursor
One undoable command class per file under packages/editor-core/src/commands. Apply when adding or editing editor-core commands.
Cursor rule Cursor
Editor React UI vs editor-core separation, selection, viewport, and dirty/undo rules. Apply when editing apps/editor or packages/editor-core.
Cursor rule Cursor
Prefer named constants over unexplained numeric literals in TypeScript. Apply when editing .ts/.tsx behavior code.
Cursor rule Cursor
Browser input is untrusted. All project filesystem access goes through ProjectService.resolveProjectPath → ProjectRootGuard.resolveSafe. Do not call path.resolve/readFile/writeFile on user-influenced paths without that guard.
Cursor rule Cursor
Vitest conventions for domain, commands, server, and security tests. Apply when editing .test.ts / .test.tsx / spec files.
Cursor rule Cursor
TypeScript conventions for this monorepo (strict mode, Zod boundaries, package imports, naming). Apply when editing .ts/.tsx files.