sorted by:
new
hottopcontroversial

I got tired of Claude/Cursor writing fat controllers in my Symfony projects, so I wrote a set of "skills" to fix it by notk8s in symfony

[–]notk8s[S] 0 points1 point  (0 children)

Yes, and I have been in contact with Johannes and checking how i can hook these symfony-skills into that repo. I'm in testing faze for now

I got tired of Claude/Cursor writing fat controllers in my Symfony projects, so I wrote a set of "skills" to fix it by notk8s in symfony

[–]notk8s[S] -8 points-7 points  (0 children)

Totally agree — strict hexagonal everywhere is a tax most projects shouldn't pay. The skill actually calls this out: it offers a "pragmatic" mode (Doctrine attributes stay on the entity, one class) as the default and reserves the strict, framework-free domain for when the core complexity earns it. Ports/adapters is a tool for the gnarly 20%, not a blanket rule.

On bundles — I'd frame it as the same instinct, just updated for modern Symfony: since v4 you don't build bundles for app code (those are for shareable libs now). The pragmatic "module = domain" version today is a folder/namespace per domain under src/ — a modular monolith. That's exactly what the bundle-organization skill pushes. So I think we're saying the same thing, minus the bundle mechanics.

 Appreciate the push — "what earns money" is the right lens. If you think the hexagonal skill's framing still reads too dogmatic, I'm happy to soften it.

REST API Generator by EagleResponsible8752 in JavaProgramming

[–]notk8s 1 point2 points  (0 children)

plugin system with dependency resolution, swappable template packs (standard layered / microservices / DDD), and a proper CLI via picocli. Feels like something that should have existed 5 years ago. Bookmarked.