run-tamagui
SkillDev toolsRun 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the run-tamagui skill
What this skill tells your AI
The instructions your AI receives, as published by jonlatane/jonline in .claude/skills/run-tamagui/SKILL.md and read by ahel’s review.
Rellm's Tamagui frontend lives in frontends/tamagui (Tamagui + Next.js) and is driven through its own Makefile.
Running the dev server
cd frontends/tamagui && make run_dev_server
- Runs
yarn web, a Next.js dev server. - Serves on port 3000 locally.
- The user often has this running themselves already — it's fine to kill and restart it.
Rebuilding
cd frontends/tamagui && make rebuild_fe
- Runs
yarn tsc && yarn build && yarn web:prod:build(withNODE_OPTIONS=--max-old-space-size=8192). make upgrade_tamaguirunsyarn upgrade:tamaguithenrebuild_fe.- Protos:
yarn protos(invoked by the rootmake protostarget — see therebuild-protosskill).
Prefer the backend-driven workflow for checking changes
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.
Signals
- GitHub stars
- 65
- Forks
- 5
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
run-tamagui- Source
- github.com/jonlatane/jonline