Define Component Boundaries
When splitting a large component, describe exactly what each piece owns: its props, its rendering responsibility, and where the data comes from. Without clear boundaries, Claude might split the code in ways that create awkward prop drilling or misplaced logic.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Split the Component
Your `Dashboard.tsx` file has grown to over 300 lines. It renders three distinct sections: a stats panel at the top showing KPI cards, an activity feed in the middle with a scrollable list of recent events, and a quick actions sidebar with shortcut buttons. All the state, data…