Plan: Transitioning to Forward Deployed Engineer / AI Engineer
一份分階段路線圖,供後端工程師轉向 FDE 與 AI Engineer 角色——解讀頭銜混亂、應用型 LLM 技術棧與面試循環。
AI 翻譯
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證製作者的介紹僅有上面的一句話。 更多詳情請閱讀儲存庫 README。 儲存庫 README ↗
正在載入完整 README。
檢視完整 README ↗A browser-based 3D simulation of a UHT milk plant in three.js, from standardization to ambient distribution: ten stages running live, six fault scenarios, and a guided tour. The research, design and schedule are in plan/; the build is split into phases and agents in plan/agent-plan/.
Live: https://sophanit-keo.github.io/simulation-milk-process/, deployed to GitHub Pages from master each time CI passes there. It needs a browser with WebGL 2; it is checked in Chrome and Edge.
factory.html. Sign in with a Let Report account to see the real factory live: UHT 1, 2 and 3, the lines each one feeds, and each line's status, product, lot, CIP and open troubles, as Let Report holds them. A change in Let Report shows within a second (D19, phase 9). Which UHT feeds a line, its filler, speed and pack size are edited in Let Report.
factory.html#3d opens it (D20, phase 10).The plant opens the same way every time: day 8 at 06:00, ×10, seed 81006. URL options: ?mock runs the UI on the mock snapshot, ?debug adds lil-gui and window.__scene, ?greybox shows the grey boxes instead of the hero models.
Needs Node 22.13 or later (22.x LTS or 24.x; see .nvmrc).
npm ci
npm run dev # http://localhost:5173
npm run build # production build in dist/ (CI sets BASE_PATH=/simulation-milk-process/ for GitHub Pages)
npm run preview # serves dist/
npm run check # typecheck, lint, unit tests (Vitest) and asset tests: what CI runs first
npm test # unit tests only: formulas, acceptance runs, the 60-day run, scenarios, the demo script
npm run test:assets # the 3D models and textures against their specs and budgets
npm run e2e # browser tests (Playwright, Chromium); `npx playwright install chromium` once
Performance (needs a build, see tests/perf/baseline.md):
npm run build
node tests/perf/measure.mjs # draw calls, triangles and fps at every stage
node tests/perf/measure.mjs --path 60 --headed --channel chrome # the 60 fps check: a 60 s camera path at ×1 and ×10,000
| Document | What |
|---|---|
| docs/report.md | The report, with the technical chapter |
| docs/demo-script.md | The live demo, step by step, with the numbers to expect |
| docs/video-script.md | The demo video's shots and narration |
| docs/slides.md | The presentation, slide by slide |
| plan/DECISIONS.md, plan/hand-calculations.md | Every default with its source, and every expected value the tests check |
| Path | What | Owner agent |
|---|---|---|
src/contracts/ | Types every part shares: PlantConfig, Snapshot, Command, ViewEvent, units | lead |
src/data/plant.json | Default settings; decisions in plan/DECISIONS.md | process |
src/sim/ | Simulation core: clock, event queue, models, fault scenarios. No three.js, no DOM | sim |
src/scene/ | 3D view | scene |
src/ui/, src/styles/, index.html | Screen layout and controls | ui |
public/models/, assets/ | 3D assets and their licences | assets |
factory.html, src/factory/ | The factory board: contracts (types.ts, view.ts), the Let Report client, the model, the floor's layout, the page; no three.js until its 3D view (src/factory/scene/) opens | lead, factory-client, factory-model, factory-scene, factory-ui |
tests/, e2e/ | Unit and browser tests, and the perf check | qa |
docs/ | Report, demo and video scripts, slides | lead, process |
The agents' definitions (phases 9 to 12) are in .claude/agents/.