// The person behind the code
Camilo

I'm Camilo, a creative developer. I turned what I learned building sites for clients in 7+ countries into a tool any designer can use — no code, no limits.

  • 7+ Countries
  • 100+ Sites Built
  • Since 2019
// Chapter 01

I was losing hours.

Every project started the same way — wiring GSAP into Elementor, debugging scroll conflicts, rewriting the same code I'd written a dozen times. Scripts broke between projects. Clients couldn't touch it without calling me.

// another-client-site.js
gsap.registerPlugin(ScrollTrigger);
gsap.to('.hero-img', { y: -120, scrollTrigger: {
  Uncaught TypeError: Cannot read properties
  of undefined (reading 'scrollTrigger')
});
// TODO: fix this AGAIN for the 4th time...
// copy-pasted from previous project
  GSAP conflict with Elementor motion effects
// Chapter 02

Then I systematized everything.

I built an internal library. Same effects, zero debugging. What used to take days took minutes. My delivery speed doubled. My quotes went up. Clients noticed the difference.

×1.0 Budget increase
÷1.0 Delivery time
100% Fewer GSAP conflicts
// Chapter 03

So I turned it
into a product.

If this system changed how I work, it could change how every Elementor designer works. No code. No conflicts. Just drag, drop, and ship.

Pro Effects Now available
Camilo
// The track record

I didn't start
with a product.

Pro Effects was born inside SNC Designs, my agency. Every effect in this plugin was battle-tested on real client projects before it became a product.

7+ Countries served
100+ Projects delivered
5+ Years as agency
Visit SNC Designs
// How I build

Designed by someone
who uses it every day.

Every decision in Pro Effects comes from a real problem I hit on a real project. These aren't product principles — they're production scars.

01

Isolation by default

Each widget runs in its own scope. No global conflicts, no GSAP collisions. Because I got burned too many times by effects breaking each other on the same page.

02

Zero code, full control

Every parameter is exposed in Elementor's panel. No custom JS snippets, no functions.php hacks. If a client can use Elementor, they can use Pro Effects.

03

Production-first testing

I don't ship effects that only work in demos. Every widget is tested on live sites with real traffic, real caching, real page builders stacked together.

04

Custom effects exist for a reason

No library covers 100% of cases. That's why the custom effect service exists — I know the gap because I've lived it on every project that needed something unique.

05

Performance is non-negotiable

Lazy-loaded scripts. No render-blocking. Sub-50ms init. My clients' PageSpeed scores pay my bills — I'd never ship something that tanks them.

06

Updates ship from real projects

Every new effect or improvement comes from a client project at SNC Designs. The roadmap isn't a wishlist — it's what I'm actively building for paying clients.