Menu
Keep JavaScript/TypeScript dependencies fresh with safety rails and monorepo support.
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.
Based on SOC occupation classification
Migrate a React Native project from NativeWind to Uniwind. Use when the user wants to replace NativeWind with Uniwind, upgrade from NativeWind, switch to Uniwind, or mentions NativeWind-to-Uniwind migration. Handles package removal, config migration, Tailwind 4 upgrade, cssInterop removal, theme conversion, and all breaking changes.
Uniwind โ Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent-* color props, platform/data/state/responsive variants, CSS variables, custom utilities, withUniwind for third-party components, cn/tailwind-merge, tailwind-variants, safe area utilities, gradients, fonts, React Navigation, UI kits, diagnostics, troubleshooting, and Uniwind Pro features. Does not cover NativeWind migration.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Use Tailwind CSS to style React Native components across web and native
Build and maintain React Native apps with Expo SDK, EAS Build, EAS Update, and Continuous Native Generation. Use when configuring Expo projects, adding native modules, building binaries, or shipping over-the-air updates.
End-to-end testing patterns with Playwright for full-stack Python/React applications. Use when writing E2E tests for complete user workflows (login, CRUD, navigation), critical path regression tests, or cross-browser validation. Covers test structure, page object model, selector strategy (data-testid > role > label), wait strategies, auth state reuse, test data management, and CI integration. Does NOT cover unit tests or component tests (use pytest-patterns or react-testing-patterns).
| name | taze |
| description | Keep JavaScript/TypeScript dependencies fresh with safety rails and monorepo support. |
| metadata | {"author":"hairy","version":"2026.02.24","source":"Generated from https://github.com/antfu-collective/taze, scripts located at https://github.com/hairyf/skills"} |
The skill is based on
taze(latest README on GitHub) as of 2026-02-24.
taze is a lightweight CLI for upgrading dependencies in JavaScript/TypeScript projects and monorepos. It focuses on safe-by-default version bumps, powerful filtering, and configuration via flags or taze.config.(js|ts) so agents can orchestrate dependency maintenance workflows.
This skill is written for agents that:
taze| Topic | Description | Reference |
|---|---|---|
| Overview & CLI modes | taze goals, install-free usage, major/minor/patch modes | core-overview |
| Monorepo support | -r recursive mode, workspaces, local packages | core-monorepo |
| Topic | Description | Reference |
|---|---|---|
| Config file usage | taze.config.js/ts, defineConfig, options mapping | features-config-file |
| Filters & peer deps | --include/--exclude, locked deps, --peer, dep fields | features-filters-and-peer-deps |
| Topic | Description | Reference |
|---|---|---|
| Safe upgrade workflow | When to upgrade, required checks (tests, e2e, lint, typecheck), major-default policy with fallback | best-practices-upgrade-strategy |