component-builder

Builds Figma component libraries with variant matrices, token bindings, and typed slots.

77|11|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/jrpease/throughline --skill component-builder-jrpease
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-builder
Source: https://github.com/jrpease/throughline/tree/main/skills/component-builder
Command: npx skills add https://github.com/jrpease/throughline --skill component-builder-jrpease

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Building a foundational UI component set in Figma by hand is slow and error-prone: variant matrices get inconsistent, states get dropped, and components end up hardcoding values instead of consuming the design system's tokens. This Skill automates the construction of well-structured Figma components that map cleanly to code. ## Core Features & Use Cases - Variant matrix construction: Builds components (buttons, inputs, cards, badges, modals, and more) as auto-layout grids with types, sizes, and the full state set (default, hover, focus, active, disabled, plus loading/selected/error where applicable). - Token and style binding: Binds every fill, radius, border, spacing, text, and shadow property to the system's semantic tokens and styles so components consume the design system rather than hardcode values. - Slot contracts and documentation: Captures icon, typed-component, and content slot contracts for code handoff, and authors a canonical documentation record projected to the Figma component description and a doc card. - Use Case: After tokens and icons exist, ask the agent to build the foundational component library; it brainstorms the set with you, builds atoms before composites, and checkpoints each component for review. ## Quick Start Ask the agent to build the foundational Figma component set for your design system, starting with buttons and inputs bound to your existing tokens.

Frequently Asked Questions about component-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Figma component library with variants and states?

Run this Skill after your tokens exist; it brainstorms the component set and variant matrices with you, then builds each component as an auto-layout grid where variants are rows and states are columns. Every component includes the full relevant state set and is bound to your semantic tokens.

What prerequisites does Figma component building need?

It requires semantic tokens to be built first and a live Figma connection. An icon set is strongly recommended beforehand since most components take icon slots, but you can override and build icon-less components if you prefer.

Does it support shadcn, MUI, and other UI frameworks?

Yes. It reads the target UI framework from the project manifest and aligns variant vocabulary, naming, and the focus-state idiom to that framework, such as the shadcn ring style versus MUI per-component focus handling.

Why can't I add a typed instance-swap dropdown in Figma?

Typed instance-swap dropdowns require the swap targets to be published in a Figma library. If the library is not published, the Skill builds a toggle plus manual-swap slot instead and queues the component for an upgrade pass after you publish.

When should I not use this Skill for component work?

Avoid it for retrofitting or migrating an existing codebase, such as converting a hand-rolled component layer to shadcn. That scope exceeds a single skill and should go through the scaling-up planning handoff instead.