[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RAD8R0J2WX1PJVCYAJR4VZ":3,"skill-same:01M6RAD8R0J2WX1PJVCYAJR4VZ":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6RAD8R0J2WX1PJVCYAJR4VZ","ui-ux-pro-max",null,"UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Ffrontend\u002Fspecialists\u002Fui-ux-pro-max\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"ui ux","ux","pro","ui","ui ux pro max","max","improve","mode","card","chart","app","fix","projects","design","Tailwind","Animation","actions","search","css","MCP","2026-11-10 10:12:30",false,"---\nname: ui-ux-pro-max\ndescription: \"UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.\"\n---\n\n# UI\u002FUX Pro Max - Design Intelligence\n\nComprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations.\n\n## When to Apply\n\nThis Skill should be used when the task involves **UI structure, visual design decisions, interaction patterns, or user experience quality control**.\n\n### Must Use\n\nThis Skill must be invoked in the following situations:\n\n- Designing new pages (Landing Page, Dashboard, Admin, SaaS, Mobile App)\n- Creating or refactoring UI components (buttons, modals, forms, tables, charts, etc.)\n- Choosing color schemes, typography systems, spacing standards, or layout systems\n- Reviewing UI code for user experience, accessibility, or visual consistency\n- Implementing navigation structures, animations, or responsive behavior\n- Making product-level design decisions (style, information hierarchy, brand expression)\n- Improving perceived quality, clarity, or usability of interfaces\n\n### Recommended\n\nThis Skill is recommended in the following situations:\n\n- UI looks \"not professional enough\" but the reason is unclear\n- Receiving feedback on usability or experience\n- Pre-launch UI quality optimization\n- Aligning cross-platform design (Web \u002F iOS \u002F Android)\n- Building design systems or reusable component libraries\n\n### Skip\n\nThis Skill is not needed in the following situations:\n\n- Pure backend logic development\n- Only involving API or database design\n- Performance optimization unrelated to the interface\n- Infrastructure or DevOps work\n- Non-visual scripts or automation tasks\n\n**Decision criteria**: If the task will change how a feature **looks, feels, moves, or is interacted with**, this Skill should be used.\n\n## Rule Categories by Priority\n\n*For human\u002FAI reference: follow priority 1→10 to decide which rule category to focus on first; use `--domain \u003CDomain>` to query details when needed. Scripts do not read this table.*\n\n| Priority | Category | Impact | Domain | Key Checks (Must Have) | Anti-Patterns (Avoid) |\n|----------|----------|--------|--------|------------------------|------------------------|\n| 1 | Accessibility | CRITICAL | `ux` | Contrast 4.5:1, Alt text, Keyboard nav, Aria-labels | Removing focus rings, Icon-only buttons without labels |\n| 2 | Touch & Interaction | CRITICAL | `ux` | Min size 44×44px, 8px+ spacing, Loading feedback | Reliance on hover only, Instant state changes (0ms) |\n| 3 | Performance | HIGH | `ux` | WebP\u002FAVIF, Lazy loading, Reserve space (CLS < 0.1) | Layout thrashing, Cumulative Layout Shift |\n| 4 | Style Selection | HIGH | `style`, `product` | Match product type, Consistency, SVG icons (no emoji) | Mixing flat & skeuomorphic randomly, Emoji as icons |\n| 5 | Layout & Responsive | HIGH | `ux` | Mobile-first breakpoints, Viewport meta, No horizontal scroll | Horizontal scroll, Fixed px container widths, Disable zoom |\n| 6 | Typography & Color | MEDIUM | `typography`, `color` | Base 16px, Line-height 1.5, Semantic color tokens | Text < 12px body, Gray-on-gray, Raw hex in components |\n| 7 | Animation | MEDIUM | `ux` | Duration 150–300ms, Motion conveys meaning, Spatial continuity | Decorative-only animation, Animating width\u002Fheight, No reduced-motion |\n| 8 | Forms & Feedback | MEDIUM | `ux` | Visible labels, Error near field, Helper text, Progressive disclosure | Placeholder-only label, Errors only at top, Overwhelm upfront |\n| 9 | Navigation Patterns | HIGH | `ux` | Predictable back, Bottom nav ≤5, Deep linking | Overloaded nav, Broken back behavior, No deep links |\n| 10 | Charts & Data | LOW | `chart` | Legends, Tooltips, Accessible colors | Relying on color alone to convey meaning |\n\n## Quick Reference\n\n### 1. Accessibility (CRITICAL)\n\n- `color-contrast` - Minimum 4.5:1 ratio for normal text (large text 3:1); Material Design\n- `focus-states` - Visible focus rings on interactive elements (2–4px; Apple HIG, MD)\n- `alt-text` - Descriptive alt text for meaningful images\n- `aria-labels` - aria-label for icon-only buttons; accessibilityLabel in native (Apple HIG)\n- `keyboard-nav` - Tab order matches visual order; full keyboard support (Apple HIG)\n- `form-labels` - Use label with for attribute\n- `skip-links` - Skip to main content for keyboard users\n- `heading-hierarchy` - Sequential h1→h6, no level skip\n- `color-not-only` - Don't convey info by color alone (add icon\u002Ftext)\n- `dynamic-type` - Support system text scaling; avoid truncation as text grows (Apple Dynamic Type, MD)\n- `reduced-motion` - Respect prefers-reduced-motion; reduce\u002Fdisable animations when requested (Apple Reduced Motion API, MD)\n- `voiceover-sr` - Meaningful accessibilityLabel\u002FaccessibilityHint; logical reading order for VoiceOver\u002Fscreen readers (Apple HIG, MD)\n- `escape-routes` - Provide cancel\u002Fback in modals and multi-step flows (Apple HIG)\n- `keyboard-shortcuts` - Preserve system and a11y shortcuts; offer keyboard alternatives for drag-and-drop (Apple HIG)\n\n### 2. Touch & Interaction (CRITICAL)\n\n- `touch-target-size` - Min 44×44pt (Apple) \u002F 48×48dp (Material); extend hit area beyond visual bounds if needed\n- `touch-spacing` - Minimum 8px\u002F8dp gap between touch targets (Apple HIG, MD)\n- `hover-vs-tap` - Use click\u002Ftap for primary interactions; don't rely on hover alone\n- `loading-buttons` - Disable button during async operations; show spinner or progress\n- `error-feedback` - Clear error messages near problem\n- `cursor-pointer` - Add cursor-pointer to clickable elements (Web)\n- `gesture-conflicts` - Avoid horizontal swipe on main content; prefer vertical scroll\n- `tap-delay` - Use touch-action: manipulation to reduce 300ms delay (Web)\n- `standard-gestures` - Use platform standard gestures consistently; don't redefine (e.g. swipe-back, pinch-zoom) (Apple HIG)\n- `system-gestures` - Don't block system gestures (Control Center, back swipe, etc.) (Apple HIG)\n- `press-feedback` - Visual feedback on press (ripple\u002Fhighlight; MD state layers)\n- `haptic-feedback` - Use haptic for confirmations and important actions; avoid overuse (Apple HIG)\n- `gesture-alternative` - Don't rely on gesture-only interactions; always provide visible controls for critical actions\n- `safe-area-awareness` - Keep primary touch targets away from notch, Dynamic Island, gesture bar and screen edges\n- `no-precision-required` - Avoid requiring pixel-perfect taps on small icons or thin edges\n- `swipe-clarity` - Swipe actions must show clear affordance or hint (chevron, label, tutorial)\n- `drag-threshold` - Use a movement threshold before starting drag to avoid accidental drags\n\n### 3. Performance (HIGH)\n\n- `image-optimization` - Use WebP\u002FAVIF, responsive images (srcset\u002Fsizes), lazy load non-critical assets\n- `image-dimension` - Declare width\u002Fheight or use aspect-ratio to prevent layout shift (Core Web Vitals: CLS)\n- `font-loading` - Use font-display: swap\u002Foptional to avoid invisible text (FOIT); reserve space to reduce layout shift (MD)\n- `font-preload` - Preload only critical fonts; avoid overusing preload on every variant\n- `critical-css` - Prioritize above-the-fold CSS (inline critical CSS or early-loaded stylesheet)\n- `lazy-loading` - Lazy load non-hero components via dynamic import \u002F route-level splitting\n- `bundle-splitting` - Split code by route\u002Ffeature (React Suspense \u002F Next.js dynamic) to reduce initial load and TTI\n- `third-party-scripts` - Load third-party scripts async\u002Fdefer; audit and remove unnecessary ones (MD)\n- `reduce-reflows` - Avoid frequent layout reads\u002Fwrites; batch DOM reads then writes\n- `content-jumping` - Reserve space for async content to avoid layout jumps (Core Web Vitals: CLS)\n- `lazy-load-below-fold` - Use loading=\"lazy\" for below-the-fold images and heavy media\n- `virtualize-lists` - Virtualize lists with 50+ items to improve memory efficiency and scroll performance\n- `main-thread-budget` - Keep per-frame work under ~16ms for 60fps; move heavy tasks off main thread (HIG, MD)\n- `progressive-loading` - Use skeleton screens \u002F shimmer instead of long blocking spinners for >1s operations (Apple HIG)\n- `input-latency` - Keep input latency under ~100ms for taps\u002Fscrolls (Material responsiveness standard)\n- `tap-feedback-speed` - Provide visual feedback within 100ms of tap (Apple HIG)\n- `debounce-throttle` - Use debounce\u002Fthrottle for high-frequency events (scroll, resize, input)\n- `offline-support` - Provide offline state messaging and basic fallback (PWA \u002F mobile)\n- `network-fallback` - Offer degraded modes for slow networks (lower-res images, fewer animations)\n\n### 4. Style Selection (HIGH)\n\n- `style-match` - Match style to product type (use `--design-system` for recommendations)\n- `consistency` - Use same style across all pages\n- `no-emoji-icons` - Use SVG icons (Heroicons, Lucide), not emojis\n- `color-palette-from-product` - Choose palette from product\u002Findustry (search `--domain color`)\n- `effects-match-style` - Shadows, blur, radius aligned with chosen style (glass \u002F flat \u002F clay etc.)\n- `platform-adaptive` - Respect platform idioms (iOS HIG vs Material): navigation, controls, typography, motion\n- `state-clarity` - Make hover\u002Fpressed\u002Fdisabled states visually distinct while staying on-style (Material state layers)\n- `elevation-consistent` - Use a consistent elevation\u002Fshadow scale for cards, sheets, modals; avoid random shadow values\n- `dark-mode-pairing` - Design light\u002Fdark variants together to keep brand, contrast, and style consistent\n- `icon-style-consistent` - Use one icon set\u002Fvisual language (stroke width, corner radius) across the product\n- `system-controls` - Prefer native\u002Fsystem controls over fully custom ones; only customize when branding requires it (Apple HIG)\n- `blur-purpose` - Use blur to indicate background dismissal (modals, sheets), not as decoration (Apple HIG)\n- `primary-action` - Each screen should have only one primary CTA; secondary actions visually subordinate (Apple HIG)\n\n### 5. Layout & Responsive (HIGH)\n\n- `viewport-meta` - width=device-width initial-scale=1 (never disable zoom)\n- `mobile-first` - Design mobile-first, then scale up to tablet and desktop\n- `breakpoint-consistency` - Use systematic breakpoints (e.g. 375 \u002F 768 \u002F 1024 \u002F 1440)\n- `readable-font-size` - Minimum 16px body text on mobile (avoids iOS auto-zoom)\n- `line-length-control` - Mobile 35–60 chars per line; desktop 60–75 chars\n- `horizontal-scroll` - No horizontal scroll on mobile; ensure content fits viewport width\n- `spacing-scale` - Use 4pt\u002F8dp incremental spacing system (Material Design)\n- `touch-density` - Keep component spacing comfortable for touch: not cramped, not causing mis-taps\n- `container-width` - Consistent max-width on desktop (max-w-6xl \u002F 7xl)\n- `z-index-management` - Define layered z-index scale (e.g. 0 \u002F 10 \u002F 20 \u002F 40 \u002F 100 \u002F 1000)\n- `fixed-element-offset` - Fixed navbar\u002Fbottom bar must reserve safe padding for underlying content\n- `scroll-behavior` - Avoid nested scroll regions that interfere with the main scroll experience\n- `viewport-units` - Prefer min-h-dvh over 100vh on mobile\n- `orientation-support` - Keep layout readable and operable in landscape mode\n- `content-priority` - Show core content first on mobile; fold or hide secondary content\n- `visual-hierarchy` - Establish hierarchy via size, spacing, contrast — not color alone\n\n### 6. Typography & Color (MEDIUM)\n\n- `line-height` - Use 1.5-1.75 for body text\n- `line-length` - Limit to 65-75 characters per line\n- `font-pairing` - Match heading\u002Fbody font personalities\n- `font-scale` - Consistent type scale (e.g. 12 14 16 18 24 32)\n- `contrast-readability` - Darker text on light backgrounds (e.g. slate-900 on white)\n- `text-styles-system` - Use platform type system: iOS 11 Dynamic Type styles \u002F Material 5 type roles (display, headline, title, body, label) (HIG, MD)\n- `weight-hierarchy` - Use font-weight to reinforce hierarchy: Bold headings (600–700), Regular body (400), Medium labels (500) (MD)\n- `color-semantic` - Define semantic color tokens (primary, secondary, error, surface, on-surface) not raw hex in components (Material color system)\n- `color-dark-mode` - Dark mode uses desaturated \u002F lighter tonal variants, not inverted colors; test contrast separately (HIG, MD)\n- `color-accessible-pairs` - Foreground\u002Fbackground pairs must meet 4.5:1 (AA) or 7:1 (AAA); use tools to verify (WCAG, MD)\n- `color-not-decorative-only` - Functional color (error red, success green) must include icon\u002Ftext; avoid color-only meaning (HIG, MD)\n- `truncation-strategy` - Prefer wrapping over truncation; when truncating use ellipsis and provide full text via tooltip\u002Fexpand (Apple HIG)\n- `letter-spacing` - Respect default letter-spacing per platform; avoid tight tracking on body text (HIG, MD)\n- `number-tabular` - Use tabular\u002Fmonospaced figures for data columns, prices, and timers to prevent layout shift\n- `whitespace-balance` - Use whitespace intentionally to group related items and separate sections; avoid visual clutter (Apple HIG)\n\n### 7. Animation (MEDIUM)\n\n- `duration-timing` - Use 150–300ms for micro-interactions; complex transitions ≤400ms; avoid >500ms (MD)\n- `transform-performance` - Use transform\u002Fopacity only; avoid animating width\u002Fheight\u002Ftop\u002Fleft\n- `loading-states` - Show skeleton or progress indicator when loading exceeds 300ms\n- `excessive-motion` - Animate 1-2 key elements per view max\n- `easing` - Use ease-out for entering, ease-in for exiting; avoid linear for UI transitions\n- `motion-meaning` - Every animation must express a cause-effect relationship, not just be decorative (Apple HIG)\n- `state-transition` - State changes (hover \u002F active \u002F expanded \u002F collapsed \u002F modal) should animate smoothly, not snap\n- `continuity` - Page\u002Fscreen transitions should maintain spatial continuity (shared element, directional slide) (Apple HIG)\n- `parallax-subtle` - Use parallax sparingly; must respect reduced-motion and not cause disorientation (Apple HIG)\n- `spring-physics` - Prefer spring\u002Fphysics-based curves over linear or cubic-bezier for natural feel (Apple HIG fluid animations)\n- `exit-faster-than-enter` - Exit animations shorter than enter (~60–70% of enter duration) to feel responsive (MD motion)\n- `stagger-sequence` - Stagger list\u002Fgrid item entrance by 30–50ms per item; avoid all-at-once or too-slow reveals (MD)\n- `shared-element-transition` - Use shared element \u002F hero transitions for visual continuity between screens (MD, HIG)\n- `interruptible` - Animations must be interruptible; user tap\u002Fgesture cancels in-progress animation immediately (Apple HIG)\n- `no-blocking-animation` - Never block user input during an animation; UI must stay interactive (Apple HIG)\n- `fade-crossfade` - Use crossfade for content replacement within the same container (MD)\n- `scale-feedback` - Subtle scale (0.95–1.05) on press for tappable cards\u002Fbuttons; restore on release (HIG, MD)\n- `gesture-feedback` - Drag, swipe, and pinch must provide real-time visual response tracking the finger (MD Motion)\n- `hierarchy-motion` - Use translate\u002Fscale direction to express hierarchy: enter from below = deeper, exit upward = back (MD)\n- `motion-consistency` - Unify duration\u002Feasing tokens globally; all animations share the same rhythm and feel\n- `opacity-threshold` - Fading elements should not linger below opacity 0.2; either fade fully or remain visible\n- `modal-motion` - Modals\u002Fsheets should animate from their trigger source (scale+fade or slide-in) for spatial context (HIG, MD)\n- `navigation-direction` - Forward navigation animates left\u002Fup; backward animates right\u002Fdown — keep direction logically consistent (HIG)\n- `layout-shift-avoid` - Animations must not cause layout reflow or CLS; use transform for position changes\n\n### 8. Forms & Feedback (MEDIUM)\n\n- `input-labels` - Visible label per input (not placeholder-only)\n- `error-placement` - Show error below the related field\n- `submit-feedback` - Loading then success\u002Ferror state on submit\n- `required-indicators` - Mark required fields (e.g. asterisk)\n- `empty-states` - Helpful message and action when no content\n- `toast-dismiss` - Auto-dismiss toasts in 3-5s\n- `confirmation-dialogs` - Confirm before destructive actions\n- `input-helper-text` - Provide persistent helper text below complex inputs, not just placeholder (Material Design)\n- `disabled-states` - Disabled elements use reduced opacity (0.38–0.5) + cursor change + semantic attribute (MD)\n- `progressive-disclosure` - Reveal complex options progressively; don't overwhelm users upfront (Apple HIG)\n- `inline-validation` - Validate on blur (not keystroke); show error only after user finishes input (MD)\n- `input-type-keyboard` - Use semantic input types (email, tel, number) to trigger the correct mobile keyboard (HIG, MD)\n- `password-toggle` - Provide show\u002Fhide toggle for password fields (MD)\n- `autofill-support` - Use autocomplete \u002F textContentType attributes so the system can autofill (HIG, MD)\n- `undo-support` - Allow undo for destructive or bulk actions (e.g. \"Undo delete\" toast) (Apple HIG)\n- `success-feedback` - Confirm completed actions with brief visual feedback (checkmark, toast, color flash) (MD)\n- `error-recovery` - Error messages must include a clear recovery path (retry, edit, help link) (HIG, MD)\n- `multi-step-progress` - Multi-step flows show step indicator or progress bar; allow back navigation (MD)\n- `form-autosave` - Long forms should auto-save drafts to prevent data loss on accidental dismissal (Apple HIG)\n- `sheet-dismiss-confirm` - Confirm before dismissing a sheet\u002Fmodal with unsaved changes (Apple HIG)\n- `error-clarity` - Error messages must state cause + how to fix (not just \"Invalid input\") (HIG, MD)\n- `field-grouping` - Group related fields logically (fieldset\u002Flegend or visual grouping) (MD)\n- `read-only-distinction` - Read-only state should be visually and semantically different from disabled (MD)\n- `focus-management` - After submit error, auto-focus the first invalid field (WCAG, MD)\n- `error-summary` - For multiple errors, show summary at top with anchor links to each field (WCAG)\n- `touch-friendly-input` - Mobile input height ≥44px to meet touch target requirements (Apple HIG)\n- `destructive-emphasis` - Destructive actions use semantic danger color (red) and are visually separated from primary actions (HIG, MD)\n- `toast-accessibility` - Toasts must not steal focus; use aria-live=\"polite\" for screen reader announcement (WCAG)\n- `aria-live-errors` - Form errors use aria-live region or role=\"alert\" to notify screen readers (WCAG)\n- `contrast-feedback` - Error and success state colors must meet 4.5:1 contrast ratio (WCAG, MD)\n- `timeout-feedback` - Request timeout must show clear feedback with retry option (MD)\n\n### 9. Navigation Patterns (HIGH)\n\n- `bottom-nav-limit` - Bottom navigation max 5 items; use labels with icons (Material Design)\n- `drawer-usage` - Use drawer\u002Fsidebar for secondary navigation, not primary actions (Material Design)\n- `back-behavior` - Back navigation must be predictable and consistent; preserve scroll\u002Fstate (Apple HIG, MD)\n- `deep-linking` - All key screens must be reachable via deep link \u002F URL for sharing and notifications (Apple HIG, MD)\n- `tab-bar-ios` - iOS: use bottom Tab Bar for top-level navigation (Apple HIG)\n- `top-app-bar-android` - Android: use Top App Bar with navigation icon for primary structure (Material Design)\n- `nav-label-icon` - Navigation items must have both icon and text label; icon-only nav harms discoverability (MD)\n- `nav-state-active` - Current location must be visually highlighted (color, weight, indicator) in navigation (HIG, MD)\n- `nav-hierarchy` - Primary nav (tabs\u002Fbottom bar) vs secondary nav (drawer\u002Fsettings) must be clearly separated (MD)\n- `modal-escape` - Modals and sheets must offer a clear close\u002Fdismiss affordance; swipe-down to dismiss on mobile (Apple HIG)\n- `search-accessible` - Search must be easily reachable (top bar or tab); provide recent\u002Fsuggested queries (MD)\n- `breadcrumb-web` - Web: use breadcrumbs for 3+ level deep hierarchies to aid orientation (MD)\n- `state-preservation` - Navigating back must restore previous scroll position, filter state, and input (HIG, MD)\n- `gesture-nav-support` - Support system gesture navigation (iOS swipe-back, Android predictive back) without conflict (HIG, MD)\n- `tab-badge` - Use badges on nav items sparingly to indicate unread\u002Fpending; clear after user visits (HIG, MD)\n- `overflow-menu` - When actions exceed available space, use overflow\u002Fmore menu instead of cramming (MD)\n- `bottom-nav-top-level` - Bottom nav is for top-level screens only; never nest sub-navigation inside it (MD)\n- `adaptive-navigation` - Large screens (≥1024px) prefer sidebar; small screens use bottom\u002Ftop nav (Material Adaptive)\n- `back-stack-integrity` - Never silently reset the navigation stack or unexpectedly jump to home (HIG, MD)\n- `navigation-consistency` - Navigation placement must stay the same across all pages; don't change by page type\n- `avoid-mixed-patterns` - Don't mix Tab + Sidebar + Bottom Nav at the same hierarchy level\n- `modal-vs-navigation` - Modals must not be used for primary navigation flows; they break the user's path (HIG)\n- `focus-on-route-change` - After page transition, move focus to main content region for screen reader users (WCAG)\n- `persistent-nav` - Core navigation must remain reachable from deep pages; don't hide it entirely in sub-flows (HIG, MD)\n- `destructive-nav-separation` - Dangerous actions (delete account, logout) must be visually and spatially separated from normal nav items (HIG, MD)\n- `empty-nav-state` - When a nav destination is unavailable, explain why instead of silently hiding it (MD)\n\n### 10. Charts & Data (LOW)\n\n- `chart-type` - Match chart type to data type (trend → line, comparison → bar, proportion → pie\u002Fdonut)\n- `color-guidance` - Use accessible color palettes; avoid red\u002Fgreen only pairs for colorblind users (WCAG, MD)\n- `data-table` - Provide table alternative for accessibility; charts alone are not screen-reader friendly (WCAG)\n- `pattern-texture` - Supplement color with patterns, textures, or shapes so data is distinguishable without color (WCAG, MD)\n- `legend-visible` - Always show legend; position near the chart, not detached below a scroll fold (MD)\n- `tooltip-on-interact` - Provide tooltips\u002Fdata labels on hover (Web) or tap (mobile) showing exact values (HIG, MD)\n- `axis-labels` - Label axes with units and readable scale; avoid truncated or rotated labels on mobile\n- `responsive-chart` - Charts must reflow or simplify on small screens (e.g. horizontal bar instead of vertical, fewer ticks)\n- `empty-data-state` - Show meaningful empty state when no data exists (\"No data yet\" + guidance), not a blank chart (MD)\n- `loading-chart` - Use skeleton or shimmer placeholder while chart data loads; don't show an empty axis frame\n- `animation-optional` - Chart entrance animations must respect prefers-reduced-motion; data should be readable immediately (HIG)\n- `large-dataset` - For 1000+ data points, aggregate or sample; provide drill-down for detail instead of rendering all (MD)\n- `number-formatting` - Use locale-aware formatting for numbers, dates, currencies on axes and labels (HIG, MD)\n- `touch-target-chart` - Interactive chart elements (points, segments) must have ≥44pt tap area or expand on touch (Apple HIG)\n- `no-pie-overuse` - Avoid pie\u002Fdonut for >5 categories; switch to bar chart for clarity\n- `contrast-data` - Data lines\u002Fbars vs background ≥3:1; data text labels ≥4.5:1 (WCAG)\n- `legend-interactive` - Legends should be clickable to toggle series visibility (MD)\n- `direct-labeling` - For small datasets, label values directly on the chart to reduce eye travel\n- `tooltip-keyboard` - Tooltip content must be keyboard-reachable and not rely on hover alone (WCAG)\n- `sortable-table` - Data tables must support sorting with aria-sort indicating current sort state (WCAG)\n- `axis-readability` - Axis ticks must not be cramped; maintain readable spacing, auto-skip on small screens\n- `data-density` - Limit information density per chart to avoid cognitive overload; split into multiple charts if needed\n- `trend-emphasis` - Emphasize data trends over decoration; avoid heavy gradients\u002Fshadows that obscure the data\n- `gridline-subtle` - Grid lines should be low-contrast (e.g. gray-200) so they don't compete with data\n- `focusable-elements` - Interactive chart elements (points, bars, slices) must be keyboard-navigable (WCAG)\n- `screen-reader-summary` - Provide a text summary or aria-label describing the chart's key insight for screen readers (WCAG)\n- `error-state-chart` - Data load failure must show error message with retry action, not a broken\u002Fempty chart\n- `export-option` - For data-heavy products, offer CSV\u002Fimage export of chart data\n- `drill-down-consistency` - Drill-down interactions must maintain a clear back-path and hierarchy breadcrumb\n- `time-scale-clarity` - Time series charts must clearly label time granularity (day\u002Fweek\u002Fmonth) and allow switching\n\n## How to Use\n\nSearch specific domains using the CLI tool below.\n\n---\n\n## Prerequisites\n\nCheck if Python is installed:\n\n```bash\npython3 --version || python --version\n```\n\nIf Python is not installed, install it based on user's OS:\n\n**macOS:**\n```bash\nbrew install python3\n```\n\n**Ubuntu\u002FDebian:**\n```bash\nsudo apt update && sudo apt install python3\n```\n\n**Windows:**\n```powershell\nwinget install Python.Python.3.12\n```\n\n---\n\n## How to Use This Skill\n\nUse this skill when the user requests any of the following:\n\n| Scenario | Trigger Examples | Start From |\n|----------|-----------------|------------|\n| **New project \u002F page** | \"Build a landing page\", \"Build a dashboard\" | Step 1 → Step 2 (design system) |\n| **New component** | \"Create a pricing card\", \"Add a modal\" | Step 3 (domain search: style, ux) |\n| **Choose style \u002F color \u002F font** | \"What style fits a fintech app?\", \"Recommend a color palette\" | Step 2 (design system) |\n| **Review existing UI** | \"Review this page for UX issues\", \"Check accessibility\" | Quick Reference checklist above |\n| **Fix a UI bug** | \"Button hover is broken\", \"Layout shifts on load\" | Quick Reference → relevant section |\n| **Improve \u002F optimize** | \"Make this faster\", \"Improve mobile experience\" | Step 3 (domain search: ux, react) |\n| **Implement dark mode** | \"Add dark mode support\" | Step 3 (domain: style \"dark mode\") |\n| **Add charts \u002F data viz** | \"Add an analytics dashboard chart\" | Step 3 (domain: chart) |\n| **Stack best practices** | \"React performance tips\"、\"SwiftUI navigation\" | Step 4 (stack search) |\n\nFollow this workflow:\n\n### Step 1: Analyze User Requirements\n\nExtract key information from user request:\n- **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid\n- **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work)\n- **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc.\n- **Stack**: React Native (this project's only tech stack)\n\n### Step 2: Generate Design System (REQUIRED)\n\n**Always start with `--design-system`** to get comprehensive recommendations with reasoning:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cproduct_type> \u003Cindustry> \u003Ckeywords>\" --design-system [-p \"Project Name\"]\n```\n\nThis command:\n1. Searches domains in parallel (product, style, color, landing, typography)\n2. Applies reasoning rules from `ui-reasoning.csv` to select best matches\n3. Returns complete design system: pattern, style, colors, typography, effects\n4. Includes anti-patterns to avoid\n\n**Example:**\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"beauty spa wellness service\" --design-system -p \"Serenity Spa\"\n```\n\n### Step 2b: Persist Design System (Master + Overrides Pattern)\n\nTo save the design system for **hierarchical retrieval across sessions**, add `--persist`:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cquery>\" --design-system --persist -p \"Project Name\"\n```\n\nThis creates:\n- `design-system\u002FMASTER.md` — Global Source of Truth with all design rules\n- `design-system\u002Fpages\u002F` — Folder for page-specific overrides\n\n**With page-specific override:**\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cquery>\" --design-system --persist -p \"Project Name\" --page \"dashboard\"\n```\n\nThis also creates:\n- `design-system\u002Fpages\u002Fdashboard.md` — Page-specific deviations from Master\n\n**How hierarchical retrieval works:**\n1. When building a specific page (e.g., \"Checkout\"), first check `design-system\u002Fpages\u002Fcheckout.md`\n2. If the page file exists, its rules **override** the Master file\n3. If not, use `design-system\u002FMASTER.md` exclusively\n\n**Context-aware retrieval prompt:**\n```\nI am building the [Page Name] page. Please read design-system\u002FMASTER.md.\nAlso check if design-system\u002Fpages\u002F[page-name].md exists.\nIf the page file exists, prioritize its rules.\nIf not, use the Master rules exclusively.\nNow, generate the code...\n```\n\n### Step 3: Supplement with Detailed Searches (as needed)\n\nAfter getting the design system, use domain searches to get additional details:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Ckeyword>\" --domain \u003Cdomain> [-n \u003Cmax_results>]\n```\n\n**When to use detailed searches:**\n\n| Need | Domain | Example |\n|------|--------|---------|\n| Product type patterns | `product` | `--domain product \"entertainment social\"` |\n| More style options | `style` | `--domain style \"glassmorphism dark\"` |\n| Color palettes | `color` | `--domain color \"entertainment vibrant\"` |\n| Font pairings | `typography` | `--domain typography \"playful modern\"` |\n| Chart recommendations | `chart` | `--domain chart \"real-time dashboard\"` |\n| UX best practices | `ux` | `--domain ux \"animation accessibility\"` |\n| Alternative fonts | `typography` | `--domain typography \"elegant luxury\"` |\n| Individual Google Fonts | `google-fonts` | `--domain google-fonts \"sans serif popular variable\"` |\n| Landing structure | `landing` | `--domain landing \"hero social-proof\"` |\n| React Native perf | `react` | `--domain react \"rerender memo list\"` |\n| App interface a11y | `web` | `--domain web \"accessibilityLabel touch safe-areas\"` |\n| AI prompt \u002F CSS keywords | `prompt` | `--domain prompt \"minimalism\"` |\n\n### Step 4: Stack Guidelines (React Native)\n\nGet React Native implementation-specific best practices:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Ckeyword>\" --stack react-native\n```\n\n---\n\n## Search Reference\n\n### Available Domains\n\n| Domain | Use For | Example Keywords |\n|--------|---------|------------------|\n| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |\n| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |\n| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |\n| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |\n| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |\n| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |\n| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |\n| `google-fonts` | Individual Google Fonts lookup | sans serif, monospace, japanese, variable font, popular |\n| `react` | React\u002FNext.js performance | waterfall, bundle, suspense, memo, rerender, cache |\n| `web` | App interface guidelines (iOS\u002FAndroid\u002FReact Native) | accessibilityLabel, touch targets, safe areas, Dynamic Type |\n| `prompt` | AI prompts, CSS keywords | (style name) |\n\n### Available Stacks\n\n| Stack | Focus |\n|-------|-------|\n| `react-native` | Components, Navigation, Lists |\n\n---\n\n## Example Workflow\n\n**User request:** \"Make an AI search homepage.\"\n\n### Step 1: Analyze Requirements\n- Product type: Tool (AI search engine)\n- Target audience: C-end users looking for fast, intelligent search\n- Style keywords: modern, minimal, content-first, dark mode\n- Stack: React Native\n\n### Step 2: Generate Design System (REQUIRED)\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"AI search tool modern minimal\" --design-system -p \"AI Search\"\n```\n\n**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.\n\n### Step 3: Supplement with Detailed Searches (as needed)\n\n```bash\n# Get style options for a modern tool product\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"minimalism dark mode\" --domain style\n\n# Get UX best practices for search interaction and loading\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"search loading animation\" --domain ux\n```\n\n### Step 4: Stack Guidelines\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"list performance navigation\" --stack react-native\n```\n\n**Then:** Synthesize design system + detailed searches and implement the design.\n\n---\n\n## Output Formats\n\nThe `--design-system` flag supports two output formats:\n\n```bash\n# ASCII box (default) - best for terminal display\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"fintech crypto\" --design-system\n\n# Markdown - best for documentation\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"fintech crypto\" --design-system -f markdown\n```\n\n---\n\n## Tips for Better Results\n\n### Query Strategy\n\n- Use **multi-dimensional keywords** — combine product + industry + tone + density: `\"entertainment social vibrant content-dense\"` not just `\"app\"`\n- Try different keywords for the same need: `\"playful neon\"` → `\"vibrant dark\"` → `\"content-first minimal\"`\n- Use `--design-system` first for full recommendations, then `--domain` to deep-dive any dimension you're unsure about\n- Always add `--stack react-native` for implementation-specific guidance\n\n### Common Sticking Points\n\n| Problem | What to Do |\n|---------|------------|\n| Can't decide on style\u002Fcolor | Re-run `--design-system` with different keywords |\n| Dark mode contrast issues | Quick Reference §6: `color-dark-mode` + `color-accessible-pairs` |\n| Animations feel unnatural | Quick Reference §7: `spring-physics` + `easing` + `exit-faster-than-enter` |\n| Form UX is poor | Quick Reference §8: `inline-validation` + `error-clarity` + `focus-management` |\n| Navigation feels confusing | Quick Reference §9: `nav-hierarchy` + `bottom-nav-limit` + `back-behavior` |\n| Layout breaks on small screens | Quick Reference §5: `mobile-first` + `breakpoint-consistency` |\n| Performance \u002F jank | Quick Reference §3: `virtualize-lists` + `main-thread-budget` + `debounce-throttle` |\n\n### Pre-Delivery Checklist\n\n- Run `--domain ux \"animation accessibility z-index loading\"` as a UX validation pass before implementation\n- Run through Quick Reference **§1–§3** (CRITICAL + HIGH) as a final review\n- Test on 375px (small phone) and landscape orientation\n- Verify behavior with **reduced-motion** enabled and **Dynamic Type** at largest size\n- Check dark mode contrast independently (don't assume light mode values work)\n- Confirm all touch targets ≥44pt and no content hidden behind safe areas\n\n---\n\n## Common Rules for Professional UI\n\nThese are frequently overlooked issues that make UI look unprofessional:\nScope notice: The rules below are for App UI (iOS\u002FAndroid\u002FReact Native\u002FFlutter), not desktop-web interaction patterns.\n\n### Icons & Visual Elements\n\n| Rule | Standard | Avoid | Why It Matters |\n|------|----------|--------|----------------|\n| **No Emoji as Structural Icons** | Use vector-based icons (e.g., Lucide, react-native-vector-icons, @expo\u002Fvector-icons). | Using emojis (? ? ⚙️) for navigation, settings, or system controls. | Emojis are font-dependent, inconsistent across platforms, and cannot be controlled via design tokens. |\n| **Vector-Only Assets** | Use SVG or platform vector icons that scale cleanly and support theming. | Raster PNG icons that blur or pixelate. | Ensures scalability, crisp rendering, and dark\u002Flight mode adaptability. |\n| **Stable Interaction States** | Use color, opacity, or elevation transitions for press states without changing layout bounds. | Layout-shifting transforms that move surrounding content or trigger visual jitter. | Prevents unstable interactions and preserves smooth motion\u002Fperceived quality on mobile. |\n| **Correct Brand Logos** | Use official brand assets and follow their usage guidelines (spacing, color, clear space). | Guessing logo paths, recoloring unofficially, or modifying proportions. | Prevents brand misuse and ensures legal\u002Fplatform compliance. |\n| **Consistent Icon Sizing** | Define icon sizes as design tokens (e.g., icon-sm, icon-md = 24pt, icon-lg). | Mixing arbitrary values like 20pt \u002F 24pt \u002F 28pt randomly. | Maintains rhythm and visual hierarchy across the interface. |\n| **Stroke Consistency** | Use a consistent stroke width within the same visual layer (e.g., 1.5px or 2px). | Mixing thick and thin stroke styles arbitrarily. | Inconsistent strokes reduce perceived polish and cohesion. |\n| **Filled vs Outline Discipline** | Use one icon style per hierarchy level. | Mixing filled and outline icons at the same hierarchy level. | Maintains semantic clarity and stylistic coherence. |\n| **Touch Target Minimum** | Minimum 44×44pt interactive area (use hitSlop if icon is smaller). | Small icons without expanded tap area. | Meets accessibility and platform usability standards. |\n| **Icon Alignment** | Align icons to text baseline and maintain consistent padding. | Misaligned icons or inconsistent spacing around them. | Prevents subtle visual imbalance that reduces perceived quality. |\n| **Icon Contrast** | Follow WCAG contrast standards: 4.5:1 for small elements, 3:1 minimum for larger UI glyphs. | Low-contrast icons that blend into the background. | Ensures accessibility in both light and dark modes. |\n\n\n### Interaction (App)\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Tap feedback** | Provide clear pressed feedback (ripple\u002Fopacity\u002Felevation) within 80-150ms | No visual response on tap |\n| **Animation timing** | Keep micro-interactions around 150-300ms with platform-native easing | Instant transitions or slow animations (>500ms) |\n| **Accessibility focus** | Ensure screen reader focus order matches visual order and labels are descriptive | Unlabeled controls or confusing focus traversal |\n| **Disabled state clarity** | Use disabled semantics (`disabled`\u002Fnative disabled props), reduced emphasis, and no tap action | Controls that look tappable but do nothing |\n| **Touch target minimum** | Keep tap areas >=44x44pt (iOS) or >=48x48dp (Android), expand hit area when icon is smaller | Tiny tap targets or icon-only hit areas without padding |\n| **Gesture conflict prevention** | Keep one primary gesture per region and avoid nested tap\u002Fdrag conflicts | Overlapping gestures causing accidental actions |\n| **Semantic native controls** | Prefer native interactive primitives (`Button`, `Pressable`, platform equivalents) with proper accessibility roles | Generic containers used as primary controls without semantics |\n\n### Light\u002FDark Mode Contrast\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Surface readability (light)** | Keep cards\u002Fsurfaces clearly separated from background with sufficient opacity\u002Felevation | Overly transparent surfaces that blur hierarchy |\n| **Text contrast (light)** | Maintain body text contrast >=4.5:1 against light surfaces | Low-contrast gray body text |\n| **Text contrast (dark)** | Maintain primary text contrast >=4.5:1 and secondary text >=3:1 on dark surfaces | Dark mode text that blends into background |\n| **Border and divider visibility** | Ensure separators are visible in both themes (not just light mode) | Theme-specific borders disappearing in one mode |\n| **State contrast parity** | Keep pressed\u002Ffocused\u002Fdisabled states equally distinguishable in light and dark themes | Defining interaction states for one theme only |\n| **Token-driven theming** | Use semantic color tokens mapped per theme across app surfaces\u002Ftext\u002Ficons | Hardcoded per-screen hex values |\n| **Scrim and modal legibility** | Use a modal scrim strong enough to isolate foreground content (typically 40-60% black) | Weak scrim that leaves background visually competing |\n\n### Layout & Spacing\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Safe-area compliance** | Respect top\u002Fbottom safe areas for all fixed headers, tab bars, and CTA bars | Placing fixed UI under notch, status bar, or gesture area |\n| **System bar clearance** | Add spacing for status\u002Fnavigation bars and gesture home indicator | Let tappable content collide with OS chrome |\n| **Consistent content width** | Keep predictable content width per device class (phone\u002Ftablet) | Mixing arbitrary widths between screens |\n| **8dp spacing rhythm** | Use a consistent 4\u002F8dp spacing system for padding\u002Fgaps\u002Fsection spacing | Random spacing increments with no rhythm |\n| **Readable text measure** | Keep long-form text readable on large devices (avoid edge-to-edge paragraphs on tablets) | Full-width long text that hurts readability |\n| **Section spacing hierarchy** | Define clear vertical rhythm tiers (e.g., 16\u002F24\u002F32\u002F48) by hierarchy | Similar UI levels with inconsistent spacing |\n| **Adaptive gutters by breakpoint** | Increase horizontal insets on larger widths and in landscape | Same narrow gutter on all device sizes\u002Forientations |\n| **Scroll and fixed element coexistence** | Add bottom\u002Ftop content insets so lists are not hidden behind fixed bars | Scroll content obscured by sticky headers\u002Ffooters |\n\n---\n\n## Pre-Delivery Checklist\n\nBefore delivering UI code, verify these items:\nScope notice: This checklist is for App UI (iOS\u002FAndroid\u002FReact Native\u002FFlutter).\n\n### Visual Quality\n- [ ] No emojis used as icons (use SVG instead)\n- [ ] All icons come from a consistent icon family and style\n- [ ] Official brand assets are used with correct proportions and clear space\n- [ ] Pressed-state visuals do not shift layout bounds or cause jitter\n- [ ] Semantic theme tokens are used consistently (no ad-hoc per-screen hardcoded colors)\n\n### Interaction\n- [ ] All tappable elements provide clear pressed feedback (ripple\u002Fopacity\u002Felevation)\n- [ ] Touch targets meet minimum size (>=44x44pt iOS, >=48x48dp Android)\n- [ ] Micro-interaction timing stays in the 150-300ms range with native-feeling easing\n- [ ] Disabled states are visually clear and non-interactive\n- [ ] Screen reader focus order matches visual order, and interactive labels are descriptive\n- [ ] Gesture regions avoid nested\u002Fconflicting interactions (tap\u002Fdrag\u002Fback-swipe conflicts)\n\n### Light\u002FDark Mode\n- [ ] Primary text contrast >=4.5:1 in both light and dark mode\n- [ ] Secondary text contrast >=3:1 in both light and dark mode\n- [ ] Dividers\u002Fborders and interaction states are distinguishable in both modes\n- [ ] Modal\u002Fdrawer scrim opacity is strong enough to preserve foreground legibility (typically 40-60% black)\n- [ ] Both themes are tested before delivery (not inferred from a single theme)\n\n### Layout\n- [ ] Safe areas are respected for headers, tab bars, and bottom CTA bars\n- [ ] Scroll content is not hidden behind fixed\u002Fsticky bars\n- [ ] Verified on small phone, large phone, and tablet (portrait + landscape)\n- [ ] Horizontal insets\u002Fgutters adapt correctly by device size and orientation\n- [ ] 4\u002F8dp spacing rhythm is maintained across component, section, and page levels\n- [ ] Long-form text measure remains readable on larger devices (no edge-to-edge paragraphs)\n\n### Accessibility\n- [ ] All meaningful images\u002Ficons have accessibility labels\n- [ ] Form fields have labels, hints, and clear error messages\n- [ ] Color is not the only indicator\n- [ ] Reduced motion and dynamic text size are supported without layout breakage\n- [ ] Accessibility traits\u002Froles\u002Fstates (selected, disabled, expanded) are announced correctly","# UI\u002FUX Pro Max - Design Intelligence\n\nComprehensive design guide for web and mobile applications. Contains 50+ styles, 161 color palettes, 57 font pairings, 161 product types with reasoning rules, 99 UX guidelines, and 25 chart types across 10 technology stacks. Searchable database with priority-based recommendations.\n\n## When to Apply\n\nThis Skill should be used when the task involves **UI structure, visual design decisions, interaction patterns, or user experience quality control**.\n\n### Must Use\n\nThis Skill must be invoked in the following situations:\n\n- Designing new pages (Landing Page, Dashboard, Admin, SaaS, Mobile App)\n- Creating or refactoring UI components (buttons, modals, forms, tables, charts, etc.)\n- Choosing color schemes, typography systems, spacing standards, or layout systems\n- Reviewing UI code for user experience, accessibility, or visual consistency\n- Implementing navigation structures, animations, or responsive behavior\n- Making product-level design decisions (style, information hierarchy, brand expression)\n- Improving perceived quality, clarity, or usability of interfaces\n\n### Recommended\n\nThis Skill is recommended in the following situations:\n\n- UI looks \"not professional enough\" but the reason is unclear\n- Receiving feedback on usability or experience\n- Pre-launch UI quality optimization\n- Aligning cross-platform design (Web \u002F iOS \u002F Android)\n- Building design systems or reusable component libraries\n\n### Skip\n\nThis Skill is not needed in the following situations:\n\n- Pure backend logic development\n- Only involving API or database design\n- Performance optimization unrelated to the interface\n- Infrastructure or DevOps work\n- Non-visual scripts or automation tasks\n\n**Decision criteria**: If the task will change how a feature **looks, feels, moves, or is interacted with**, this Skill should be used.\n\n## Rule Categories by Priority\n\n*For human\u002FAI reference: follow priority 1→10 to decide which rule category to focus on first; use `--domain \u003CDomain>` to query details when needed. Scripts do not read this table.*\n\n| Priority | Category | Impact | Domain | Key Checks (Must Have) | Anti-Patterns (Avoid) |\n|----------|----------|--------|--------|------------------------|------------------------|\n| 1 | Accessibility | CRITICAL | `ux` | Contrast 4.5:1, Alt text, Keyboard nav, Aria-labels | Removing focus rings, Icon-only buttons without labels |\n| 2 | Touch & Interaction | CRITICAL | `ux` | Min size 44×44px, 8px+ spacing, Loading feedback | Reliance on hover only, Instant state changes (0ms) |\n| 3 | Performance | HIGH | `ux` | WebP\u002FAVIF, Lazy loading, Reserve space (CLS < 0.1) | Layout thrashing, Cumulative Layout Shift |\n| 4 | Style Selection | HIGH | `style`, `product` | Match product type, Consistency, SVG icons (no emoji) | Mixing flat & skeuomorphic randomly, Emoji as icons |\n| 5 | Layout & Responsive | HIGH | `ux` | Mobile-first breakpoints, Viewport meta, No horizontal scroll | Horizontal scroll, Fixed px container widths, Disable zoom |\n| 6 | Typography & Color | MEDIUM | `typography`, `color` | Base 16px, Line-height 1.5, Semantic color tokens | Text < 12px body, Gray-on-gray, Raw hex in components |\n| 7 | Animation | MEDIUM | `ux` | Duration 150–300ms, Motion conveys meaning, Spatial continuity | Decorative-only animation, Animating width\u002Fheight, No reduced-motion |\n| 8 | Forms & Feedback | MEDIUM | `ux` | Visible labels, Error near field, Helper text, Progressive disclosure | Placeholder-only label, Errors only at top, Overwhelm upfront |\n| 9 | Navigation Patterns | HIGH | `ux` | Predictable back, Bottom nav ≤5, Deep linking | Overloaded nav, Broken back behavior, No deep links |\n| 10 | Charts & Data | LOW | `chart` | Legends, Tooltips, Accessible colors | Relying on color alone to convey meaning |\n\n## Quick Reference\n\n### 1. Accessibility (CRITICAL)\n\n- `color-contrast` - Minimum 4.5:1 ratio for normal text (large text 3:1); Material Design\n- `focus-states` - Visible focus rings on interactive elements (2–4px; Apple HIG, MD)\n- `alt-text` - Descriptive alt text for meaningful images\n- `aria-labels` - aria-label for icon-only buttons; accessibilityLabel in native (Apple HIG)\n- `keyboard-nav` - Tab order matches visual order; full keyboard support (Apple HIG)\n- `form-labels` - Use label with for attribute\n- `skip-links` - Skip to main content for keyboard users\n- `heading-hierarchy` - Sequential h1→h6, no level skip\n- `color-not-only` - Don't convey info by color alone (add icon\u002Ftext)\n- `dynamic-type` - Support system text scaling; avoid truncation as text grows (Apple Dynamic Type, MD)\n- `reduced-motion` - Respect prefers-reduced-motion; reduce\u002Fdisable animations when requested (Apple Reduced Motion API, MD)\n- `voiceover-sr` - Meaningful accessibilityLabel\u002FaccessibilityHint; logical reading order for VoiceOver\u002Fscreen readers (Apple HIG, MD)\n- `escape-routes` - Provide cancel\u002Fback in modals and multi-step flows (Apple HIG)\n- `keyboard-shortcuts` - Preserve system and a11y shortcuts; offer keyboard alternatives for drag-and-drop (Apple HIG)\n\n### 2. Touch & Interaction (CRITICAL)\n\n- `touch-target-size` - Min 44×44pt (Apple) \u002F 48×48dp (Material); extend hit area beyond visual bounds if needed\n- `touch-spacing` - Minimum 8px\u002F8dp gap between touch targets (Apple HIG, MD)\n- `hover-vs-tap` - Use click\u002Ftap for primary interactions; don't rely on hover alone\n- `loading-buttons` - Disable button during async operations; show spinner or progress\n- `error-feedback` - Clear error messages near problem\n- `cursor-pointer` - Add cursor-pointer to clickable elements (Web)\n- `gesture-conflicts` - Avoid horizontal swipe on main content; prefer vertical scroll\n- `tap-delay` - Use touch-action: manipulation to reduce 300ms delay (Web)\n- `standard-gestures` - Use platform standard gestures consistently; don't redefine (e.g. swipe-back, pinch-zoom) (Apple HIG)\n- `system-gestures` - Don't block system gestures (Control Center, back swipe, etc.) (Apple HIG)\n- `press-feedback` - Visual feedback on press (ripple\u002Fhighlight; MD state layers)\n- `haptic-feedback` - Use haptic for confirmations and important actions; avoid overuse (Apple HIG)\n- `gesture-alternative` - Don't rely on gesture-only interactions; always provide visible controls for critical actions\n- `safe-area-awareness` - Keep primary touch targets away from notch, Dynamic Island, gesture bar and screen edges\n- `no-precision-required` - Avoid requiring pixel-perfect taps on small icons or thin edges\n- `swipe-clarity` - Swipe actions must show clear affordance or hint (chevron, label, tutorial)\n- `drag-threshold` - Use a movement threshold before starting drag to avoid accidental drags\n\n### 3. Performance (HIGH)\n\n- `image-optimization` - Use WebP\u002FAVIF, responsive images (srcset\u002Fsizes), lazy load non-critical assets\n- `image-dimension` - Declare width\u002Fheight or use aspect-ratio to prevent layout shift (Core Web Vitals: CLS)\n- `font-loading` - Use font-display: swap\u002Foptional to avoid invisible text (FOIT); reserve space to reduce layout shift (MD)\n- `font-preload` - Preload only critical fonts; avoid overusing preload on every variant\n- `critical-css` - Prioritize above-the-fold CSS (inline critical CSS or early-loaded stylesheet)\n- `lazy-loading` - Lazy load non-hero components via dynamic import \u002F route-level splitting\n- `bundle-splitting` - Split code by route\u002Ffeature (React Suspense \u002F Next.js dynamic) to reduce initial load and TTI\n- `third-party-scripts` - Load third-party scripts async\u002Fdefer; audit and remove unnecessary ones (MD)\n- `reduce-reflows` - Avoid frequent layout reads\u002Fwrites; batch DOM reads then writes\n- `content-jumping` - Reserve space for async content to avoid layout jumps (Core Web Vitals: CLS)\n- `lazy-load-below-fold` - Use loading=\"lazy\" for below-the-fold images and heavy media\n- `virtualize-lists` - Virtualize lists with 50+ items to improve memory efficiency and scroll performance\n- `main-thread-budget` - Keep per-frame work under ~16ms for 60fps; move heavy tasks off main thread (HIG, MD)\n- `progressive-loading` - Use skeleton screens \u002F shimmer instead of long blocking spinners for >1s operations (Apple HIG)\n- `input-latency` - Keep input latency under ~100ms for taps\u002Fscrolls (Material responsiveness standard)\n- `tap-feedback-speed` - Provide visual feedback within 100ms of tap (Apple HIG)\n- `debounce-throttle` - Use debounce\u002Fthrottle for high-frequency events (scroll, resize, input)\n- `offline-support` - Provide offline state messaging and basic fallback (PWA \u002F mobile)\n- `network-fallback` - Offer degraded modes for slow networks (lower-res images, fewer animations)\n\n### 4. Style Selection (HIGH)\n\n- `style-match` - Match style to product type (use `--design-system` for recommendations)\n- `consistency` - Use same style across all pages\n- `no-emoji-icons` - Use SVG icons (Heroicons, Lucide), not emojis\n- `color-palette-from-product` - Choose palette from product\u002Findustry (search `--domain color`)\n- `effects-match-style` - Shadows, blur, radius aligned with chosen style (glass \u002F flat \u002F clay etc.)\n- `platform-adaptive` - Respect platform idioms (iOS HIG vs Material): navigation, controls, typography, motion\n- `state-clarity` - Make hover\u002Fpressed\u002Fdisabled states visually distinct while staying on-style (Material state layers)\n- `elevation-consistent` - Use a consistent elevation\u002Fshadow scale for cards, sheets, modals; avoid random shadow values\n- `dark-mode-pairing` - Design light\u002Fdark variants together to keep brand, contrast, and style consistent\n- `icon-style-consistent` - Use one icon set\u002Fvisual language (stroke width, corner radius) across the product\n- `system-controls` - Prefer native\u002Fsystem controls over fully custom ones; only customize when branding requires it (Apple HIG)\n- `blur-purpose` - Use blur to indicate background dismissal (modals, sheets), not as decoration (Apple HIG)\n- `primary-action` - Each screen should have only one primary CTA; secondary actions visually subordinate (Apple HIG)\n\n### 5. Layout & Responsive (HIGH)\n\n- `viewport-meta` - width=device-width initial-scale=1 (never disable zoom)\n- `mobile-first` - Design mobile-first, then scale up to tablet and desktop\n- `breakpoint-consistency` - Use systematic breakpoints (e.g. 375 \u002F 768 \u002F 1024 \u002F 1440)\n- `readable-font-size` - Minimum 16px body text on mobile (avoids iOS auto-zoom)\n- `line-length-control` - Mobile 35–60 chars per line; desktop 60–75 chars\n- `horizontal-scroll` - No horizontal scroll on mobile; ensure content fits viewport width\n- `spacing-scale` - Use 4pt\u002F8dp incremental spacing system (Material Design)\n- `touch-density` - Keep component spacing comfortable for touch: not cramped, not causing mis-taps\n- `container-width` - Consistent max-width on desktop (max-w-6xl \u002F 7xl)\n- `z-index-management` - Define layered z-index scale (e.g. 0 \u002F 10 \u002F 20 \u002F 40 \u002F 100 \u002F 1000)\n- `fixed-element-offset` - Fixed navbar\u002Fbottom bar must reserve safe padding for underlying content\n- `scroll-behavior` - Avoid nested scroll regions that interfere with the main scroll experience\n- `viewport-units` - Prefer min-h-dvh over 100vh on mobile\n- `orientation-support` - Keep layout readable and operable in landscape mode\n- `content-priority` - Show core content first on mobile; fold or hide secondary content\n- `visual-hierarchy` - Establish hierarchy via size, spacing, contrast — not color alone\n\n### 6. Typography & Color (MEDIUM)\n\n- `line-height` - Use 1.5-1.75 for body text\n- `line-length` - Limit to 65-75 characters per line\n- `font-pairing` - Match heading\u002Fbody font personalities\n- `font-scale` - Consistent type scale (e.g. 12 14 16 18 24 32)\n- `contrast-readability` - Darker text on light backgrounds (e.g. slate-900 on white)\n- `text-styles-system` - Use platform type system: iOS 11 Dynamic Type styles \u002F Material 5 type roles (display, headline, title, body, label) (HIG, MD)\n- `weight-hierarchy` - Use font-weight to reinforce hierarchy: Bold headings (600–700), Regular body (400), Medium labels (500) (MD)\n- `color-semantic` - Define semantic color tokens (primary, secondary, error, surface, on-surface) not raw hex in components (Material color system)\n- `color-dark-mode` - Dark mode uses desaturated \u002F lighter tonal variants, not inverted colors; test contrast separately (HIG, MD)\n- `color-accessible-pairs` - Foreground\u002Fbackground pairs must meet 4.5:1 (AA) or 7:1 (AAA); use tools to verify (WCAG, MD)\n- `color-not-decorative-only` - Functional color (error red, success green) must include icon\u002Ftext; avoid color-only meaning (HIG, MD)\n- `truncation-strategy` - Prefer wrapping over truncation; when truncating use ellipsis and provide full text via tooltip\u002Fexpand (Apple HIG)\n- `letter-spacing` - Respect default letter-spacing per platform; avoid tight tracking on body text (HIG, MD)\n- `number-tabular` - Use tabular\u002Fmonospaced figures for data columns, prices, and timers to prevent layout shift\n- `whitespace-balance` - Use whitespace intentionally to group related items and separate sections; avoid visual clutter (Apple HIG)\n\n### 7. Animation (MEDIUM)\n\n- `duration-timing` - Use 150–300ms for micro-interactions; complex transitions ≤400ms; avoid >500ms (MD)\n- `transform-performance` - Use transform\u002Fopacity only; avoid animating width\u002Fheight\u002Ftop\u002Fleft\n- `loading-states` - Show skeleton or progress indicator when loading exceeds 300ms\n- `excessive-motion` - Animate 1-2 key elements per view max\n- `easing` - Use ease-out for entering, ease-in for exiting; avoid linear for UI transitions\n- `motion-meaning` - Every animation must express a cause-effect relationship, not just be decorative (Apple HIG)\n- `state-transition` - State changes (hover \u002F active \u002F expanded \u002F collapsed \u002F modal) should animate smoothly, not snap\n- `continuity` - Page\u002Fscreen transitions should maintain spatial continuity (shared element, directional slide) (Apple HIG)\n- `parallax-subtle` - Use parallax sparingly; must respect reduced-motion and not cause disorientation (Apple HIG)\n- `spring-physics` - Prefer spring\u002Fphysics-based curves over linear or cubic-bezier for natural feel (Apple HIG fluid animations)\n- `exit-faster-than-enter` - Exit animations shorter than enter (~60–70% of enter duration) to feel responsive (MD motion)\n- `stagger-sequence` - Stagger list\u002Fgrid item entrance by 30–50ms per item; avoid all-at-once or too-slow reveals (MD)\n- `shared-element-transition` - Use shared element \u002F hero transitions for visual continuity between screens (MD, HIG)\n- `interruptible` - Animations must be interruptible; user tap\u002Fgesture cancels in-progress animation immediately (Apple HIG)\n- `no-blocking-animation` - Never block user input during an animation; UI must stay interactive (Apple HIG)\n- `fade-crossfade` - Use crossfade for content replacement within the same container (MD)\n- `scale-feedback` - Subtle scale (0.95–1.05) on press for tappable cards\u002Fbuttons; restore on release (HIG, MD)\n- `gesture-feedback` - Drag, swipe, and pinch must provide real-time visual response tracking the finger (MD Motion)\n- `hierarchy-motion` - Use translate\u002Fscale direction to express hierarchy: enter from below = deeper, exit upward = back (MD)\n- `motion-consistency` - Unify duration\u002Feasing tokens globally; all animations share the same rhythm and feel\n- `opacity-threshold` - Fading elements should not linger below opacity 0.2; either fade fully or remain visible\n- `modal-motion` - Modals\u002Fsheets should animate from their trigger source (scale+fade or slide-in) for spatial context (HIG, MD)\n- `navigation-direction` - Forward navigation animates left\u002Fup; backward animates right\u002Fdown — keep direction logically consistent (HIG)\n- `layout-shift-avoid` - Animations must not cause layout reflow or CLS; use transform for position changes\n\n### 8. Forms & Feedback (MEDIUM)\n\n- `input-labels` - Visible label per input (not placeholder-only)\n- `error-placement` - Show error below the related field\n- `submit-feedback` - Loading then success\u002Ferror state on submit\n- `required-indicators` - Mark required fields (e.g. asterisk)\n- `empty-states` - Helpful message and action when no content\n- `toast-dismiss` - Auto-dismiss toasts in 3-5s\n- `confirmation-dialogs` - Confirm before destructive actions\n- `input-helper-text` - Provide persistent helper text below complex inputs, not just placeholder (Material Design)\n- `disabled-states` - Disabled elements use reduced opacity (0.38–0.5) + cursor change + semantic attribute (MD)\n- `progressive-disclosure` - Reveal complex options progressively; don't overwhelm users upfront (Apple HIG)\n- `inline-validation` - Validate on blur (not keystroke); show error only after user finishes input (MD)\n- `input-type-keyboard` - Use semantic input types (email, tel, number) to trigger the correct mobile keyboard (HIG, MD)\n- `password-toggle` - Provide show\u002Fhide toggle for password fields (MD)\n- `autofill-support` - Use autocomplete \u002F textContentType attributes so the system can autofill (HIG, MD)\n- `undo-support` - Allow undo for destructive or bulk actions (e.g. \"Undo delete\" toast) (Apple HIG)\n- `success-feedback` - Confirm completed actions with brief visual feedback (checkmark, toast, color flash) (MD)\n- `error-recovery` - Error messages must include a clear recovery path (retry, edit, help link) (HIG, MD)\n- `multi-step-progress` - Multi-step flows show step indicator or progress bar; allow back navigation (MD)\n- `form-autosave` - Long forms should auto-save drafts to prevent data loss on accidental dismissal (Apple HIG)\n- `sheet-dismiss-confirm` - Confirm before dismissing a sheet\u002Fmodal with unsaved changes (Apple HIG)\n- `error-clarity` - Error messages must state cause + how to fix (not just \"Invalid input\") (HIG, MD)\n- `field-grouping` - Group related fields logically (fieldset\u002Flegend or visual grouping) (MD)\n- `read-only-distinction` - Read-only state should be visually and semantically different from disabled (MD)\n- `focus-management` - After submit error, auto-focus the first invalid field (WCAG, MD)\n- `error-summary` - For multiple errors, show summary at top with anchor links to each field (WCAG)\n- `touch-friendly-input` - Mobile input height ≥44px to meet touch target requirements (Apple HIG)\n- `destructive-emphasis` - Destructive actions use semantic danger color (red) and are visually separated from primary actions (HIG, MD)\n- `toast-accessibility` - Toasts must not steal focus; use aria-live=\"polite\" for screen reader announcement (WCAG)\n- `aria-live-errors` - Form errors use aria-live region or role=\"alert\" to notify screen readers (WCAG)\n- `contrast-feedback` - Error and success state colors must meet 4.5:1 contrast ratio (WCAG, MD)\n- `timeout-feedback` - Request timeout must show clear feedback with retry option (MD)\n\n### 9. Navigation Patterns (HIGH)\n\n- `bottom-nav-limit` - Bottom navigation max 5 items; use labels with icons (Material Design)\n- `drawer-usage` - Use drawer\u002Fsidebar for secondary navigation, not primary actions (Material Design)\n- `back-behavior` - Back navigation must be predictable and consistent; preserve scroll\u002Fstate (Apple HIG, MD)\n- `deep-linking` - All key screens must be reachable via deep link \u002F URL for sharing and notifications (Apple HIG, MD)\n- `tab-bar-ios` - iOS: use bottom Tab Bar for top-level navigation (Apple HIG)\n- `top-app-bar-android` - Android: use Top App Bar with navigation icon for primary structure (Material Design)\n- `nav-label-icon` - Navigation items must have both icon and text label; icon-only nav harms discoverability (MD)\n- `nav-state-active` - Current location must be visually highlighted (color, weight, indicator) in navigation (HIG, MD)\n- `nav-hierarchy` - Primary nav (tabs\u002Fbottom bar) vs secondary nav (drawer\u002Fsettings) must be clearly separated (MD)\n- `modal-escape` - Modals and sheets must offer a clear close\u002Fdismiss affordance; swipe-down to dismiss on mobile (Apple HIG)\n- `search-accessible` - Search must be easily reachable (top bar or tab); provide recent\u002Fsuggested queries (MD)\n- `breadcrumb-web` - Web: use breadcrumbs for 3+ level deep hierarchies to aid orientation (MD)\n- `state-preservation` - Navigating back must restore previous scroll position, filter state, and input (HIG, MD)\n- `gesture-nav-support` - Support system gesture navigation (iOS swipe-back, Android predictive back) without conflict (HIG, MD)\n- `tab-badge` - Use badges on nav items sparingly to indicate unread\u002Fpending; clear after user visits (HIG, MD)\n- `overflow-menu` - When actions exceed available space, use overflow\u002Fmore menu instead of cramming (MD)\n- `bottom-nav-top-level` - Bottom nav is for top-level screens only; never nest sub-navigation inside it (MD)\n- `adaptive-navigation` - Large screens (≥1024px) prefer sidebar; small screens use bottom\u002Ftop nav (Material Adaptive)\n- `back-stack-integrity` - Never silently reset the navigation stack or unexpectedly jump to home (HIG, MD)\n- `navigation-consistency` - Navigation placement must stay the same across all pages; don't change by page type\n- `avoid-mixed-patterns` - Don't mix Tab + Sidebar + Bottom Nav at the same hierarchy level\n- `modal-vs-navigation` - Modals must not be used for primary navigation flows; they break the user's path (HIG)\n- `focus-on-route-change` - After page transition, move focus to main content region for screen reader users (WCAG)\n- `persistent-nav` - Core navigation must remain reachable from deep pages; don't hide it entirely in sub-flows (HIG, MD)\n- `destructive-nav-separation` - Dangerous actions (delete account, logout) must be visually and spatially separated from normal nav items (HIG, MD)\n- `empty-nav-state` - When a nav destination is unavailable, explain why instead of silently hiding it (MD)\n\n### 10. Charts & Data (LOW)\n\n- `chart-type` - Match chart type to data type (trend → line, comparison → bar, proportion → pie\u002Fdonut)\n- `color-guidance` - Use accessible color palettes; avoid red\u002Fgreen only pairs for colorblind users (WCAG, MD)\n- `data-table` - Provide table alternative for accessibility; charts alone are not screen-reader friendly (WCAG)\n- `pattern-texture` - Supplement color with patterns, textures, or shapes so data is distinguishable without color (WCAG, MD)\n- `legend-visible` - Always show legend; position near the chart, not detached below a scroll fold (MD)\n- `tooltip-on-interact` - Provide tooltips\u002Fdata labels on hover (Web) or tap (mobile) showing exact values (HIG, MD)\n- `axis-labels` - Label axes with units and readable scale; avoid truncated or rotated labels on mobile\n- `responsive-chart` - Charts must reflow or simplify on small screens (e.g. horizontal bar instead of vertical, fewer ticks)\n- `empty-data-state` - Show meaningful empty state when no data exists (\"No data yet\" + guidance), not a blank chart (MD)\n- `loading-chart` - Use skeleton or shimmer placeholder while chart data loads; don't show an empty axis frame\n- `animation-optional` - Chart entrance animations must respect prefers-reduced-motion; data should be readable immediately (HIG)\n- `large-dataset` - For 1000+ data points, aggregate or sample; provide drill-down for detail instead of rendering all (MD)\n- `number-formatting` - Use locale-aware formatting for numbers, dates, currencies on axes and labels (HIG, MD)\n- `touch-target-chart` - Interactive chart elements (points, segments) must have ≥44pt tap area or expand on touch (Apple HIG)\n- `no-pie-overuse` - Avoid pie\u002Fdonut for >5 categories; switch to bar chart for clarity\n- `contrast-data` - Data lines\u002Fbars vs background ≥3:1; data text labels ≥4.5:1 (WCAG)\n- `legend-interactive` - Legends should be clickable to toggle series visibility (MD)\n- `direct-labeling` - For small datasets, label values directly on the chart to reduce eye travel\n- `tooltip-keyboard` - Tooltip content must be keyboard-reachable and not rely on hover alone (WCAG)\n- `sortable-table` - Data tables must support sorting with aria-sort indicating current sort state (WCAG)\n- `axis-readability` - Axis ticks must not be cramped; maintain readable spacing, auto-skip on small screens\n- `data-density` - Limit information density per chart to avoid cognitive overload; split into multiple charts if needed\n- `trend-emphasis` - Emphasize data trends over decoration; avoid heavy gradients\u002Fshadows that obscure the data\n- `gridline-subtle` - Grid lines should be low-contrast (e.g. gray-200) so they don't compete with data\n- `focusable-elements` - Interactive chart elements (points, bars, slices) must be keyboard-navigable (WCAG)\n- `screen-reader-summary` - Provide a text summary or aria-label describing the chart's key insight for screen readers (WCAG)\n- `error-state-chart` - Data load failure must show error message with retry action, not a broken\u002Fempty chart\n- `export-option` - For data-heavy products, offer CSV\u002Fimage export of chart data\n- `drill-down-consistency` - Drill-down interactions must maintain a clear back-path and hierarchy breadcrumb\n- `time-scale-clarity` - Time series charts must clearly label time granularity (day\u002Fweek\u002Fmonth) and allow switching\n\n## How to Use\n\nSearch specific domains using the CLI tool below.\n\n---\n\n## Prerequisites\n\nCheck if Python is installed:\n\n```bash\npython3 --version || python --version\n```\n\nIf Python is not installed, install it based on user's OS:\n\n**macOS:**\n```bash\nbrew install python3\n```\n\n**Ubuntu\u002FDebian:**\n```bash\nsudo apt update && sudo apt install python3\n```\n\n**Windows:**\n```powershell\nwinget install Python.Python.3.12\n```\n\n---\n\n## How to Use This Skill\n\nUse this skill when the user requests any of the following:\n\n| Scenario | Trigger Examples | Start From |\n|----------|-----------------|------------|\n| **New project \u002F page** | \"Build a landing page\", \"Build a dashboard\" | Step 1 → Step 2 (design system) |\n| **New component** | \"Create a pricing card\", \"Add a modal\" | Step 3 (domain search: style, ux) |\n| **Choose style \u002F color \u002F font** | \"What style fits a fintech app?\", \"Recommend a color palette\" | Step 2 (design system) |\n| **Review existing UI** | \"Review this page for UX issues\", \"Check accessibility\" | Quick Reference checklist above |\n| **Fix a UI bug** | \"Button hover is broken\", \"Layout shifts on load\" | Quick Reference → relevant section |\n| **Improve \u002F optimize** | \"Make this faster\", \"Improve mobile experience\" | Step 3 (domain search: ux, react) |\n| **Implement dark mode** | \"Add dark mode support\" | Step 3 (domain: style \"dark mode\") |\n| **Add charts \u002F data viz** | \"Add an analytics dashboard chart\" | Step 3 (domain: chart) |\n| **Stack best practices** | \"React performance tips\"、\"SwiftUI navigation\" | Step 4 (stack search) |\n\nFollow this workflow:\n\n### Step 1: Analyze User Requirements\n\nExtract key information from user request:\n- **Product type**: Entertainment (social, video, music, gaming), Tool (scanner, editor, converter), Productivity (task manager, notes, calendar), or hybrid\n- **Target audience**: C-end consumer users; consider age group, usage context (commute, leisure, work)\n- **Style keywords**: playful, vibrant, minimal, dark mode, content-first, immersive, etc.\n- **Stack**: React Native (this project's only tech stack)\n\n### Step 2: Generate Design System (REQUIRED)\n\n**Always start with `--design-system`** to get comprehensive recommendations with reasoning:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cproduct_type> \u003Cindustry> \u003Ckeywords>\" --design-system [-p \"Project Name\"]\n```\n\nThis command:\n1. Searches domains in parallel (product, style, color, landing, typography)\n2. Applies reasoning rules from `ui-reasoning.csv` to select best matches\n3. Returns complete design system: pattern, style, colors, typography, effects\n4. Includes anti-patterns to avoid\n\n**Example:**\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"beauty spa wellness service\" --design-system -p \"Serenity Spa\"\n```\n\n### Step 2b: Persist Design System (Master + Overrides Pattern)\n\nTo save the design system for **hierarchical retrieval across sessions**, add `--persist`:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cquery>\" --design-system --persist -p \"Project Name\"\n```\n\nThis creates:\n- `design-system\u002FMASTER.md` — Global Source of Truth with all design rules\n- `design-system\u002Fpages\u002F` — Folder for page-specific overrides\n\n**With page-specific override:**\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Cquery>\" --design-system --persist -p \"Project Name\" --page \"dashboard\"\n```\n\nThis also creates:\n- `design-system\u002Fpages\u002Fdashboard.md` — Page-specific deviations from Master\n\n**How hierarchical retrieval works:**\n1. When building a specific page (e.g., \"Checkout\"), first check `design-system\u002Fpages\u002Fcheckout.md`\n2. If the page file exists, its rules **override** the Master file\n3. If not, use `design-system\u002FMASTER.md` exclusively\n\n**Context-aware retrieval prompt:**\n```\nI am building the [Page Name] page. Please read design-system\u002FMASTER.md.\nAlso check if design-system\u002Fpages\u002F[page-name].md exists.\nIf the page file exists, prioritize its rules.\nIf not, use the Master rules exclusively.\nNow, generate the code...\n```\n\n### Step 3: Supplement with Detailed Searches (as needed)\n\nAfter getting the design system, use domain searches to get additional details:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Ckeyword>\" --domain \u003Cdomain> [-n \u003Cmax_results>]\n```\n\n**When to use detailed searches:**\n\n| Need | Domain | Example |\n|------|--------|---------|\n| Product type patterns | `product` | `--domain product \"entertainment social\"` |\n| More style options | `style` | `--domain style \"glassmorphism dark\"` |\n| Color palettes | `color` | `--domain color \"entertainment vibrant\"` |\n| Font pairings | `typography` | `--domain typography \"playful modern\"` |\n| Chart recommendations | `chart` | `--domain chart \"real-time dashboard\"` |\n| UX best practices | `ux` | `--domain ux \"animation accessibility\"` |\n| Alternative fonts | `typography` | `--domain typography \"elegant luxury\"` |\n| Individual Google Fonts | `google-fonts` | `--domain google-fonts \"sans serif popular variable\"` |\n| Landing structure | `landing` | `--domain landing \"hero social-proof\"` |\n| React Native perf | `react` | `--domain react \"rerender memo list\"` |\n| App interface a11y | `web` | `--domain web \"accessibilityLabel touch safe-areas\"` |\n| AI prompt \u002F CSS keywords | `prompt` | `--domain prompt \"minimalism\"` |\n\n### Step 4: Stack Guidelines (React Native)\n\nGet React Native implementation-specific best practices:\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"\u003Ckeyword>\" --stack react-native\n```\n\n---\n\n## Search Reference\n\n### Available Domains\n\n| Domain | Use For | Example Keywords |\n|--------|---------|------------------|\n| `product` | Product type recommendations | SaaS, e-commerce, portfolio, healthcare, beauty, service |\n| `style` | UI styles, colors, effects | glassmorphism, minimalism, dark mode, brutalism |\n| `typography` | Font pairings, Google Fonts | elegant, playful, professional, modern |\n| `color` | Color palettes by product type | saas, ecommerce, healthcare, beauty, fintech, service |\n| `landing` | Page structure, CTA strategies | hero, hero-centric, testimonial, pricing, social-proof |\n| `chart` | Chart types, library recommendations | trend, comparison, timeline, funnel, pie |\n| `ux` | Best practices, anti-patterns | animation, accessibility, z-index, loading |\n| `google-fonts` | Individual Google Fonts lookup | sans serif, monospace, japanese, variable font, popular |\n| `react` | React\u002FNext.js performance | waterfall, bundle, suspense, memo, rerender, cache |\n| `web` | App interface guidelines (iOS\u002FAndroid\u002FReact Native) | accessibilityLabel, touch targets, safe areas, Dynamic Type |\n| `prompt` | AI prompts, CSS keywords | (style name) |\n\n### Available Stacks\n\n| Stack | Focus |\n|-------|-------|\n| `react-native` | Components, Navigation, Lists |\n\n---\n\n## Example Workflow\n\n**User request:** \"Make an AI search homepage.\"\n\n### Step 1: Analyze Requirements\n- Product type: Tool (AI search engine)\n- Target audience: C-end users looking for fast, intelligent search\n- Style keywords: modern, minimal, content-first, dark mode\n- Stack: React Native\n\n### Step 2: Generate Design System (REQUIRED)\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"AI search tool modern minimal\" --design-system -p \"AI Search\"\n```\n\n**Output:** Complete design system with pattern, style, colors, typography, effects, and anti-patterns.\n\n### Step 3: Supplement with Detailed Searches (as needed)\n\n```bash\n# Get style options for a modern tool product\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"minimalism dark mode\" --domain style\n\n# Get UX best practices for search interaction and loading\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"search loading animation\" --domain ux\n```\n\n### Step 4: Stack Guidelines\n\n```bash\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"list performance navigation\" --stack react-native\n```\n\n**Then:** Synthesize design system + detailed searches and implement the design.\n\n---\n\n## Output Formats\n\nThe `--design-system` flag supports two output formats:\n\n```bash\n# ASCII box (default) - best for terminal display\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"fintech crypto\" --design-system\n\n# Markdown - best for documentation\npython3 skills\u002Fui-ux-pro-max\u002Fscripts\u002Fsearch.py \"fintech crypto\" --design-system -f markdown\n```\n\n---\n\n## Tips for Better Results\n\n### Query Strategy\n\n- Use **multi-dimensional keywords** — combine product + industry + tone + density: `\"entertainment social vibrant content-dense\"` not just `\"app\"`\n- Try different keywords for the same need: `\"playful neon\"` → `\"vibrant dark\"` → `\"content-first minimal\"`\n- Use `--design-system` first for full recommendations, then `--domain` to deep-dive any dimension you're unsure about\n- Always add `--stack react-native` for implementation-specific guidance\n\n### Common Sticking Points\n\n| Problem | What to Do |\n|---------|------------|\n| Can't decide on style\u002Fcolor | Re-run `--design-system` with different keywords |\n| Dark mode contrast issues | Quick Reference §6: `color-dark-mode` + `color-accessible-pairs` |\n| Animations feel unnatural | Quick Reference §7: `spring-physics` + `easing` + `exit-faster-than-enter` |\n| Form UX is poor | Quick Reference §8: `inline-validation` + `error-clarity` + `focus-management` |\n| Navigation feels confusing | Quick Reference §9: `nav-hierarchy` + `bottom-nav-limit` + `back-behavior` |\n| Layout breaks on small screens | Quick Reference §5: `mobile-first` + `breakpoint-consistency` |\n| Performance \u002F jank | Quick Reference §3: `virtualize-lists` + `main-thread-budget` + `debounce-throttle` |\n\n### Pre-Delivery Checklist\n\n- Run `--domain ux \"animation accessibility z-index loading\"` as a UX validation pass before implementation\n- Run through Quick Reference **§1–§3** (CRITICAL + HIGH) as a final review\n- Test on 375px (small phone) and landscape orientation\n- Verify behavior with **reduced-motion** enabled and **Dynamic Type** at largest size\n- Check dark mode contrast independently (don't assume light mode values work)\n- Confirm all touch targets ≥44pt and no content hidden behind safe areas\n\n---\n\n## Common Rules for Professional UI\n\nThese are frequently overlooked issues that make UI look unprofessional:\nScope notice: The rules below are for App UI (iOS\u002FAndroid\u002FReact Native\u002FFlutter), not desktop-web interaction patterns.\n\n### Icons & Visual Elements\n\n| Rule | Standard | Avoid | Why It Matters |\n|------|----------|--------|----------------|\n| **No Emoji as Structural Icons** | Use vector-based icons (e.g., Lucide, react-native-vector-icons, @expo\u002Fvector-icons). | Using emojis (? ? ⚙️) for navigation, settings, or system controls. | Emojis are font-dependent, inconsistent across platforms, and cannot be controlled via design tokens. |\n| **Vector-Only Assets** | Use SVG or platform vector icons that scale cleanly and support theming. | Raster PNG icons that blur or pixelate. | Ensures scalability, crisp rendering, and dark\u002Flight mode adaptability. |\n| **Stable Interaction States** | Use color, opacity, or elevation transitions for press states without changing layout bounds. | Layout-shifting transforms that move surrounding content or trigger visual jitter. | Prevents unstable interactions and preserves smooth motion\u002Fperceived quality on mobile. |\n| **Correct Brand Logos** | Use official brand assets and follow their usage guidelines (spacing, color, clear space). | Guessing logo paths, recoloring unofficially, or modifying proportions. | Prevents brand misuse and ensures legal\u002Fplatform compliance. |\n| **Consistent Icon Sizing** | Define icon sizes as design tokens (e.g., icon-sm, icon-md = 24pt, icon-lg). | Mixing arbitrary values like 20pt \u002F 24pt \u002F 28pt randomly. | Maintains rhythm and visual hierarchy across the interface. |\n| **Stroke Consistency** | Use a consistent stroke width within the same visual layer (e.g., 1.5px or 2px). | Mixing thick and thin stroke styles arbitrarily. | Inconsistent strokes reduce perceived polish and cohesion. |\n| **Filled vs Outline Discipline** | Use one icon style per hierarchy level. | Mixing filled and outline icons at the same hierarchy level. | Maintains semantic clarity and stylistic coherence. |\n| **Touch Target Minimum** | Minimum 44×44pt interactive area (use hitSlop if icon is smaller). | Small icons without expanded tap area. | Meets accessibility and platform usability standards. |\n| **Icon Alignment** | Align icons to text baseline and maintain consistent padding. | Misaligned icons or inconsistent spacing around them. | Prevents subtle visual imbalance that reduces perceived quality. |\n| **Icon Contrast** | Follow WCAG contrast standards: 4.5:1 for small elements, 3:1 minimum for larger UI glyphs. | Low-contrast icons that blend into the background. | Ensures accessibility in both light and dark modes. |\n\n\n### Interaction (App)\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Tap feedback** | Provide clear pressed feedback (ripple\u002Fopacity\u002Felevation) within 80-150ms | No visual response on tap |\n| **Animation timing** | Keep micro-interactions around 150-300ms with platform-native easing | Instant transitions or slow animations (>500ms) |\n| **Accessibility focus** | Ensure screen reader focus order matches visual order and labels are descriptive | Unlabeled controls or confusing focus traversal |\n| **Disabled state clarity** | Use disabled semantics (`disabled`\u002Fnative disabled props), reduced emphasis, and no tap action | Controls that look tappable but do nothing |\n| **Touch target minimum** | Keep tap areas >=44x44pt (iOS) or >=48x48dp (Android), expand hit area when icon is smaller | Tiny tap targets or icon-only hit areas without padding |\n| **Gesture conflict prevention** | Keep one primary gesture per region and avoid nested tap\u002Fdrag conflicts | Overlapping gestures causing accidental actions |\n| **Semantic native controls** | Prefer native interactive primitives (`Button`, `Pressable`, platform equivalents) with proper accessibility roles | Generic containers used as primary controls without semantics |\n\n### Light\u002FDark Mode Contrast\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Surface readability (light)** | Keep cards\u002Fsurfaces clearly separated from background with sufficient opacity\u002Felevation | Overly transparent surfaces that blur hierarchy |\n| **Text contrast (light)** | Maintain body text contrast >=4.5:1 against light surfaces | Low-contrast gray body text |\n| **Text contrast (dark)** | Maintain primary text contrast >=4.5:1 and secondary text >=3:1 on dark surfaces | Dark mode text that blends into background |\n| **Border and divider visibility** | Ensure separators are visible in both themes (not just light mode) | Theme-specific borders disappearing in one mode |\n| **State contrast parity** | Keep pressed\u002Ffocused\u002Fdisabled states equally distinguishable in light and dark themes | Defining interaction states for one theme only |\n| **Token-driven theming** | Use semantic color tokens mapped per theme across app surfaces\u002Ftext\u002Ficons | Hardcoded per-screen hex values |\n| **Scrim and modal legibility** | Use a modal scrim strong enough to isolate foreground content (typically 40-60% black) | Weak scrim that leaves background visually competing |\n\n### Layout & Spacing\n\n| Rule | Do | Don't |\n|------|----|----- |\n| **Safe-area compliance** | Respect top\u002Fbottom safe areas for all fixed headers, tab bars, and CTA bars | Placing fixed UI under notch, status bar, or gesture area |\n| **System bar clearance** | Add spacing for status\u002Fnavigation bars and gesture home indicator | Let tappable content collide with OS chrome |\n| **Consistent content width** | Keep predictable content width per device class (phone\u002Ftablet) | Mixing arbitrary widths between screens |\n| **8dp spacing rhythm** | Use a consistent 4\u002F8dp spacing system for padding\u002Fgaps\u002Fsection spacing | Random spacing increments with no rhythm |\n| **Readable text measure** | Keep long-form text readable on large devices (avoid edge-to-edge paragraphs on tablets) | Full-width long text that hurts readability |\n| **Section spacing hierarchy** | Define clear vertical rhythm tiers (e.g., 16\u002F24\u002F32\u002F48) by hierarchy | Similar UI levels with inconsistent spacing |\n| **Adaptive gutters by breakpoint** | Increase horizontal insets on larger widths and in landscape | Same narrow gutter on all device sizes\u002Forientations |\n| **Scroll and fixed element coexistence** | Add bottom\u002Ftop content insets so lists are not hidden behind fixed bars | Scroll content obscured by sticky headers\u002Ffooters |\n\n---\n\n## Pre-Delivery Checklist\n\nBefore delivering UI code, verify these items:\nScope notice: This checklist is for App UI (iOS\u002FAndroid\u002FReact Native\u002FFlutter).\n\n### Visual Quality\n- [ ] No emojis used as icons (use SVG instead)\n- [ ] All icons come from a consistent icon family and style\n- [ ] Official brand assets are used with correct proportions and clear space\n- [ ] Pressed-state visuals do not shift layout bounds or cause jitter\n- [ ] Semantic theme tokens are used consistently (no ad-hoc per-screen hardcoded colors)\n\n### Interaction\n- [ ] All tappable elements provide clear pressed feedback (ripple\u002Fopacity\u002Felevation)\n- [ ] Touch targets meet minimum size (>=44x44pt iOS, >=48x48dp Android)\n- [ ] Micro-interaction timing stays in the 150-300ms range with native-feeling easing\n- [ ] Disabled states are visually clear and non-interactive\n- [ ] Screen reader focus order matches visual order, and interactive labels are descriptive\n- [ ] Gesture regions avoid nested\u002Fconflicting interactions (tap\u002Fdrag\u002Fback-swipe conflicts)\n\n### Light\u002FDark Mode\n- [ ] Primary text contrast >=4.5:1 in both light and dark mode\n- [ ] Secondary text contrast >=3:1 in both light and dark mode\n- [ ] Dividers\u002Fborders and interaction states are distinguishable in both modes\n- [ ] Modal\u002Fdrawer scrim opacity is strong enough to preserve foreground legibility (typically 40-60% black)\n- [ ] Both themes are tested before delivery (not inferred from a single theme)\n\n### Layout\n- [ ] Safe areas are respected for headers, tab bars, and bottom CTA bars\n- [ ] Scroll content is not hidden behind fixed\u002Fsticky bars\n- [ ] Verified on small phone, large phone, and tablet (portrait + landscape)\n- [ ] Horizontal insets\u002Fgutters adapt correctly by device size and orientation\n- [ ] 4\u002F8dp spacing rhythm is maintained across component, section, and page levels\n- [ ] Long-form text measure remains readable on larger devices (no edge-to-edge paragraphs)\n\n### Accessibility\n- [ ] All meaningful images\u002Ficons have accessibility labels\n- [ ] Form fields have labels, hints, and clear error messages\n- [ ] Color is not the only indicator\n- [ ] Reduced motion and dynamic text size are supported without layout breakage\n- [ ] Accessibility traits\u002Froles\u002Fstates (selected, disabled, expanded) are announced correctly",{"name":5,"description":7},"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","frontend\u002Fspecialists\u002Fui-ux-pro-max",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill ui-ux-pro-max",{"tool":78,"command":79},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill ui-ux-pro-max",{"tool":81,"command":82},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill ui-ux-pro-max","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Ffrontend\u002Fspecialists\u002Fui-ux-pro-max\u002FSKILL.md",true,[],[87,120,142,163,183,205],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":99,"publishedAt":58},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[93,96],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":97,"categoryName":98,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"writing","writing shape","shape","notes","help","file","markdown","format","session","use","take","draft","article","material","it","about","quotes","at","candidate","when",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":128,"publishedAt":58},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[126,127],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":32,"taxonomyTypeDesc":33},[100,129,130,131,132,133,108,109,134,135,136,112,137,113,138,139,140,141,119],"writing fragments","grilling","ideate","develop","user","document","structure","ideas","as","sharp","claims","for","single",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":58},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[148,149],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":32,"taxonomyTypeDesc":33},[100,151,152,153,109,154,155,102,156,157,158,112,159,137,160,113,161,162,140,119],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":171,"publishedAt":58},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[169,170],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":32,"taxonomyTypeDesc":33},[172,173,174,100,175,176,177,178,179,109,180,181,182,140,119],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":58},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[189,190],{"categoryNo":94,"categoryName":95,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":97,"categoryName":98,"taxonomyType":32,"taxonomyTypeDesc":33},[185,100,192,193,177,194,153,195,196,179,197,198,181,199,200,201,202,203,204,119],"code","em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":211,"publishedAt":58},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[207,212,213,214,215,216,109,217,218,219,220,221,119,222],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]