> they require manually writing templates for the frameworks the ones i've used come with defaults that you can then customize. here are some of the better one

> they require manually writing templates for the frameworks the ones i've used come with defaults that you can then customize. here are some of the better ones: - https://guides.rubyonrails.org/command_line.html#generating-code https://guides.rubyonrails.org/command_line.html#generating-... - https://hexdocs.pm/phoenix/Mix.Tasks.Phx.Gen.html https://hexdocs.pm/phoenix/Mix.Tasks.Phx.Gen.html - https://laravel.com/docs/13.x/artisan#stub-customization https://laravel.com/docs/13.x/artisan#stub-customization - https://learn.microsoft.com/en-us/aspnet/core/fundamentals/tools/dotnet-aspnet-codegenerator?view=aspnetcore-10.0 https://learn.microsoft.com/en-us/aspnet/core/fundamentals/t... > my experience has been these get left behind as the service implementations change yeah i've definitely seen this, ultimately it comes down to your culture / ensuring time is invested in devex. an approach that helps avoid drift is generating directly from an _actual_ project instead of using something like yeoman, but that's quite involved