How Can I Start Thinking Like a Front-End Architect?

I recently stumbled upon an article that made a strong point: Front-end developers often think about components, while architects focus on flows, boundaries, and responsibilities. This really got me reflecting on whether we're just slapping buttons and boxes on a screen, or if we are actually building something sustainable and capable of growth. So, I'm curious how I can elevate my thinking from just being a developer to approaching my work more like an architect. I understand that to step up my game, I need to think bigger than just writing code. Here are a few thoughts I have:

- Each code block should have a single responsibility and not be overloaded with multiple tasks just for reusability.
- Keeping files organized is crucial, especially when collaborating with a larger team to avoid confusion.
- Consistency in style throughout the app is important, not just relying on frameworks like Tailwind.
- Accessibility should be a priority from the start—not an afterthought—so that everyone, including those with disabilities, can use our creations.
- Page load speed matters; nobody likes a sluggish site.
- Writing clear notes in the code is helpful for other developers down the line, not just users.

Any tips on adopting an architectural mindset?