superpowers-flow
The routing layer for superpowers skills. This file tells the agent WHEN to Skills by Jesse Vincent (https://github.com/obra/superpowers, MIT). FLOW.md routing by Flowy (https://flowy.dev).
Loading...
Skills are powerful. Most are trash. Flowy hand-picks the best and glues them with a FLOW.md that auto-invokes the right skill at the right moment based on your intent and context. You just prompt.
A big messy pile of skills. A Flow auto-invokes the perfect skill for the moment, based on your intent and context. You just prompt.
your skills
your Flow
Loads once. Runs for about 40 tokens a prompt. See the cost ↓
Load the Flow once. After that it routes you to the perfect skill every time you prompt. About 40 tokens a turn.
One install line. Your agent reads it a single time.
agent context
So you just prompt, and it fires the exact skill you need. No skill names. No searching.
↻ every prompt · ≈40 tokens
You prompt. It routes you to the perfect skill.
One messy prompt, four problems. The Flow scoped all four before it wrote a line.
Token cost
You load the Flow once. After that, your agent reads the routing straight from context. About 40 tokens a prompt, not the whole file every turn.
fewer tokens over a 50-prompt session.
measured on superpowers-flow · ≈4 chars/token estimate
You can. Then you are the router, every prompt. Or Flowy auto-invokes the perfect skill for the task, and you just prompt.
The AI auto-invokes the perfect skill for your task.
Got a routing pattern you run every day? Ship it. We review every one. Merged Flows join the library: credit, open source, free.
$ git clone https://github.com/MaximoCorrea1/flowy-flows $ cd flowy-flows && cp -r flow.template flow.your-name $ # edit FLOW.md + README.md: declare the goal and the steps $ gh pr create --title "Add flow: your-name"
Drop your skills repo. A Flow gets built. Install the plugin and your own skills start auto-invoking, by your intent and context.
Your team has its own skills for its own workflow. Build the Flow once. They fire by intent. Save the time, save the mental energy.
Any folder of skills. Point Flowy at it.
Flowy wraps them with a FLOW.md router.
Your own skills, fired by your intent and context.
Stay tuned. One short note the day it ships.
Roadmap: team flows, gated delivery, creator earningsDon't let your agent go wild. Harness it.
One install covers every Flow. You just prompt.
Install in Claude Code
> /plugin marketplace add MaximoCorrea1/flowy-flows> /plugin install flowy@flowy-flows
The routing layer for superpowers skills. This file tells the agent WHEN to Skills by Jesse Vincent (https://github.com/obra/superpowers, MIT). FLOW.md routing by Flowy (https://flowy.dev).
Grow a product across the funnel, from customer research to a measured experiment, firing the right marketing skill per intent and refusing to call a result a win until a number moves.
Take a Next.js UI task from first keystroke to a fast, accessible, deployed page, firing the right Vercel skill at each phase.
Build front-end work that looks deliberate and is proven to run, by routing the design, test, and skill-authoring steps to the right skill and refusing to call UI "done" until it has been driven again
Take a software change from a written spec to a tested, hardened, shipped release, firing the right engineering skill at each step.
Carry a change from a raw issue through a sharpened model, a designed interface, a test-first build, a diagnosed fix, and a clean handoff, firing the right discipline at each step.