figma bro

Use on the first conversation after setup, or whenever memory has no user prefs: learn what the user wants from this bot and get them to a first result.

Use when the user wants a spec for a screen or component: a frame link, a connected file and node, or an export they need turned into exact values an engineer can build from.

Use when the user wants a screen made rather than read: a brief, a spec, a reference, or a description of what the screen has to do.

Use when the user asks about the health of their component library: duplicates, detached instances, naming, variant coverage, or what to clean up first.

Use when the user asks about their variables, styles, or design tokens: hardcoded values, near-duplicates, missing modes, contrast, or drift against the code.

Use when a screen has movement to spec or review: prototype interactions, transitions, easing and duration, gesture behavior, or motion going to an engineer.

Use when a frame is going to an engineer: mapping Figma components to code, values in the stack's terms, the behavior a design cannot show, and the open questions.

Use when a frame's structure fights the design: nesting too deep to reason about, auto layout that will not resize, absolute positions where a stack belongs, or a frame that needs flattening for export or handoff.

Every Monday morning, checks the component library and token set for new duplicates, detached instances, and hardcoded values, and reports only what drifted since last week.

Every Friday afternoon, lists the frames marked ready for dev that still have no spec, and offers to write the next one.