Proposal: Add Uniwind setup skill for Expo projects #19
Description
Proposal: Add Uniwind setup skill for Expo projects
Summary
I’d like to propose adding a new skill to the expo/skills repository that documents how to set up Uniwind in Expo projects.
Uniwind is a utility-first styling solution for React Native that provides a Tailwind-like developer experience and works well with Expo. While the repo already includes guidance for Tailwind + NativeWind, there is currently no equivalent reference for Uniwind.
Why Uniwind is important
Uniwind is increasingly being adopted in React Native and Expo projects because it:
- Provides a familiar utility-first API similar to Tailwind
- Works at runtime without requiring a build-time CSS pipeline
- Reduces configuration complexity in some setups
- Is well-suited for Expo’s managed workflow
- Has clear and actively maintained official documentation
Having Uniwind documented as a skill would help AI agents and developers choose and correctly configure an alternative styling approach when NativeWind is not preferred.
High-level comparison (context only)
This proposal is not about replacing existing skills, but about offering additional, well-documented options:
- NativeWind: Tailwind-based, widely used, relies on build-time processing
- Uniwind: Utility-first, runtime-based, simpler setup for some Expo workflows
Both approaches are valid, and having skills for each improves coverage and accuracy.
Scope of the proposed skill
The skill would focus on Expo-specific setup, including:
- Installing Uniwind in an Expo project
- Required Babel and Metro configuration (Expo-compatible)
- App entry configuration
- Minimal usage example
- Common Expo-specific pitfalls and notes
All information would be derived directly from the official Uniwind documentation:
https://docs.uniwind.dev/
Contribution
If this proposal makes sense to the maintainers, I’d be happy to contribute by:
- Drafting the skill markdown file
- Ensuring it follows the existing
expo/skillsformat - Keeping the content factual, procedural, and aligned with official docs
Thanks for considering this addition!