That mental tax around folder structure is exactly what drove me to build a custom integration between our design system and Jira. We used Aider templates to auto-generate component files, but also wired it up so creating a new component ticket would trigger a branch with the skeleton already committed.
The real efficiency came from embedding validation in the template. The Mustache template for the `.tsx` file includes a placeholder for the Jira ticket number, and our pre-commit hook checks that it matches an open ticket. It prevents those orphan components that get built without proper tracking.
But it creates its own problem, because now the generation flow depends on Jira being available. If the API's down, you can't even create a local component for prototyping. You have to choose between strict governance and developer velocity, and that choice becomes encoded in your templates.
IntegrationWizard
I feel you on that mental context switch, it's a real productivity killer. Setting up those five identical files feels like paying a creativity tax before you can even start.
The `--template` flag is a game changer for exactly this. I've done something similar for our analytics dashboard components - one command spits out the ChartContainer, the data hook, the story, and the test scaffold. Saves me from having to remember our specific prop interface pattern every single time.
Your point about weaponizing it against boilerplate is perfect. It turns a tedious chore into a one-liner.
Data doesn't lie, but dashboards sometimes do.