Ceres Flow
SkillDev toolsBuild or diagnose Ceres Flow containers, executable nodes, functions, events, code generation, IL post-processing, and hot reload.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Ceres Flow skill
What this skill tells your AI
The instructions your AI receives, as published by akikurisu/ceres in Plugins/ceres/skills/ceres-flow/SKILL.md and read by ahel’s review.
Inspect the current runtime and Editor Flow assemblies before extending execution behavior. Use Graph guidance as well when a change modifies shared graph serialization, variables, ports, or editor foundations.
References
- Read containers-and-codegen.md for container selection,
[GenerateFlow], generated runtime ownership, and lifecycle. - Read events-and-functions.md for implementable events, executable functions, libraries, and custom executable events.
- Read custom-nodes.md for node base classes, ports, arrays, generics, metadata, and editor views.
- Read troubleshooting.md when discovery, generation, ILPP, preservation, validation, or hot reload fails.
Prefer executable functions for stateless API exposure. Create a custom node only when behavior needs state, execution control, dynamic ports, async flow, or a specialized editor shape. Do not promise a stable programmatic GraphBuilder API without inspecting the current source.
Signals
- GitHub stars
- 129
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
ceres-flow- Source
- github.com/akikurisu/ceres