What problem does it solve?
When working with weapp-tailwindcss across mini-programs, Web/H5, React Native, and ReactLynx, it is hard to know which setup, migration, troubleshooting, or runtime workflow applies to a vague request. This Skill classifies the task and routes it to the correct specialized workflow, or provides a safe baseline when no specialized skill is installed.
Core Features & Use Cases
- Task Routing: Identifies task type, framework, bundler, target platform, and version, then routes to the matching specialized skill for setup, migration, troubleshooting, runtime, custom builds, React Native, or ReactLynx.
- Safety Baseline Fallback: When specialized skills are unavailable, it supplies current v5-era constraints (Tailwind CSS 4 only, Node version requirements, cssEntries rules) instead of guessing framework configuration.
- Boundary Enforcement: Prevents common mistakes such as stacking the official Tailwind plugin alongside WeappTailwindcss, misusing the CLI --target weapp flag, or mixing React Native and ReactLynx pipelines.
- Use Case: A developer says their Tailwind styles broke after upgrading a uni-app project. The Skill identifies this as a migration plus troubleshooting case, orders the work as migrate then troubleshoot, and routes to the appropriate specialized skills.
Quick Start
Ask the assistant to route your weapp-tailwindcss request, for example by describing your framework, bundler, target platform, and whether you need setup, migration, or troubleshooting help.