القائمة
Run validation checks in Flipbook, Storyteller, or ModuleLoader. Use when: running tests, lint, analyze, CI checks, quality checks, or verifying changes 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 | run-flipbook-checks |
| description | Run validation checks in Flipbook, Storyteller, or ModuleLoader. Use when: running tests, lint, analyze, CI checks, quality checks, or verifying changes in the Flipbook repo family. |
| type | process |
Always use lute run tasks before lower-level commands. Runs Selene, StyLua, luau-lsp, Jest, and Rocale.
For dependency verification (testing local storyteller or module-loader changes), see test-dependencies-in-flipbook. For evidence standards and test anatomy, see flipbook-validation-and-qa. For build channel/target details, see flipbook-build-and-toolchain. For test filtering and output parsing, see flipbook-diagnostics-and-tooling.
lute run lint
lute run analyze
lute run test
All commands run from the repo root. No setup required beyond lute run install (see setup-flipbook-dev-env).
lute run lint
Runs checks in order:
--check: Code formatting validation on all project folders..lua files (error; should be .luau).Passes when all checks succeed and no .lua files are found.
lute run analyze
Runs luau-lsp with two passes:
--platform=standard and --flag:LuauSolverV2=true on the scripts directory.If local setup is missing (sourcemap not generated), run lute run install first.
lute run test
lute run test --filter "PartialFileName"
lute run test --apiKey "YOUR_KEY"
Builds plugin with --channel dev --clean, generates Rocale test place, and runs Jest via Rocale.
Requires: ROBLOX_API_KEY environment variable (from .env) or --apiKey flag. Place and universe IDs are read from .env.template (grep for ROBLOX_UNIT_TESTING_). If key is unavailable, tests cannot run; use lute run lint and lute run analyze instead.
--filter accepts a filename pattern to run only matching test files (e.g., "Story" to run Story.test.luau). Useful for focused test runs when changed area has a clear test pattern.
Date stamped: as of 2026-07-02.
Re-verify these claims when this skill next loads:
head -40 .lute/lint.luau to confirm selene, stylua, lua-vs-luau checks existgrep "platform=standard\|LuauSolverV2" .lute/analyze.luau to confirm passesgrep -A 3 "args:add(\"apiKey\"\|args:add(\"filter\"" .lute/test.luau to verify optionsgrep "ROBLOX_API_KEY or" .lute/test.luau to confirm required checkgrep "ROBLOX_UNIT_TESTING" .env.template to verify IDs are defined