electron-rare/le-mystere-professeur-zacus
1
0
Fork 0
Code Issues 1 Pull Requests 2 Actions 1 Packages Projects Releases Wiki Activity
Files
d31d8af1807efa58e154863c92f35c58d91089e4
le-mystere-professeur-zacus/frontend-v3/CLAUDE.md
T
L'électron rare d31d8af180 docs: nested CLAUDE.md via init-deep 
Slim root CLAUDE.md (90 lines) and add 7 nested CLAUDE.md
files for progressive disclosure. Each nested file loads
automatically when Claude reads files in that directory.

Nested files:
- game/        scenarios + NPC phrases (source-of-truth)
- tools/       Python tooling (Runtime 3, TTS, MCP, dev CLI)
- tests/       Python unittest patterns
- specs/       contracts governance
- frontend-scratch-v2/  React 19 + Blockly + Vite (legacy)
- frontend-v3/ pnpm monorepo (production target)
- desktop/     Electron Zacus Studio (macOS)

Root CLAUDE.md gains a Where-to-Look table and pointer to
nested guidance. ESP32_ZACUS submodule is intentionally not
covered (separate repo with its own CI).
2026-05-01 11:44:17 +02:00

1.8 KiB
Raw Blame History

Frontend V3 (Monorepo)

pnpm + turbo monorepo. Three apps + three shared packages. Node ≥20, pnpm ≥9.

Layout

apps/
  dashboard/         # Live game-master dashboard (analytics, control)
  editor/            # Scenario editor (V3 successor of frontend-scratch-v2)
  simulation/        # Runtime simulator / playtest UI
packages/
  scenario-engine/   # Runtime 3 IR + execution (shared core)
  shared/            # Cross-app utilities, types, constants
  ui/                # Shared component library

Commands

pnpm install            # Bootstrap workspace
pnpm dev                # turbo run dev (all apps)
pnpm --filter dashboard dev   # Single app
pnpm build              # turbo run build
pnpm test               # turbo run test
pnpm typecheck          # turbo run typecheck
pnpm lint               # turbo run lint

Patterns

  • scenario-engine is the canonical TS Runtime 3 implementation. New apps consume it; do not fork the IR.
  • All cross-app types live in packages/shared — never copy-paste types between apps.
  • Components shared across ≥2 apps move to packages/ui. Keep app-local components in apps/<app>/src/components.
  • Turbo cache keys: ensure inputs in turbo.json cover all source paths; missing globs cause stale cache.

V2 vs V3

  • frontend-scratch-v2/ is the legacy single-app Vite playground. V3 is the production target.
  • When porting features from V2, extract reusable logic into packages/scenario-engine or packages/shared first.
  • Do not symlink or import across V2/V3 boundaries.

Anti-Patterns

  • Adding deps to root package.json (use the relevant app/package)
  • Bypassing turbo with manual tsc invocations — breaks cache invalidation
  • Circular dependencies between packages (turbo will warn; fix immediately)
  • Publishing packages/* to npm — they're internal workspace-only
Reference in New Issue View Git Blame Copy Permalink