mastermind-component-research

Mastermind component research

The default failure of an agent writing UI is not bad markup. It is writing a component that already exists, or changing a props contract without seeing who depends on it. Both are structural questions, and the codegraph answers them.

Answer these before writing. Evidence is a query result, not a recollection.

Does it already exist?

mmcg_search "Button"                    # exact name
mmcg_files --prefix src/components      # what the component directory holds
mmcg_centrality --prefix src/components # the components everything already leans on

Search the name you were about to invent, then the words around it. A Button may live as BaseButton, AppButton, or UiButton, and a design system rarely names things the way a ticket does. mmcg_centrality is the fastest read of a component library you do not know: the highest in-degree symbols are what the codebase actually builds on.

Report the search as evidence — the names tried and what came back. "I looked and found nothing" without the queries is not a finding, and reinvention is the most expensive mistake available here.

Who renders it?

mmcg_callers "Button"          # components that render it
mmcg_impact "Button" --depth 3 # transitive blast radius
mmcg_imported_by "Button"      # files importing it, including barrels

mmcg_callers answers "who renders this": JSX usage (<Button />) and Vue template usage (<base-button />) are call edges from the containing component. A component with callers is a shared contract — treat a change to it as a change to every caller, and say how many there are.

Zero callers means one of three things, and they are not the same: the component is new, it is dead, or it is reached in a way the graph cannot see. Check the invisible paths before concluding it is dead — route tables, lazy import(), story and test files, and Vue components auto-imported by build tooling never produce an edge.

What is the contract?