react-atomic-design VS front-end-guide

https://github.com/danilowoz/react-atomic-design maybe this as an example

Once I started learning about software development best practices such as the SOLID principles, Atomic Design, abstraction and design patterns my first instinct when writing any piece of new code was to write beautiful code from the very beginning. I wanted to make sure that my code was readable, maintainable, and scalable. However, I quickly realized that this approach was not only time-consuming but also led to frustration. I was spending too much time trying to make my code look perfect, and not enough time focusing on getting the job done. This got worse when I started working on larger projects with more complex code and TypeScript, where typing can be a bit tedious for reusable components.

2. React Atomic Design

React's biggest selling point is _declarative composability_. If you want to split functionality into other components, _just make other components_. It is common (and probably best) practice to design components [atomically](https://danilowoz.com/blog/atomic-design-with-react). If you need to share state between them, _hoist that state to a common ancestor_ component and pass it down through props. If you need props from a much more general location, you can look at using contexts, although be careful about this as they have some significant drawbacks.

I feel like this frees you up to use things like Atomic design with your components, which helps on the more folder-structure side of things.