tailwind-refactor

Tailwind CSS code refactoring patterns for v4 migration and anti-pattern cleanup. This skill should be used when refactoring Tailwind utility classes, migrating from v3 to v4, cleaning up deprecated utilities, consolidating verbose class patterns, or removing code smells — all without changing the visual output. Triggers on tasks involving Tailwind CSS cleanup, v4 migration, class refactoring, @apply removal, or utility modernization.

الانتقال إلى التثبيت

المستودع: pproenca/dot-skills
آخر نشاط في المصدر: ٢٧ مايو ٢٠٢٦ في ٠٩:٥٠
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ١٩٤
التفرعات: ١٧

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

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

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات

54 ملفات

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

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

عرض الكل من هذا المستودع

name

tailwind-refactor

description

Community Tailwind CSS Refactoring Best Practices

Comprehensive code quality refactoring guide for Tailwind CSS applications targeting v4. Contains 50 rules across 8 categories, prioritized by migration urgency. Every transformation preserves the existing look and feel — this skill is purely about cleaner code, modern syntax, and v4 compatibility.

Companion skills: Use tailwind-ui-refactor for visual design improvements and tailwind-responsive-ui for responsive layout patterns.

When to Apply

Before manual migration: Run npx @tailwindcss/upgrade first — it handles most configuration and renamed utility changes automatically. Then use this skill for patterns the automated tool does not cover.

Reference these guidelines when:

Migrating a project from Tailwind CSS v3 to v4
Cleaning up deprecated or renamed utility classes
Consolidating verbose multi-class patterns
Replacing arbitrary values with design tokens
Removing @apply overuse in CSS files
Modernizing syntax to v4 conventions

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Configuration Migration

File	Description
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

tailwind-refactor

خيارات التثبيت

مراجعة ملفات المصدر

Community Tailwind CSS Refactoring Best Practices

When to Apply

Rule Categories by Priority

Community Tailwind CSS Refactoring Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Configuration Migration (CRITICAL)

2. Deprecated Utility Replacement (CRITICAL)

3. Renamed Utility Updates (HIGH)

4. Class Consolidation (HIGH)

5. Arbitrary Value Cleanup (MEDIUM-HIGH)

6. Syntax Modernization (MEDIUM)

7. @apply & Architecture Cleanup (MEDIUM)

8. Modern Feature Adoption (LOW-MEDIUM)

How to Use

Reference Files

tailwind-refactor

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

المزيد من هذا المستودع

المزيد من هذا المستودع

Community Tailwind CSS Refactoring Best Practices

When to Apply

Rule Categories by Priority

Community Tailwind CSS Refactoring Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Configuration Migration (CRITICAL)

2. Deprecated Utility Replacement (CRITICAL)

3. Renamed Utility Updates (HIGH)

4. Class Consolidation (HIGH)

5. Arbitrary Value Cleanup (MEDIUM-HIGH)

6. Syntax Modernization (MEDIUM)

7. @apply & Architecture Cleanup (MEDIUM)

8. Modern Feature Adoption (LOW-MEDIUM)

How to Use

Reference Files