analyze-projectlisted

# Analyze HTML5 Project ## Steps ### Phase 0 — Workspace setup (MANDATORY, v4.7.7+) **Перед сканированием — копировка sources в WorkProgress/.** ```bash # Auto-detect from GameIntegration/ folder name (or input/{project} for legacy) mkdir -p WorkProgress/{ProjectName} cp -r GameIntegration/{ProjectName}/* WorkProgress/{ProjectName}/ ``` ВСЁ дальнейшее scanning + edits в `WorkProgress/{ProjectName}/`. `GameIntegration/` остаётся read-only. `workspace-discipline` hook блокирует Edit/Write в `GameIntegration/*`. ### 1. Scan files ```bash find WorkProgress/{ProjectName}/ -type f | head -100 du -sh WorkProgress/{ProjectName}/ ``` ### 2. Detect type Check indicators: - manifest.json / site.webmanifest → PWA - package.json with express/fastify/ws/socket.io → SERVER - canvas + requestAnimationFrame + gameLoop → CANVAS_GAME - Build/ + .wasm + .data → UNITY_WEBGL - .env / .env.example → SERVER (API keys) - fetch(http...) / axios(http...) → external API deps - None of above → SIMPLE_HTML5 ### 2.5. Classify app category (v4.7.9+, MANDATORY for non-game projects) **If type is NOT a game (CANVAS_GAME / UNITY_WEBGL)**, classify into one of 8 app categories. Categories drive: - `$product-metrics` — different KPI benchmarks (D7=50% normal for productivity, terrible for games) - `$design-pipeline` — different specialists (info architect vs game designer) - Architectural skills auto-invoked (e.g. health → privacy, finance → PCI) | Category | Indicators in code/structure | Examples |