Vibe-coding on Creatio mostly produces broken pseudo-code out of the box. Here's the fix that got me to ~90% working code, plus an open repo you can use today.
Before getting to the main topic, I want to put my general take on vibe-coding on the table: for strong, experienced developers it's a massive force multiplier, it speeds up writing the kind of code you've already written a dozen times. For less experienced developers, from what I see, two problems consistently show up:
They can't describe - technically and conceptually, what actually needs to be built.
They trust the output too much, which turns the session into endless rework instead of just reading the implementation and noticing it does something completely different from what was asked.
Now to the main topic.
Working with Creatio as a developer, I couldn't ignore the vibe-coding wave. Even though Creatio positions itself as a No-Code platform, in practice you still mix No-Code and Hard-Code for a meaningful share of tasks, and in my opinion that's a big plus. The platform gives you huge speed via No-Code while still letting you build the most complex, high-load processes in Hard-Code. That's a strong balance between time-to-delivery and runtime performance.
The main problem I ran into when trying to vibe-code on Creatio: there is no solid, large base of examples - how it should be done, how it shouldn't, what the trade-offs between approaches are. As a result, my AI agent kept generating pseudo-code that mostly didn't work.
To solve this, I built an open repository with examples for both Backend and Frontend. I took everything I'd accumulated over my years of work with the platform and standardized it into a single reference base. Now, when I start a new project, I just point my agent at this folder. It indexes the file names, pulls the relevant example when it needs to implement something, and generates code that works out of the box in roughly 90% of cases.
This has dramatically optimized a large part of my projects, though some pieces I still write by hand because of strict security constraints.
So this post is also a request: if you have interesting examples and want to help grow the Creatio developer community, send them over or open a pull request. I'll standardize them and add them to the shared base.
To close - use this wisely and keep learning the platform. Asking an AI to write code is no longer the hard part. Making that code high-quality, fitting it into a coherent architecture, and keeping it easy to change (following SOLID) is still on you.
Repo: