القائمة
Run or rebuild the local Tamagui/Next.js frontend (frontends/tamagui). Use when the user wants to start the Tamagui dev server or rebuild it standalone.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run, build, screenshot, or regenerate protos for the local Elm SPA frontend (frontends/elm-spa). Use when the user wants to start the Elm dev server, check an Elm change standalone, or drive/screenshot a page in a headless browser.
Add a new app-wide "Shared panel" (like Accounts/Starred Posts/Markdown) to the Elm SPA (frontends/elm-spa). Use when asked to add a new global overlay/panel driven from Shared.Model, not page-local state.
Call a Jonline gRPC RPC (from protos/*.proto) from Elm SPA code (frontends/elm-spa). Use when writing or wiring up a new fetch/mutation against the backend from a page or Shared panel.
Regenerate protobuf bindings and docs for all Jonline frontends/backend after editing .proto files. Use when the user changes anything under protos/ or asks to regenerate protos/docs/graphs.
Run or rebuild the local Jonline Rust backend, with or without a frontend baked in. Use when the user wants to start/restart the backend server, test backend changes, or check a Tamagui/Elm change as served by the Rust server itself.
| name | run-tamagui |
| description | Run or rebuild the local Tamagui/Next.js frontend (frontends/tamagui). Use when the user wants to start the Tamagui dev server or rebuild it standalone. |
Jonline's Tamagui frontend lives in frontends/tamagui (Tamagui + Next.js) and is driven through its own Makefile.
cd frontends/tamagui && make run_dev_server
yarn web, a Next.js dev server.cd frontends/tamagui && make rebuild_fe
yarn tsc && yarn build && yarn web:prod:build (with NODE_OPTIONS=--max-old-space-size=8192).make upgrade_tamagui runs yarn upgrade:tamagui then rebuild_fe.yarn protos (invoked by the root make protos target — see the rebuild-protos skill).Tamagui is noticeably slower and more painful to iterate with than Elm. Unless the user specifically wants the standalone Next.js dev server, prefer validating changes through the Rust backend instead, via the run-backend skill's:
cd backend && make rebuild_tamagui_and_run
This rebuilds the Tamagui FE and serves it from the Rust server (ports 80/8000), which is generally a more reliable way to check a change end-to-end.