Proposal: New templates for scaffolding (Components, Hooks, Context, etc.)

[Israelamat]

💡 Context

Our goal with react-isr-cli is to automate the repetitive work of creating file structures. Currently, we have standard templates for interfaces, services, and components, but the React ecosystem is huge!

We want to open this space for the community to suggest or contribute new templates that follow best practices and "Clean Architecture".

🎯 The Challenge

We are looking for proposals for new templates that can be generated via the rg command.

Some ideas to get started:

• 🎣 Custom Hooks: A standard structure for use... hooks.
• 📁 Context API: A folder with Context, Provider, and Reducer.
• 🧪 Unit Tests: Automatic generation of .test.tsx or .spec.tsx files.
• 🎨 Styled Components / Tailwind: Templates that include styling boilerplate.
• 👔 Redux/Zustand Slices: Logic for state management.

🛠️ How to participate?

1. Comment below: Tell us what template you would like to see and why it would be useful.
2. Technical Proposal: If you can, provide a snippet of how the generated code should look.
3. Contribute: If you want to code it yourself, let us know! We will guide you through the process of adding it to the src/templates folder.

---

This is a good first issue! Don't be shy, every idea is welcome. Let's make React development faster together! 🚀

[ea57-ua]

Great initiative! It would be fantastic to have a template for Zustand or DaisyUI modals. I'm following the project closely!

[Israelamat]

I'm currently working on making the CLI more interactive. If you have any ideas for new templates—like specific hooks or state management structures—feel free to drop a comment in the 'Proposals' issue. Getting different perspectives is what helps the tool grow.

[Aracelyhub]

Hi! Nice work on this CLI — it looks like a useful tool for starting React projects from scratch.

Allowing the routes file to be configurable would be really helpful, since this part often depends a lot on the specific project and isn't very standard.
Right now, having to manually adjust it (or remove certain lines to avoid ESLint issues with Vite) can cause errors.
Providing more flexibility or options during setup would make it easier to use this CLI in real projects, not just as a basic starter template.

[Israelamat]

Thanks for the feedback. I agree—the routing structure needs more flexibility to avoid those ESLint/Vite conflicts in real environments.

I'll look into this and study how to make it more configurable. If you have a specific implementation in mind or a better template, feel free to open a PR. Contributions are welcome.