Add Tailwind 4 plugin for automatic MCU color variable mapping

[Copilot]

Users previously had to manually copy 180+ lines of @theme CSS variable mappings and manually add custom color definitions. This plugin automates both.

Changes

Plugin implementation (src/tailwind-plugin.js)

• Maps all --mcu-* CSS variables to Tailwind theme colors (background, surface, primary, secondary, tertiary, error, neutral variants)
• Generates shade mappings (50-950) for all color palettes
• Accepts customColors array parameter for dynamic custom color registration
• Converts camelCase color names to kebab-case for CSS variable compatibility

Package configuration

• Exported plugin at react-mcu/tailwind-plugin with TypeScript definitions
• Added post-build script to copy .d.ts files after tsup's DTS build phase

Documentation

• Added plugin usage examples to README with and without custom colors

Usage

Before:

@import "react-mcu/tailwind.css";
/* + manually add custom color mappings */

After:

@import "tailwindcss";
@plugin "react-mcu/tailwind-plugin" {
  customColors: ["myCustomColor1", "myCustomColor2"];
}

Enables: bg-primary, text-on-surface, bg-myCustomColor1-500, etc.

Original prompt

code un plugin tailwind 4 qui automatise les instructions du readme (section tailwind) pour qu'un utilisateur tw puisse directemwbt @plugin dans son css - gere la transmission de parametres (au besoin inspire toi des plugin officiels tailwind pour voir comment ils code t ca proprement

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.