Analyze your project · compose visual workflows · forge zero-dependency setup scripts
{
"steps": [
{ "type": "input", "prompt": "Project name" }
{ "type": "check", "condition": "node --version" },
{ "type": "command", "run": "npm install" },
{ "type": "command", "run": "npm run dev" },
]
}From raw project to one-command setup — in three steps.
Scans your project directory — package.json, config files, scripts, dependencies — and suggests a starter workflow. No need to model from scratch; the Analyzer detects the setup patterns already in your project.
For maintainers: Maintainers save hours: point Project Igniter at your repo, get a workflow draft that captures your existing setup. Tweak and ship.
Visual tree editor for modeling project setup. 9 step types, drag-to-reorder, recursive branching, 3-panel layout with context variables and property inspector.
For maintainers: Model your entire setup process visually — inputs, commands, checks, conditionals, OS branches. Every step is configurable and the tree structure maps naturally to setup logic.
Converts visual workflows into zero-dependency Bash and PowerShell scripts. No Node.js, no Tauri, no runtime required — just native shell.
For maintainers: Define separate workflows per environment. Contributors run `bash setup.sh --env dev` or `--env prod`. Drift detection warns when workflows change. Monorepo support built in.
Zero to running in a single command.
Branch workflows by OS. Generated scripts run everywhere.
Workflows stored as JSON — PR-reviewable, version-controlled.
User input, env vars, and computed values flow across steps.
Nest branches within branches. Handle any complexity.
User answers saved locally. Re-run without re-typing.
Define a separate workflow for dev, staging, and production. Contributors pick the right setup with a single flag.
./setup.sh --env dev./setup.sh --env staging./setup.sh --env prodAnalyze → Compose → Forge. A three-phase pipeline from project to one-command setup.
Project Analyzer
Point the Analyzer at any project directory. It scans package.json, config files, scripts, and dependency manifests to understand your project's setup patterns. The output is a starter workflow — no blank canvas needed.
Workflow Composer
Open the visual tree editor. Drag to reorder steps, add branches for different OSes and conditions, configure properties in the side panel. Every step type maps to a real action: prompt for input, run a command, check a condition, write a file.
Script Forge
Hit generate and the Composer output — a JSON workflow tree — is compiled into zero-dependency Bash and PowerShell scripts. No runtime needed. Commit them to your repo and contributors run `bash setup.sh --env dev` to get started, `--env staging` for pre-release, or `--env prod` for production deployment.
A visual workflow editor that makes setup modeling intuitive.
Workflow Tree Editor
Drag-to-reorder steps, expand branches, add new steps — all visually.
Properties Panel
Configure each step's behavior — commands, conditions, inputs, and more.
Context Variables
Track all variables used across steps — inputs, conditions, and outputs.
Current status and what's coming down the pipeline.
The converter works end-to-end: Bash and PowerShell generation, state machine dispatch, drift detection, monorepo support. Current focus is on optimising output quality — cleaner generated scripts, better error handling, faster generation.
The Analyzer will scan a project directory and produce a starter workflow. It detects package managers (npm, pip, cargo, etc.), config files, build scripts, and environment requirements. Maintainers get a draft workflow they can refine in the Composer — no need to model from scratch.
Beyond generated shell scripts — a dedicated runtime that executes workflows natively. Rich UI, progress reporting, interactive prompts, and real-time feedback during setup.
Early development — preview builds coming soon. Star the repo to stay updated.