skills.rest
TechsioCZ
TechsioCZOFFICIAL
Explore all skills by this author →
GitHub

ui-kit-publish-readiness

Validate UI kit exports, tokens, Storybook, and semantic-release constraints.

2|Updated Dec 2, 2024
Search Tags:#validation#release#storybook#ci-cd#exports#ui-kit#token-entrypoints
One-click install
npx skills add https://github.com/TechsioCZ/new-engine --skill ui-kit-publish-readiness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-kit-publish-readiness
Source: https://github.com/TechsioCZ/new-engine/tree/main/libs/ui/skills/ui-kit-publish-readiness
Command: npx skills add https://github.com/TechsioCZ/new-engine --skill ui-kit-publish-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that a UI kit release meets quality gates before publication by validating exports, token entrypoints, and CI constraints.

Core Features & Use Cases

  • Export validation: verifies package exports are properly subpath-based and consumable.
  • Token entrypoint validation: ensures token CSS/entrypoints are public and accessible to consumers.
  • CI & release gating: checks semantic-release configuration and CI integration to prevent faulty releases.
  • Build & accessibility checks: validates Storybook build status and accessibility verifications.
  • Documentation & assets verification: confirms presence of necessary screenshots and docs.

Quick Start

Run the ui-kit-publish-readiness check before releasing to verify exports, tokens, and CI constraints.

Frequently Asked Questions about ui-kit-publish-readiness

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

FAQPage Schema
How do I validate UI-kit exports and token entrypoints before a release?▼

To validate UI-kit release readiness, run checks that verify subpath exports, public token entrypoints, Storybook build status, and semantic-release CI constraints. This enforces deterministic pass/fail criteria across packaging workflows to prevent faulty publications.

What is UI-kit release readiness validation in CI-CD pipelines?▼

UI-kit release readiness validation in CI-CD pipelines is a pre-release gating mechanism that checks semantic-release configuration, subpath exports, and Storybook builds. It prevents faulty releases by enforcing deterministic validation scripts with clear pass/fail criteria.

How do I gate semantic-release publications using Storybook build status?▼

Gate semantic-release publications by running readiness validation scripts that check Storybook build status and accessibility verifications alongside export checks. This integration prevents faulty UI-kit releases in CI pipelines by enforcing strict pass/fail criteria.

Does semantic-release work with subpath export validation for UI-kits?▼

Semantic-release works with subpath export validation by using pre-release pipeline checks to verify exports and tokens before publication. This ensures the semantic-release process only triggers when CI gating confirms proper subpath exports and public token entrypoints.

Why does my UI-kit release fail CI gating when Storybook builds pass?▼

Your UI-kit release might fail CI gating despite passing Storybook builds because semantic-release constraints, subpath exports, or public token entrypoints are invalid. Release readiness validation enforces all these checks simultaneously with strict pass/fail criteria.

Related Skills

Explore More Software Engineering Skills→
cyanheadscyanheads
148

add-export

Add a public subpath export to the MCP-ts-core package.

Community
Intermediate
SimplexLabSimplexLab
392

prepare-release

Verify changelog, README, and version in pyproject.toml for TorchJD releases.

Official
Advanced
gihwan-devgihwan-dev
1

component-screenshot

Capture Storybook story screenshots as PNG assets by story-id.

Community
Intermediate
AshleyHollisAshleyHollis

ci-validation-gates

Enforces semantic versioning and validates npm tokens in CI/CD pipelines.

Community
Advanced