EDIT: Check https://github.com/Snownee/Cuisine/wiki first

For guys who want to modify recipes before this done: use /ct dumpzs

To be honest, that doesnt really help all that much. Well from what I saw from the dump.
It's better to just look into the source code and read the files.
It tells you what goes where, and it's much easier to sift though.

This is what I already have been using:

mods.cuisine.AxeChopping.remove(<INPUT:ITEM>);
mods.cuisine.AxeChopping.add(<INPUT:ITEM>, <OUTPUT:ITEM>);

mods.cuisine.BasinHeating.remove(<INPUT:LIQUID>);
mods.cuisine.BasinHeating.add("RECIPEID", <INPUT:LIQUID>, <OUTPUT:ITEM>);

mods.cuisine.BasinSqueezing.remove(<INPUT:ITEM>);
mods.cuisine.BasinSqueezing.add("RECIPEID", <INPUT:ITEM>, <OUTPUT:LIQUID>);

@Fortist
One thing that hasn't been settled is that, should we provide methods without passing recipe_id as 1st param.? The intent of using recipe id is to allow fine control over built-in recipes as well as Patchouli support (a special manual page that display a specific recipe). These might not be needed for all people...

@3TUSK I think pack makers should set input and output item by themselves. We only provide the layout. Requiring recipe id in CraftTweaker integration is an excess