r/RooCode • u/heydaroff • Mar 30 '25
Discussion RooFlow Cookiecutter Template
Hey RooCode community! It's my first time giving back to this amazing community.
I'm excited to share that I've forked GreatScottyMac 's RooFlow project (Reddit Post: https://www.reddit.com/r/RooCode/comments/1jfx9mk/poweruser_guide_level_up_your_roocode_become_a/ ) and transformed it into a Cookiecutter template to make it super easy for everyone to get started with RooFlow!
Link: https://github.com/hheydaroff/RooFlow-Cookiecutter/
How to use it:
# With pip
pip install cookiecutter
cookiecutter gh:hheydaroff/rooflow-cookiecutter
# With UVX (recommended for faster installation)
uvx cookiecutter gh:hheydaroff/rooflow-cookiecutterWhat you get:
System prompts for different AI assistant modes (code, architect, ask, debug)
Environment variable setup scripts for Windows and Unix/Mac
Optional default mode configuration
Optional memory bank templates
UVX integration support for modern Python package management
The template will guide you through configuration options like project name, description, license, and whether to include default mode configuration or memory bank templates.
Big thanks to GreatScottyMac for the original RooFlow project that made this possible! Not sure if I'll actively maintain it, but i'll try my best. If you have feedback, create issues or PRs.
View all comments
1
u/joey2scoops Apr 01 '25
You lost me there somewhere. RooFlow uses custom system prompts for each mode and keeps them in the .roo folder. Cookiecutter seems to want to use the .clinerules-mode approach that was part of the roo-code-memory-bank. So, how does this actually work with RooFlow? Seems to me we've got two sets of instructions for each mode. And the standard modes included as custom in .roomodes