# Develop Through Studioplugins

> Special internal workflow for testing FlipbookCore changes through the StudioPlugins Flipbook plugin. Use only when the engineer explicitly asks to verify Flipbook through StudioPlugins, mentions StudioPlugins with FlipbookCore local rotriever builds, or says the StudioPlugins Flipbook watcher is already running. Use when this capability is needed.

- Skill: `tomevault-io/develop-through-studioplugins` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/develop-through-studioplugins`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/develop-through-studioplugins/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/develop-through-studioplugins

---


# Develop Through StudioPlugins

This is a special internal workflow for testing this repo's `FlipbookCore` changes through the StudioPlugins repo. Do not use it as the default Flipbook development path.

## Setup

1. Build FlipbookCore from the `flipbook` repo:

```bash
lute run build --target rotriever --clean
```

The output path is `build/flipbook-core-rotriever/`.

2. In the StudioPlugins repo's Flipbook Rotriever manifest, point `FlipbookCore` at the local build output:

```toml
[dependencies]
FlipbookCore = { path = "/path/to/flipbook/build/flipbook-core-rotriever" }
```

3. Build the StudioPlugins Flipbook plugin.

## Agent-Run Loop

For each iteration:

1. The agent rebuilds FlipbookCore. From the `flipbook` repo:

```bash
lute run build --target rotriever --clean
```

2. The agent rebuilds the StudioPlugins Flipbook plugin using the engineer's documented build command for that repo. Ask the engineer for the exact command if it cannot be determined.

Studio will reload the plugin automatically once the build completes.

## Dependency Changes

Only run these overlay steps when the current task actually changed that dependency repo:

```bash
# from the module-loader repo, if this task changed it
lute run try-in-flipbook

# from the storyteller repo, if this task changed it
lute run try-in-flipbook
```

When StudioPlugins points `FlipbookCore` at the local rotriever output, its watcher should pick up the rebuilt bundle automatically. Do not ask the engineer to run the FlipbookCore rebuild manually; run it from the agent unless the command fails and needs human intervention.

---
> Source: [flipbook-labs/flipbook](https://github.com/flipbook-labs/flipbook) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-07-04 -->