Frontend Component Boundaries

Decide where to cut a frontend component's boundary by cohesion, behavior, semantics, reuse, and shared reasons to change — not by a mechanical "one responsibility per component" rule that produces ceremonial fragmentation. Use whenever creating a new component, splitting or merging existing ones, or reviewing a PR that adds/removes component files. Trigger on "should this be its own component", "this component is doing too much", "prop drilling", "too many props", "extract a component", "where does this state live". Not a naming/style-guide skill — it's about the structural decision of where the boundary goes.

annatchijova Updated 9 repo stars

File contents

annatchijova/skills commit 67933a93d4

Frequently asked questions

npx get-skill add annatchijova/frontend-component-boundaries