Learn how to name components. Apply the single responsibility principle. Find the indivisible component units, and compose them together into larger molecules.
Extract common styles. Define a style guide. How do you keep styles consistent?
What sort of components should be resuable? How granular should you go?
When do you need a pattern library? Who are they for? How should you manage them?
Unit test components. Test the behaviours that matter first. Use type-safety to remove impossible states.
Testing data flow
Test your data flow in isolation. Use test-driven design. Mock APIs and other sources.
Composable component patterns
Components are really composable. Can we reduce boilerplate? What useful component utilities can we make?
Handle errors from publishers. What and when should you show users?
Learn how to name components. Apply the single responsibility principle. Find the atomic units, and compose them together.
Improving performance in the right areas
Learn when you should focus on performance. Measure to be informed. Apply optimization techniques.
Automating repetitive tasks
Produce screenshots across many devices.