bklit-ship

What problem does it solve?

bklit-ui monorepo contributors often lack a standardized, end-to-end process for moving a chart or component validated in Studio to production, leading to missing exports, incomplete documentation, or unregistered components that cannot be used by end users.

Core Features & Use Cases

• End-to-end shipping checklist: Guides contributors through every required step to move a Studio-validated chart or component to production, from exporting the code to opening a PR.
• Cross-package coordination: Covers updates to the UI package, documentation sites, Studio prototyping tool, and shadcn registry to ensure consistency across the monorepo.
• Validation guardrails: Includes pre-merge checks for linting, formatting, testing, and building to catch errors before code is merged. Use case: A contributor has a new candlestick chart variant validated in Studio, and uses this skill to ensure the component is exported, documented, added to the chart gallery, wired into Studio, registered in the shadcn registry, and passes all CI checks before opening a PR.

Quick Start

Use the bklit-ship skill to ship your validated Studio chart or component prototype to production in the bklit-ui monorepo following the full end-to-end checklist.