ios-hig

Apple Human Interface Guidelines for iOS 26 / Swift 6.2 clinic-architecture apps. Covers navigation, interaction design, accessibility, feedback states, UX patterns, and visual design for SwiftUI implementations that follow App-target coordinators/route shells and Domain/Data boundaries. Use when designing or reviewing HIG-compliant experiences in the clinic modular MVVM-C stack.

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 ios-hig

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

38 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	ios-hig
description	Apple Human Interface Guidelines for iOS 26 / Swift 6.2 clinic-architecture apps. Covers navigation, interaction design, accessibility, feedback states, UX patterns, and visual design for SwiftUI implementations that follow App-target coordinators/route shells and Domain/Data boundaries. Use when designing or reviewing HIG-compliant experiences in the clinic modular MVVM-C stack.

Apple iOS HIG Best Practices

Comprehensive guide for Apple Human Interface Guidelines compliance in iOS apps built with SwiftUI. Contains 34 rules across 6 categories covering navigation, interaction design, accessibility, user feedback, UX patterns, and visual design.

Clinic Architecture Contract (iOS 26 / Swift 6.2)

All guidance in this skill assumes the clinic modular MVVM-C architecture:

Feature modules import Domain + DesignSystem only (never Data, never sibling features)
App target is the convergence point and owns DependencyContainer, concrete coordinators, and Route Shell wiring
Domain stays pure Swift and defines models plus repository, *Coordinating, ErrorRouting, and AppError contracts
Data owns SwiftData/network/sync/retry/background I/O and implements Domain protocols
Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes
ViewModels call repository protocols directly (no default use-case/interactor layer)

When to Apply

Reference these guidelines when:

Building navigation hierarchies with tab bars, NavigationStack, or split views
Designing touch interactions, gestures, and haptic feedback
Ensuring accessibility with VoiceOver, Dynamic Type, and color contrast
Implementing loading states, error handling, and empty states
Building onboarding flows, permission requests, and confirmation dialogs
Supporting dark mode, SF Symbols, and standard layout margins
Reviewing apps for HIG compliance

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Navigation	CRITICAL	`nav-`
2	Interaction Design	CRITICAL	`inter-`
3	Accessibility	CRITICAL	`acc-`
4	User Feedback	HIGH	`feed-`
5	UX Patterns	HIGH	`ux-`
6	Visual Design	HIGH	`vis-`

Quick Reference

1. Navigation (CRITICAL)

nav-tab-bar - Design tab bars for top-level navigation
nav-navigation-stack - Use NavigationStack for hierarchical navigation
nav-toolbar-placement - Place actions in toolbars using standard placements

2. Interaction Design (CRITICAL)

inter-touch-targets - Maintain 44pt minimum touch targets
inter-gesture-patterns - Use standard gesture patterns
inter-haptic-feedback - Add haptic feedback for meaningful events
inter-keyboard-handling - Handle keyboard appearance gracefully
inter-drag-drop - Support drag and drop for content transfer
inter-pull-to-refresh - Support pull to refresh for lists
inter-swipe-actions - Add swipe actions for contextual operations
inter-list-search - Use searchable for built-in search

3. Accessibility (CRITICAL)

acc-labels - Provide meaningful accessibility labels
acc-dynamic-type - Support Dynamic Type for all text
acc-color-contrast - Maintain sufficient color contrast
acc-reduce-motion - Respect reduce motion preference
acc-color-independent - Never rely on color alone
acc-focus-management - Manage focus for assistive technologies
acc-scaled-metric - Use ScaledMetric for adaptive sizing
acc-view-that-fits - Use ViewThatFits for adaptive layouts

4. User Feedback (HIGH)

feed-loading-states - Show appropriate loading indicators
feed-error-states - Handle errors with clear recovery actions
feed-notifications - Use notifications judiciously
feed-success-confirmation - Confirm successful actions appropriately
feed-empty-states - Design helpful empty states

5. UX Patterns (HIGH)

ux-onboarding - Design minimal onboarding
ux-permissions - Request permissions in context
ux-modality - Use modality appropriately
ux-confirmation-dialog - Use confirmation dialogs for destructive actions
ux-data-entry - Minimize data entry friction
ux-undo - Support undo for destructive actions
ux-settings - Organize settings logically

6. Visual Design (HIGH)

vis-dark-mode - Support dark mode with semantic colors
vis-sf-symbols - Use SF Symbols with correct rendering mode and weight
vis-layout-margins - Use standard layout margins and safe areas

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

ios-hig

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Apple iOS HIG Best Practices

Clinic Architecture Contract (iOS 26 / Swift 6.2)

When to Apply

Rule Categories by Priority

Quick Reference

1. Navigation (CRITICAL)

2. Interaction Design (CRITICAL)

3. Accessibility (CRITICAL)

4. User Feedback (HIGH)

5. UX Patterns (HIGH)

6. Visual Design (HIGH)

How to Use

Reference Files

Apple iOS HIG Best Practices

Clinic Architecture Contract (iOS 26 / Swift 6.2)

When to Apply

Rule Categories by Priority

Quick Reference

1. Navigation (CRITICAL)

2. Interaction Design (CRITICAL)

3. Accessibility (CRITICAL)

4. User Feedback (HIGH)

5. UX Patterns (HIGH)

6. Visual Design (HIGH)

How to Use

Reference Files