メニュー
Set up or repair the Flipbook, Storyteller, or ModuleLoader development environment. Use when: first-time setup, installing dependencies, managing .env files, troubleshooting rokit/wally/lute, or repairing stale tooling in the Flipbook repo family.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Special workflow for testing FlipbookCore changes through the StudioPlugins Flipbook plugin. Use only when: the engineer explicitly asks to verify changes through StudioPlugins, mentions StudioPlugins with local FlipbookCore rotriever builds, or says the StudioPlugins watcher is already running.
Load-bearing design decisions, invariants, and known weak points of Flipbook's architecture. Use when understanding or extending system design, debugging architectural mismatches, or validating deep changes (PR
Understanding the Flipbook build system from environment setup through final deployment; source→rbxm pipeline with deep focus on Darklua require transformation, environment globals injection, and dead-code elimination
Classification, gating, and review discipline for Flipbook changes: branch/PR workflow, version gating, CI gates, change-type decision table, community-first and telemetry-privacy doctrine, and the non-negotiables with their historical incidents. Use when authoring a PR, reviewing change control, understanding release requirements, or evaluating whether a change is safe to merge.
Community-first doctrine, telemetry/privacy posture, ecosystem positioning vs web Storybook and UI Labs, and claim discipline for Flipbook features
Configuration axes (env vars, injected globals, build channels/targets, user settings); adding new config; re-verification commands
| name | setup-flipbook-dev-env |
| description | Set up or repair the Flipbook, Storyteller, or ModuleLoader development environment. Use when: first-time setup, installing dependencies, managing .env files, troubleshooting rokit/wally/lute, or repairing stale tooling in the Flipbook repo family. |
| type | process |
First-time setup or when package/tooling state looks stale. Rokit installs tools; Wally installs packages; Lute runs builds and tests.
For testing local dependency changes (storyteller or module-loader), see test-dependencies-in-flipbook. For running lint/analyze/test tasks, see run-flipbook-checks. For toolchain details, see flipbook-build-and-toolchain.
flipbook, storyteller, and module-loader are expected to be sibling checkouts:
~/git/flipbook
~/git/storyteller
~/git/module-loader
The install script detects and works with any repo in this family.
Run these commands from the repo root:
rokit install
lute run install
For flipbook only, ensure a .env file exists:
cp .env.template .env
Required: BASE_URL in .env must be set to https://apis.flipbooklabs.com (the default in .env.template). The build task checks for this value (anchor: if not process.env.BASE_URL in .lute/build.luau).
lute run install DoesPackages/.LuauPackages/."Cannot resolve packages" — lute run tasks failing with unresolved imports: run lute run install again.
Stale build output after dependency changes — Use lute run build --clean for a full rebuild from scratch.
"ERROR No such file or directory (os error 2)" — Rokit is trying to invoke a tool it has not installed. Run rokit install to recover.
Do not edit Packages/ or LuauPackages/ directly — these are generated. Regenerate with lute run install if needed.
Date stamped: as of 2026-07-02.
Re-verify these claims when this skill next loads:
rokit.toml presence and tool list: run cat rokit.toml | grep "^\[" to confirm tools section exists.env.template contents: run grep BASE_URL .env.template to confirm default is https://apis.flipbooklabs.comgrep -n "if not process.env.BASE_URL" .lute/build.luau to verify anchor existslute run install availability: run lute run install --help from repo root