chrome-extension-ui

Chrome Extensions UX/UI design and implementation guidelines for popups, side panels, content scripts, and options pages. Triggers on tasks involving browser extension UI, manifest v3, chrome APIs.

Ir a la instalación

Repositorio: pproenca/dot-skills
Última actividad en el origen: 27 de mayo de 2026 a las 09:50
Idioma detectado de SKILL.md: inglés
Estrellas: 194
Forks: 17

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/pproenca/dot-skills --skill chrome-extension-ui

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

47 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Ver todos los de este repositorio

name	chrome-extension-ui
description	Chrome Extensions UX/UI design and implementation guidelines for popups, side panels, content scripts, and options pages. Triggers on tasks involving browser extension UI, manifest v3, chrome APIs.

Chrome Extensions UX/UI Best Practices

Comprehensive UX/UI design guide for Chrome Extensions, optimized for Manifest V3. Contains 42 rules across 8 categories, prioritized by impact to guide extension UI development and code review.

When to Apply

Reference these guidelines when:

Building new Chrome extension user interfaces
Choosing between popup, side panel, or content script UI
Implementing accessible, keyboard-navigable interfaces
Designing loading states, error handling, and feedback patterns
Creating options pages and settings persistence

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Component Selection	CRITICAL	`comp-`
2	Accessibility & Navigation	CRITICAL	`access-`
3	Popup Design	HIGH	`popup-`
4	Side Panel UX	HIGH	`panel-`
5	Content Script UI	MEDIUM-HIGH	`inject-`
6	Visual Feedback	MEDIUM	`feedback-`
7	Options & Settings	MEDIUM	`options-`
8	Icons & Branding	LOW-MEDIUM	`brand-`

Quick Reference

1. Component Selection (CRITICAL)

comp-popup-vs-sidepanel - Choose Side Panel for Persistent Tasks
comp-content-script-ui - Use Content Scripts for In-Page UI
comp-single-purpose - Design for Single Purpose
comp-minimal-permissions - Request Minimal Permissions
comp-action-tooltip - Provide Descriptive Action Tooltips

2. Accessibility & Navigation (CRITICAL)

access-keyboard-navigation - Enable Complete Keyboard Navigation
access-focus-visible - Maintain Visible Focus Indicators
access-aria-labels - Use ARIA Labels for Icon-Only Buttons
access-color-contrast - Ensure Sufficient Color Contrast
access-focus-trap - Avoid Keyboard Focus Traps
access-semantic-html - Use Semantic HTML Elements

3. Popup Design (HIGH)

popup-size-constraints - Design Within Popup Size Limits
popup-instant-render - Render Popup Content Instantly
popup-primary-action - Make the Primary Action Obvious
popup-auto-close - Handle Popup Auto-Close Gracefully
popup-external-js - Keep JavaScript in External Files
popup-dynamic-switch - Use Dynamic Popups for State-Based UI

4. Side Panel UX (HIGH)

panel-non-distracting - Design Non-Distracting Side Panels
panel-tab-vs-window - Choose Tab-Specific vs Window-Wide Panels
panel-responsive-width - Design for Variable Panel Widths
panel-page-context - Sync Panel Content with Page Context
panel-lazy-sections - Lazy Load Panel Sections

5. Content Script UI (MEDIUM-HIGH)

inject-shadow-dom - Use Shadow DOM for Style Isolation
inject-z-index - Use Maximum Z-Index for Overlays
inject-document-ready - Inject UI After DOM Ready
inject-unique-ids - Use Unique IDs to Prevent Conflicts
inject-cleanup - Clean Up Injected Elements on Removal

6. Visual Feedback (MEDIUM)

feedback-loading-states - Show Loading States for Async Operations
feedback-error-messages - Write Actionable Error Messages
feedback-badge-status - Use Badge for At-a-Glance Status
feedback-success-confirmation - Confirm Successful Actions
feedback-notifications - Use Notifications Sparingly
feedback-progress-indication - Show Progress for Long Operations

7. Options & Settings (MEDIUM)

options-embedded-page - Use Embedded Options for Simple Settings
options-sync-storage - Sync Settings Across Devices
options-auto-save - Auto-Save Settings on Change
options-sensible-defaults - Provide Sensible Default Settings

8. Icons & Branding (LOW-MEDIUM)

brand-icon-sizes - Provide All Required Icon Sizes
brand-distinctive-icon - Design a Distinctive Toolbar Icon
brand-badge-text - Keep Badge Text Under 4 Characters
brand-consistent-styling - Maintain Consistent Visual Style
brand-web-store-assets - Create Quality Web Store Assets

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
references/_sections.md	Category definitions and ordering
assets/templates/_template.md	Template for new rules
metadata.json	Version and reference information

chrome-extension-ui

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Chrome Extensions UX/UI Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Component Selection (CRITICAL)

2. Accessibility & Navigation (CRITICAL)

3. Popup Design (HIGH)

4. Side Panel UX (HIGH)

5. Content Script UI (MEDIUM-HIGH)

6. Visual Feedback (MEDIUM)

7. Options & Settings (MEDIUM)

8. Icons & Branding (LOW-MEDIUM)

How to Use

Reference Files

Chrome Extensions UX/UI Best Practices

When to Apply

Rule Categories by Priority

Quick Reference

1. Component Selection (CRITICAL)

2. Accessibility & Navigation (CRITICAL)

3. Popup Design (HIGH)

4. Side Panel UX (HIGH)

5. Content Script UI (MEDIUM-HIGH)

6. Visual Feedback (MEDIUM)

7. Options & Settings (MEDIUM)

8. Icons & Branding (LOW-MEDIUM)

How to Use

Reference Files