A clean folder structure is not a substitute for good component boundaries, but both help. In this post we walk through the conventions I use for naming, splitting, and composing components — including the difference between container and presentational components in a Server Components world, how to design component APIs that resist misuse, and how to introduce animation with Framer Motion without turning your codebase into spaghetti.

Key takeaways

• Start from the problem you are trying to solve, not the tool you want to use.
• Measure the baseline first — most improvement ideas fail without one.
• Close the loop: review, write down what you learned, and share it.

Thanks for reading

If you found this article useful, you'll probably enjoy the rest of the writing in this category — a mix of practical field notes and framework-agnostic engineering ideas.