uniwind

Uniwind best practices for React Native styling with Tailwind CSS. This skill should be used when writing, reviewing, or refactoring React Native code using Uniwind. Triggers on tasks involving Uniwind, className styling, Tailwind in React Native, NativeWind migration, or theming.

Jump to install

Repository: pproenca/dot-skills
Last source activity: May 27, 2026 at 09:50
Detected SKILL.md language: English
Stars: 194
Forks: 17

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/pproenca/dot-skills --skill uniwind

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

50 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

drizzle-nextjs-postgres

Drizzle ORM against PostgreSQL inside a Next.js App Router app. Covers client construction (globalThis singleton across HMR, serverless pool sizing, `prepare:false` behind PgBouncer/Supavisor, driver choice when you need interactive transactions, `server-only`), reads in Server Components under Next.js 16 Cache Components (`use cache` superseding `unstable_cache` and the `revalidate`/`dynamic` segment configs, Suspense boundaries, React `cache()` dedupe), Server Actions (authorization inside the action, `updateTag` vs `revalidateTag`, `after()`), Postgres schema types (timestamptz, identity vs serial, jsonb, numeric-as-string, bigint modes), drizzle-kit migrations (generate vs push, CONCURRENTLY outside the migrator, NOT VALID constraints, rename prompts), transactions and pooled connections, and Postgres query traps (keyset pagination, count cost, driver-dependent `db.execute()` shape, NOT IN nulls, prepared statements). Use when writing or reviewing Drizzle + Postgres code in Next.js.

2026-07-24

relational-data-modeling

Corrects the wrong defaults a model has when designing a relational schema — the DDL decisions an experienced engineer makes differently. Use when creating or reviewing tables, migrations, ER models, or ORM schema definitions. Covers identity and keys (surrogate vs natural, identity vs serial, uuidv7, composite keys that make cross-tenant references impossible), relationships (polymorphic foreign keys the database cannot enforce, referential actions, unindexed FK columns, disjoint subtypes), invariants the engine can prove instead of application code (EXCLUDE, partial unique indexes, CHECK limits, deferrable cycles, NOT VALID), types (timestamptz, exact money, range types, enum vs lookup table), derived and encoded data (generated columns, JSONB as an escape hatch), and time (events vs in-place updates, soft-delete flags that silently disable constraints, temporal keys). NOT for query tuning, index selection for read paths, or connection pooling.

2026-07-23

relational-database-design

Distills a logical relational-database design methodology into rules an agent applies while designing or reviewing a schema. Covers the design sequence (mission → tables → fields → keys → relationships → business rules → views → integrity review), one-subject-per-table decomposition, atomic single-valued fields, candidate/primary/foreign keys, relationship types with deletion rules and participation, the four levels of data integrity, database-vs-application business rules, validation tables, views for derived data, and the flat-file / spreadsheet / RDBMS-driven antipatterns to avoid. The structure is logical and RDBMS-agnostic, and normalized by construction. Use when designing a new relational schema, reviewing or refactoring an existing one, resolving redundant or repeating data, choosing keys, modeling relationships, or deciding where a constraint belongs.

2026-07-23

View all from this repository

name	uniwind
description	Uniwind best practices for React Native styling with Tailwind CSS. This skill should be used when writing, reviewing, or refactoring React Native code using Uniwind. Triggers on tasks involving Uniwind, className styling, Tailwind in React Native, NativeWind migration, or theming.

Uniwind Best Practices

Comprehensive performance optimization and best practices guide for Uniwind - the fastest Tailwind CSS bindings for React Native. Contains 45+ rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

When to Apply

Reference these guidelines when:

Setting up Uniwind in a new React Native project
Configuring Metro plugin and CSS entry points
Building theme systems with CSS variables
Integrating third-party components with className support
Creating responsive layouts for mobile and tablet
Optimizing styling performance
Migrating from NativeWind to Uniwind

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Build-Time Configuration	CRITICAL	`build-`
2	Theme Architecture	CRITICAL	`theme-`
3	Component Integration	HIGH	`comp-`
4	Responsive Design	HIGH	`resp-`
5	Performance Optimization	MEDIUM-HIGH	`perf-`
6	Platform Patterns	MEDIUM	`plat-`
7	State & Interaction	MEDIUM	`state-`
8	Migration & Compatibility	LOW-MEDIUM	`compat-`

Quick Reference

1. Build-Time Configuration (CRITICAL)

build-metro-config - Configure Metro Plugin with Required Options
build-css-entry - Place CSS Entry File in App Root Directory
build-typescript-types - Configure TypeScript Definition File Location
build-restart-metro - Restart Metro After Configuration Changes
build-debug-mode - Enable Debug Mode During Development
build-rem-polyfill - Configure rem Base Value for Design System Consistency

2. Theme Architecture (CRITICAL)

theme-css-variables - Define Theme Variables with @theme Directive
theme-variant-blocks - Use @variant Blocks for Theme Definitions
theme-consistent-variables - Define Identical Variables Across All Themes
theme-custom-registration - Register Custom Themes in Metro Config
theme-oklch-colors - Use OKLCH Color Space for Perceptual Uniformity
theme-light-dark-function - Use light-dark() Function for Adaptive Colors
theme-no-provider - Remove ThemeProvider Wrapper from App

3. Component Integration (HIGH)

comp-with-uniwind - Use withUniwind for Third-Party Components
comp-module-level - Define Wrapped Components at Module Level
comp-prop-mapping - Use Custom Prop Mappings for Non-Style Props
comp-accent-colors - Use accent-* Classes for Color Prop Extraction
comp-reanimated - Reanimated Components Work Without withUniwind
comp-custom-css - Use Custom CSS Classes for Complex Reusable Styles

4. Responsive Design (HIGH)

resp-mobile-first - Design Mobile-First with Progressive Enhancement
resp-limit-breakpoints - Limit Breakpoints to 3-5 for Maintainability
resp-visibility-toggle - Use hidden/flex for Responsive Visibility
resp-custom-breakpoints - Define Custom Breakpoints with Semantic Names
resp-responsive-spacing - Scale Spacing and Typography Responsively

5. Performance Optimization (MEDIUM-HIGH)

perf-static-classnames - Use Complete Static Class Names for Build-Time Resolution
perf-use-resolve-sparingly - Use useResolveClassNames Sparingly
perf-memoize-variants - Memoize Variant Style Objects
perf-tailwind-merge - Use tailwind-merge for Class Deduplication
perf-avoid-inline-styles - Prefer className Over Inline style Prop
perf-combine-styles - Combine className and style Prop Correctly

6. Platform Patterns (MEDIUM)

plat-ios-android-selectors - Use Platform Selectors for iOS/Android Differences
plat-safe-area-context - Use react-native-safe-area-context for Safe Areas
plat-yoga-layout - Understand Yoga Layout Engine Differences
plat-web-selector - Use web: Selector for Cross-Platform Apps
plat-font-families - Configure Font Families Without Fallbacks

7. State & Interaction (MEDIUM)

state-pressable-states - Use Pressable with active:/focus:/disabled: States
state-data-selectors - Use Data Selectors for Component State Styling
state-no-hover - Avoid hover: on Native - Use active: Instead
state-group-variants - Use Group Variants for Parent-Child Styling (WIP)
state-dark-mode - Use dark: Variant for Dark Mode Styles

8. Migration & Compatibility (LOW-MEDIUM)

compat-nativewind-migration - Follow NativeWind Migration Checklist
compat-tailwind-4-syntax - Use Tailwind 4 CSS-First Configuration
compat-rem-default - Account for Different rem Default Values
compat-cssinterop-replacement - Replace cssInterop with withUniwind
compat-safe-area-changes - Replace *-safe Classes with Safe Area Context

How to Use

Read individual reference files for detailed explanations and code examples:

Section definitions - Category structure and impact levels
Rule template - Template for adding new rules

Reference Files

File	Description
AGENTS.md	Complete compiled guide with all rules
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

uniwind

Source facts

Install options

Review the source files

More from this repository

More from this repository

Uniwind Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Build-Time Configuration (CRITICAL)

2. Theme Architecture (CRITICAL)

3. Component Integration (HIGH)

4. Responsive Design (HIGH)

5. Performance Optimization (MEDIUM-HIGH)

6. Platform Patterns (MEDIUM)

7. State & Interaction (MEDIUM)

8. Migration & Compatibility (LOW-MEDIUM)

How to Use

Reference Files

Uniwind Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Build-Time Configuration (CRITICAL)

2. Theme Architecture (CRITICAL)

3. Component Integration (HIGH)

4. Responsive Design (HIGH)

5. Performance Optimization (MEDIUM-HIGH)

6. Platform Patterns (MEDIUM)

7. State & Interaction (MEDIUM)

8. Migration & Compatibility (LOW-MEDIUM)

How to Use

Reference Files