@springernature/breeze-ui-bt

Breeze UI 3

Project Overview

Breeze UI 3 is a React UI library written in TypeScript, designed for non-Mendix applications. It’s built on top of Radix primitives and themes, and provides a consistent set of reusable components with well-typed APIs.

The goal of the library is simple: help teams build interfaces faster while keeping a unified look, behavior, and developer experience across projects.

It includes all the common building blocks you’d expect — buttons, inputs, modals, dropdowns, tabs, navigation, typography, notifications, and layout utilities. Components are designed to be composable, accessible, and easy to integrate, while keeping complexity and implementation details inside the design system.

By centralizing UI logic, Breeze UI 3 helps reduce duplication, improves maintainability, and ensures consistency across different products.

The library is developed and documented using Storybook, making it easy to explore and test components in isolation. Under the hood, it uses a modern Vite + TypeScript setup for fast development and reliable builds.

Demo: https://breeze-ui-bt.apps.private.k8s.springernature.io/

Copilot Guidelines

Please follow the existing conventions of this repository and keep all changes aligned with the current codebase.

General Rules

• Follow existing architecture, file structure, naming, and component patterns.
• Prefer simple, clear, and maintainable solutions.
• Reuse existing components and utilities instead of duplicating logic.
• Avoid unnecessary abstractions and over-engineering.
• Do not add new dependencies unless explicitly requested.
• Avoid using any; prefer proper TypeScript types and generics.
• Keep exported APIs clearly typed.
• Do not refactor or modify unrelated code.
• Do not change public APIs unless the task explicitly requires it.
• Make minimal, focused changes that solve only the requested problem.

Git Rules

• Do not create commits.
• Do not write commit messages.
• Do not push changes.
• Do not manage branches.

Expected Behavior

• Stay consistent with the existing implementation style.
• Prefer the simplest solution that fits the current project.
• If something is unclear, do not invent missing requirements.