component-pipeline

Orchestrates a new component from Figma build through token sync to code and stories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a single new design system component end to end requires coordinating Figma component construction, token synchronization, and code/story generation across multiple skills, which is error-prone when done ad hoc. This Skill sequences that entire flow with human confirmation gates between stages so nothing half-built moves forward. ## Core Features & Use Cases - Three-stage orchestration: Invokes component-builder to construct the Figma component, token-sync-layer to sync any new tokens as a reviewable PR, and storybook-chromatic-builder to produce the code component and its stories. - Human confirmation gates: Pauses for explicit approval between every stage, so a failure at any point leaves a clean, resumable state. - Resumability: Each completed stage (Figma component, token PR, code/stories) stands on its own, letting users stop and resume later via the manifest. - Use Case: A designer wants to add a Tooltip to an existing design system. This Skill builds it in Figma, syncs its new tokens to code, then generates the code component and Storybook stories, checking in with the user at each step. ## Quick Start Ask the agent to run the new-component pipeline to take a Tooltip from Figma all the way to tested code and stories.

Frequently Asked Questions about component-pipeline

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

FAQPage Schema
How do I ship a new design system component from Figma to code?

Run the component pipeline, which builds the component in Figma with component-builder, syncs any new tokens via token-sync-layer, then generates the code component and stories with storybook-chromatic-builder. You confirm each stage before the next begins.

What happens if the component pipeline fails partway through?

Each stage is gated and invokes a real skill, so a failure leaves a clean resume point: the Figma component exists after stage 1, the token PR after stage 2, and the code and stories after stage 3. You can stop and pick up later using the manifest.

When should I use the pipeline instead of the individual skills?

Use the pipeline for one new component end to end on a system that already has foundations: tokens, a repo, sync, and Storybook. For initial setup or when many foundations are missing, run the individual setup skills directly instead.

Does the pipeline require an existing design system setup?

Yes. It assumes tokens are built, a repo exists at least at local-git level, sync is configured, and Storybook is initialized. If pieces are missing, it offers to run the relevant setup skill first.

Does the pipeline build components itself or call other skills?

It contains no domain logic of its own and only sequences the real skills: component-builder, token-sync-layer, and storybook-chromatic-builder. This keeps it from drifting out of date as those skills improve.