design-review

Structured UI design review — existing code (React/JSX, CSS, Tailwind) and, when behaviour matters, the running app in a real browser — reported as a prioritised Before / After / Why table. Covers visual hierarchy, spacing, typography, colour & contrast, component states, motion, responsiveness, accessibility, multi-page flow & navigation, and interaction continuity — grounded in Refactoring UI and Emil Kowalski's principles. For animation/jank/FPS, focus order, and cross-page UX it can drive Chrome via chrome-devtools-mcp to capture what a screenshot can't. Trigger when the user asks to "review this UI", "design review", "critique this component/screen/page or multi-page flow", asks why something "looks off", "looks AI-generated", or "looks like a wireframe", or wants to raise visual polish. For building UI from scratch use web-taste; for the full animation set see emilkowal-animations.

Jump to install

Repository: pproenca/dot-skills
Last source activity: July 5, 2026 at 07:23
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 design-review

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

47 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

Design Review

Conduct a design review of UI code and return a prioritised critique. The reviewer's lens is Emil Kowalski's design-engineering philosophy — taste is the differentiator; the unseen details compound; show the eye where to look — made concrete with the heuristics from Refactoring UI, WCAG, and MDN.

This is a read-only review skill: it diagnoses and proposes fixes; it does not rewrite the codebase. Each finding names the wrong default the code fell into, the exact fix, and why it matters.

When to Apply

The user asks to "review this UI", run a "design review", or "critique" a component, screen, or page.

The user says the output "looks off", "looks AI-generated", "looks like a wireframe", or "feels generic", and wants to know why.

A PR touches CSS/JSX/Tailwind and the user wants design feedback before merge.

The user wants to raise the visual polish or accessibility of an existing interface.

Not for building UI from scratch (use web-taste) or for the exhaustive animation rule set (use emilkowal-animations).

How to Run the Review

Design Review

This is a read-only review skill: it diagnoses and proposes fixes; it does not rewrite the codebase. Each finding names the wrong default the code fell into, the exact fix, and why it matters.

When to Apply

The user asks to "review this UI", run a "design review", or "critique" a component, screen, or page.

The user says the output "looks off", "looks AI-generated", "looks like a wireframe", or "feels generic", and wants to know why.

A PR touches CSS/JSX/Tailwind and the user wants design feedback before merge.

The user wants to raise the visual polish or accessibility of an existing interface.

Not for building UI from scratch (use web-taste) or for the exhaustive animation rule set (use emilkowal-animations).

How to Run the Review

Severity	Before	After	Why
High	`transition: all 300ms ease-in`	`transition: opacity 180ms cubic-bezier(0.23, 1, 0.32, 1)`	`ease-in` feels sluggish on entry; name the property and use a strong ease-out curve
High	every button `bg-indigo-600`	one filled primary; others ghost/outline	Equal-weight buttons compete; one primary makes the next step obvious
Medium	`color: #000` on `#fff`	`color: hsl(222 47% 11%)`	Pure black is harsher than ink and reads as stark
Critical	`<div onClick={remove}>`	`<button type="button" onClick={remove}>`	A div is unreachable by keyboard and invisible to screen readers

Severity	Meaning
Critical	Breaks usability or accessibility — fails contrast, no keyboard access, unreadable text
High	Clearly damages the design — no hierarchy, cramped spacing, competing primary actions
Medium	Noticeable polish gap — default easing, uniform line-height, missing press feedback
Low	Minor refinement — a value slightly off the scale

#	Category	Prefix	Covers
1	Visual Hierarchy	`hier-`	Focal point, emphasis technique, one primary action, value-over-label, space over borders
2	Spacing & Layout	`space-`	Spacing scale, generous whitespace, proximity grouping, constrained width
3	Typography	`type-`	Type scale, line length, line-height, alignment, readable body text
4	Colour & Contrast	`color-`	Near-black text, WCAG contrast, HSL ramps, restrained accents, colour-plus-cue
5	Component States & Feedback	`state-`	Press feedback, focus-visible, the full state matrix, empty states
6	Motion & Animation	`motion-`	Purpose/frequency, ease-out curves, sub-300ms, enter origin/scale, transform-only
7	Responsiveness & Touch	`resp-`	Fluid mobile-first, 44px targets, gating hover
8	Accessibility & Semantics	`access-`	Semantic elements, accessible names, reduced-motion
9	Flow & Navigation	`flow-`	App-shell consistency, view-state persistence, entry-point integrity, wayfinding
10	Interaction Continuity	`interact-`	Bridging route transitions, async feedback, focus on navigation

File	Description
references/_runtime-capture.md	Browser-driven capture playbook (chrome-devtools-mcp via mcporter)
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and source references

design-review

Install options

Review the source files

Design Review

When to Apply

How to Run the Review

Design Review

When to Apply

How to Run the Review

Output Format (Required)

Rule Categories

Quick Reference

1. Visual Hierarchy (`hier-`)

2. Spacing & Layout (`space-`)

3. Typography (`type-`)

4. Colour & Contrast (`color-`)

5. Component States & Feedback (`state-`)

6. Motion & Animation (`motion-`)

7. Responsiveness & Touch (`resp-`)

8. Accessibility & Semantics (`access-`)

9. Flow & Navigation (`flow-`)

10. Interaction Continuity (`interact-`)

How to Use

Related Skills

Reference Files

design-review

Source facts

Install options

Review the source files

More from this repository

Design Review

When to Apply

How to Run the Review

Design Review

When to Apply

How to Run the Review

Output Format (Required)

Rule Categories

Quick Reference

1. Visual Hierarchy (hier-)

2. Spacing & Layout (space-)

3. Typography (type-)

4. Colour & Contrast (color-)

5. Component States & Feedback (state-)

6. Motion & Animation (motion-)

7. Responsiveness & Touch (resp-)

8. Accessibility & Semantics (access-)

9. Flow & Navigation (flow-)

10. Interaction Continuity (interact-)

How to Use

Related Skills

Reference Files

More from this repository

1. Visual Hierarchy (`hier-`)

2. Spacing & Layout (`space-`)

3. Typography (`type-`)

4. Colour & Contrast (`color-`)

5. Component States & Feedback (`state-`)

6. Motion & Animation (`motion-`)

7. Responsiveness & Touch (`resp-`)

8. Accessibility & Semantics (`access-`)

9. Flow & Navigation (`flow-`)

10. Interaction Continuity (`interact-`)