Most shortcuts that lean on a function library make you copy actions in by hand, hoping you didn’t fumble a rename halfway through. Cyclone Studio skips that step, since it’s a fork of Join Shortcuts built for one job: wiring the Cyclone dependency into whatever you’re building without you touching the block yourself.

What it actually does

Under the hood it runs on gluebyte’s Join Shortcuts, the merge tool a lot of RoutineHub authors already use. This fork narrows that logic to one purpose: inserting Cyclone, the Cyclone Library dependency, into a project you’re already working on. Point it at your shortcut and it stitches the block in for you.

Version 1.3.0, released 28 June 2026, changed what gets inserted. Its author switched the embedded dependency to a newer “Lite Loader” and added a prompt so you can install that Lite Loader on your device in the same pass, rather than tracking it down separately afterward.

How to install

Tap Add Shortcut on this page to open Cyclone Studio in the Shortcuts app.
Scroll the preview to the bottom and tap Add Shortcut to confirm.
Run it once, choose the shortcut you want to modify, then pick where the Cyclone block should land.
Decide whether to install the Lite Loader alongside the embed if you’re asked, or handle that separately.

Nothing beyond the Shortcuts app itself is required to run it.

How to use it

Its workflow mirrors Join Shortcuts, the tool this one was forked from: pick a main shortcut, then choose from a list of comment-marked insertion points for where the new block should go. Only Cyclone ever lands there, not a picker full of unrelated shortcuts. Because it runs on that same merge mechanic, it can drop the dependency near the start, at the end, or right after a comment action you’ve placed as a marker, whichever matches how your project is structured. Each run only touches the shortcut you select.

Where it comes in handy

Publishing a new shortcut on RoutineHub that calls Cyclone’s global variables, styled menus, or other library functions.
Updating an older published shortcut to the newer Lite Loader without manually deleting and rebuilding the old block.
Adding Cyclone to a shortcut forked from someone else, when the original never depended on it.
Testing a spare copy of a project to confirm it behaves once Cyclone is wired in, before publishing the real version.

Keep in mind

This is a developer utility, not something the average person running a finished shortcut opens directly. Cyclone reaches most users through the shortcuts they download, not by them running this one. It needs nothing beyond Shortcuts itself, though it does need an existing shortcut to work on — there’s nothing to embed anything into on a blank canvas.

FAQ

Do I need this if I’m just using a shortcut that already calls Cyclone?

Nope. This is strictly a build-time tool for the person making the shortcut. If you downloaded one that already depends on Cyclone, the loader it needs ships as part of that shortcut, and Cyclone Studio never enters the picture.

What changed in version 1.3.0?

A 28 June 2026 update swapped the block it embeds from the older loader over to a newer, smaller Lite Loader, and it now asks whether you want that Lite Loader installed on your device at the same time.

Isn’t this the same thing as the Cyclone Library?

Not quite. Cyclone Library is the actual function toolkit your shortcuts call into. This shortcut is the fork of Join Shortcuts that stitches the loader for that toolkit into a project you’re building, so the two handle different halves of the job.