bingo-import-from-project

Import design tokens, CSS, and components from a local React project into a Bingo canvas.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/Carlosfengv/bingo --skill bingo-import-from-project-carlosfengv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bingo-import-from-project
Source: https://github.com/Carlosfengv/bingo/tree/main/packages/compiler/skills/bingo-import-from-project
Command: npx skills add https://github.com/Carlosfengv/bingo --skill bingo-import-from-project-carlosfengv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving an existing project's real design system into a visual editor is slow and error-prone: tokens get retyped, Tailwind configs get rewritten, and components get replaced with lookalike markup. This Skill imports the source project's actual design tokens, CSS entry chain, Tailwind configuration, assets, and components into Bingo while progressively drawing a live design-system reference page that proves the import compiles. ## Core Features & Use Cases - Foundation-first import: Copies the package manifest, CSS entry and import chain, and Tailwind v3 or v4 configuration exactly as authored, then renders token swatches using the source's own utility classes rather than inline values. - Batched component ingestion: Reads, adapts, and writes source components in batches of 6-10, preserving names, exports, props, path aliases, and variants, with a ledger tracking import, adapt, or skip decisions. - Live verification page: Builds a Design System canvas page section by section, takes screenshots to verify rendering, and recreates one representative source page for fidelity comparison. - Use Case: Point the assistant at your local React codebase and ask it to import the design system; it lands the Tailwind foundation, draws color and typography scales, imports components in batches, and finishes with a verified reference page and coverage summary. ## Quick Start Ask the assistant to import the design system from your current local project into Bingo and build the Design System reference page.

Frequently Asked Questions about bingo-import-from-project

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

FAQPage Schema
How do I import a design system from a local React project into Bingo?

Ask the assistant to import the design system from your current project or an explicitly named accessible folder. It scans the project, copies the CSS entry and Tailwind config, then imports components in batches while drawing a Design System reference page.

Does the import support Tailwind v3 and v4 projects?

Both versions are supported. Tailwind v4 sources keep their @theme and @import rules, while v3 sources keep their @tailwind directives and config file, which Bingo compiles through the v4 compatibility bridge.

What happens to components that cannot run in Bingo?

Components with router, server-only, or unmockable dependencies are skipped with a recorded reason in the import ledger. Adaptable components are minimally modified with a file comment, and their public props and exports are preserved.

How do I resume an interrupted design system import?

Simply ask to continue the import. The assistant inspects existing destination files and the canvas, reuses the active Design System page, skips correctly imported files, and resumes at the first incomplete batch.

Why do imported token swatches use utility classes instead of inline styles?

The reference page is a functional test of the imported design system, so each sample must exercise the source's real utility class such as bg-accent-500 or shadow-lg. Inline values would hide compilation problems in the imported foundation.