ux-craft-2026

name	ux-craft-2026
description	UX & content craft for high-end sites 2026 — information architecture & page blueprints (pages.yaml, hero archetypes, conversion section ordering), UX heuristics & conversion patterns, accessibility (WCAG 2.2 deep + deterministic CI), copywriting & microcopy, responsive & mobile craft. Use when: information architecture, sitemap, page blueprint, pages.yaml, hero archetype, conversion, landing page UX, pricing table, form UX, social proof, empty state, WCAG 2.2, accessibility audit, axe, target size, focus management, ARIA, microcopy, headline formula, value prop, responsive, mobile-first, dvh, touch targets, container queries. SKIP: visual styling/tokens (→design-system-2026), animation (→web-animation-router).
source	gemini-harvest-2026
risk	low-stakes

ux-craft-2026

Built from a 2026 deep knowledge-harvest (Gemini 3.5 + live web grounding), QC'd for cross-references and package names. Some design-system token values are tagged [UNVERIFIED] in the references — confirm against live docs before quoting exact numbers.

Use this skill when

• Designing IA / page blueprints (sitemap, sections, hero, conversion ordering) → pages.yaml
• Auditing UX/conversion or accessibility (WCAG 2.2) with deterministic checks
• Writing hero/section copy & microcopy, or making a site responsive/mobile-solid

Reference library

Topic	File
Knowledge Base: Information Architecture & Page Blueprint Methodology	references/ia_page_blueprint_kb.md
UX Heuristics & Conversion Patterns for Landing, SaaS, and E-commerce	references/ux-conversion-patterns.md
Accessibility: WCAG 2.2 Standards & Implementation Guide	references/accessibility-wcag22.md
Copywriting & Microcopy for Premium and Award Sites	references/copywriting-microcopy.md
Responsive & Mobile Craft for Motion and WebGL Sites	references/responsive-mobile-craft.md

How to use

Each reference is a self-contained, copy-paste-ready 2026 production guide. Route to the file matching the task, apply its recipes, and honor its antipatterns + accessibility/performance notes. Prefer the cheapest technique that satisfies the requirement (CSS before JS, native before library).