Design & UI Skills

| Create and modify PowerPoint presentations (PPTX) through direct XML manipulation. (3) Inserting images or custom shapes, (4) Applying POTX templates for consistent branding, (5) Editing existing PPTX files, (6) Working with slide layouts and placeholders, (7) User asks to make a "presentation", "slides", "deck", or mentions ".pptx". Supports all 11 standard Office slide layouts.

Generate production-ready React/Next.js code from Figma designs. Instructs proper Figma MCP tool usage, component reuse strategies, and variant mapping. **CRITICAL: ALWAYS use this skill when user provides a Figma link or mentions implementing/redesigning from Figma design.** Never attempt manual implementation without invoking this skill first.

Consulte sur le système de design d'un produit et produit `docs/DESIGN.md` + un preview HTML (spécimen typo + palette + 1 mockup d'écran). Propose un système cohérent et opinioné (aesthetic, typographie, color, layout, spacing, motion) avec breakdown SAFE/RISK. Utilise sur /design, "crée le design system", "écris DESIGN.md", "design depuis zéro", "système de design", "design consultation", "fais-moi un design system", ou dès qu'il faut formaliser l'identité visuelle d'un projet. Pair naturel de /cadre (PRD amont) et /planifie (plan d'impl aval).

Pull a Korean brand's published design.md from the ko-design-md catalog (getdesign.kr) and apply its design language — colors, typography, spacing, radius, components, do's & don'ts — to the UI you are building in the CURRENT project. Use this skill whenever the user wants to build or restyle UI in the *style of* a catalogued Korean service — phrases like "토스 디자인으로 만들어줘", "당근 스타일로 이 화면 다시 꾸며줘", "getdesign 카탈로그에서 배민 디자인 가져와서 적용", "KRDS 톤으로 폼 잡아줘", "make this look like Toss", "use the Karrot design system here", or "/use-design-md". Works in ANY repository — it fetches over the network, no local catalog needed. Do NOT use this to ADD a brand to the catalog or edit catalog entries — that is the separate `design-md` producer skill, which only runs inside the ko-design-md repo. If the requested brand isn't in the catalog, say so plainly rather than inventing a design.md.

Use when a Hermes session involves UI design, interface craft, Figma, design systems, shadcn/ui, Tailwind, Atomic Design, research synthesis, component specs, design audits, or code generation from design evidence.

Use when a task spans interface understanding, design-system memory, UI audits, design CI, Figma, shadcn or Tailwind code generation, research, or agent design workflows and needs the correct Memi capability selected.

Use when an OpenCode task involves UI design, interface craft, Figma, design systems, shadcn/ui, Tailwind, Atomic Design, research synthesis, component specs, design audits, or design-to-code generation.

Use when an OpenClaw workspace task involves UI design, interface craft, Figma, design systems, shadcn/ui, Tailwind, Atomic Design, research synthesis, design audits, component specs, or code generation from design evidence.

Use when reviewing or changing a React, Next.js, Tailwind, or shadcn interface and you need evidence-backed findings for accessibility, hierarchy, tokens, states, and responsive design before editing code.

Use when a Grok Build task involves UI design, interface understanding, Figma, design systems, shadcn/ui, Tailwind, UX audits, Atomic Design, component specs, MCP, or design-to-code generation.

Use when a repository needs deterministic pull-request checks for new accessibility, design-token, component-structure, responsive, and UI-state regressions with file-level evidence.

Use when an agent is about to build or refactor interface code and needs a compact, repository-specific brief covering existing tokens, components, routes, conventions, and verification commands.

Use when a coding agent must design, scaffold, implement, or verify an iOS or macOS SwiftUI interface with Apple-platform state, accessibility, availability, testing, and Xcode evidence.

> (Clauses 4-10) and all 93 Annex A controls reorganized into four themes. Auto-invoked when discussing ISO 27001 certification readiness, ISMS implementation, or Statement of Applicability development. Identifies control gaps, scores implementation maturity, and produces a remediation roadmap aligned to the 2022 revision structure.

Build and configure the DevExpress Blazor Ribbon (DxRibbon) — an Office-style tabbed command UI for Blazor. Use when creating ribbon tabs, groups, and items; application menu (File); contextual tabs; toggle/check items and radio groups; and embedding editors like combo boxes, spin edits, and color palettes. Also use for DxRibbon, ribbon UI, Office ribbon, command bar, and ribbon feature comparisons or migration scenarios.

Build and configure the DevExpress Blazor Pivot Table (DxPivotTable) — an interactive pivot grid / cross-tab analysis component for Blazor. Use for pivot-style row/column aggregation (sum/count/avg/min/max), field layout (area/area index), date grouping (year/quarter/month), interactive filtering, and building analytical dashboards. Also use for DxPivotTable, pivot grid, pivot table, cross-tab, OLAP-style analysis, and pivot feature comparisons or migration scenarios.

> Help developers use the DevExtreme Button component (dxButton) in Angular, React, Vue, and jQuery. Use when someone asks about Button configuration, click handling, icons, styling, button types, form submission, validation, custom templates, or any scenario involving dxButton or DxButton. "button icon", "button type", "button styling", "submit form with button", "custom button template".

> Apply, customize, and switch DevExtreme themes (Generic, Material, Fluent). Covers predefined theme CSS import, ThemeBuilder UI and CLI, SCSS variables, custom CSS overrides, color swatches, and runtime theme switching.

Build .NET applications with the DevExpress Presentation API for creating, reading, modifying, and exporting PowerPoint presentations programmatically without Microsoft Office. Use when working with .pptx files, slides, shapes, text, tables, slide masters and layouts, themes, slide backgrounds, notes, headers/footers, or exporting presentations to PDF. Also use when someone mentions "DevExpress Presentation", "Presentation API", "DevExpress.Docs.Presentation", "create PowerPoint in C#", "pptx automation .NET", "merge presentations", or asks about any PowerPoint/presentation processing with DevExpress. Covers .NET.

Expert skill for the DevExpress WinForms AccordionControl (DevExpress.XtraBars.Navigation.AccordionControl, DevExpress.Win.Navigation NuGet). Covers creating and populating accordion menus, data-driven element generation from collections, AccordionControlElement groups and items, content containers with embedded controls, header layout customization via HeaderTemplate, view types (Default accordion vs HamburgerMenu), Hamburger Menu display modes (Inline/Overlay/Minimal), minimize/expand state, Footer root-element mode, built-in and external search/filter panel, AI Smart Search, expand/collapse behavior, animations, appearance and HTML-CSS templates, context buttons, custom drawing, and guidance on choosing between AccordionControl, NavBarControl, and Hamburger Menu style. Use this skill when a user asks about WinForms side navigation, accordion menus, hamburger menus, collapsible navigation bars, AccordionControlElement configuration, NavigationFrame integration, or FluentDesignForm navigation setup.

DevExpress WinForms Data Grid — GridControl with GridView, BandedGridView, AdvBandedGridView, CardView, LayoutView, TileView, and WinExplorerView, plus the TreeList for hierarchical data. Covers data binding (regular, ServerMode, InstantFeedback, VirtualServerModeSource), column generation (PopulateColumns, AddVisible, unbound columns via UnboundExpression, bands, ColumnEdit), cell display and editing (RepositoryItem, CustomRowCellEdit, DisplayFormat, edit forms, OptionsColumn), conditional formatting (FormatRules), validation (ValidateRow, SetColumnError), filtering (Excel-style, Auto Filter Row, Find Panel, ActiveFilterString), sorting and grouping (SortInfo, GroupInterval), master-detail (LevelTree, pattern views), print and export (ExportToXlsx/Pdf), focus and selection (FocusedRow, MultiSelect), drag-and-drop, and layout persistence (SaveLayoutToXml). Use for any WinForms grid, tree-list, or card-view scenario.

DevExpress WinForms Layout Management — form layout and docking controls: LayoutControl (free/flow/table layout modes, groups, tabbed groups, size constraints, runtime customization), DataLayoutControl (data-source-driven auto-generated editor layout, RetrieveFields, DataAnnotations), DockManager with DockPanel (VS-style docking, floating panels, auto-hide, tab groups, DockingStyle, DockAsTab), StackPanel, and TablePanel (Absolute/AutoSize/Relative sizing, RowSpan/ColumnSpan). Covers NuGet (DevExpress.Win.Navigation, DevExpress.Utils), namespaces (DevExpress.XtraLayout, DevExpress.XtraDataLayout, DevExpress.XtraBars.Docking, DevExpress.Utils.Layout), authoring layouts in the *.Designer.cs file (InitializeComponent), building layouts in code (AddItem, AddGroup, AddTabbedGroup), and saving/restoring layouts (SaveLayoutToXml/Json, WorkspaceManager). Use for any WinForms layout, form arrangement, or docking scenario; for a form generated from a table/class use DataLayoutControl.

> AI agent skill for the DevExpress WinForms PivotGridControl. Covers NuGet setup, data binding (DataSourceColumnBinding, ExpressionDataBinding, OLAP), field areas and layout, summaries, grouping, sorting, filtering, conditional formatting (FormatRules), and appearance customization. Use for any DevExpress WinForms PivotGridControl cross-tabular analysis scenario.

DevExpress WinForms Ribbon (RibbonControl) and traditional Bars (BarManager + Bar) — Office-style ribbon UIs or classic main-menu/toolbar/status-bar UIs. Covers the RibbonForm host requirement, the items/links architecture (BarItem and BarItemLink: BarButtonItem, BarCheckItem, BarToggleSwitchItem, BarSubItem, BarEditItem, BarStaticItem, BarLargeButtonItem, RibbonGalleryBarItem), item properties (Caption, ImageOptions.SvgImage, RibbonStyle, ButtonStyle, GroupIndex, ItemShortcut), per-link overrides (UserCaption, BeginGroup, MostRecentlyUsed), appearance (RibbonControl.RibbonStyle Office2007 through OfficeUniversal, SkinManager), MDI ribbon and bars merging (MdiMergeStyle, MergeRibbon, Bar.Merge, MergeType/MergeOrder), bar layout (DockStyle, DockRow, MainMenu, StatusBar), and ribbon structure (RibbonPageCategory, RibbonPage, RibbonPageGroup, Toolbar/QAT, ApplicationMenu or BackstageViewControl, galleries). Use for any WinForms ribbon or bars/toolbar/menu scenario.

Build WPF applications with the DevExpress Chart Control (ChartControl) — 2D bar, line, area, pie, financial, polar, radar, funnel, box plot, point, bubble, and scatter series. Use when adding ChartControl to a WPF project; building XYDiagram2D, SimpleDiagram2D (pie/funnel), PolarDiagram2D, or RadarDiagram2D; binding series via DataSource + ArgumentDataMember/ValueDataMember or Diagram.SeriesItemsSource; configuring axes and scale types (Numerical, DateTime, TimeSpan, Qualitative); aggregating data; styling Legend; configuring tooltips and the Crosshair Cursor; or enabling selection. Also use when someone mentions "DevExpress WPF chart", "dxc:ChartControl", "DevExpress.Xpf.Charts", "AreaSeries2D", "LineSeries2D", "BarSideBySideSeries2D", "StockSeries2D", "PieSeries2D", "AxisX2D", "AxisY2D", or "SeriesItemsSource".

Build WPF applications with the DevExpress layout-management controls — DockLayoutManager (Visual Studio-style dockable panels and MDI), LayoutControl (compound forms with auto-aligned labels and groups), DataLayoutControl (auto-generated form from a POCO via DataAnnotations), TileLayoutControl (Windows UI-style tiles), FlowLayoutControl (wrapping flow of items), DockLayoutControl (edge docking inside a single panel). Use when picking the right layout container, building compound forms with LayoutGroup / LayoutItem, configuring tile sizes and groups, arranging flow items with break-flow and maximization, persisting user customizations with WriteToXML / SaveLayoutToXml. Also use when someone mentions "DockLayoutManager", "LayoutControl", "DataLayoutControl", "TileLayoutControl", "FlowLayoutControl", "DockLayoutControl", "DevExpress.Xpf.LayoutControl", "DevExpress.Xpf.Docking", "dxdo:", "dxlc:". Covers .NET 8+ and .NET Framework 4.6.2+.

>- XAF Conditional Appearance module for dynamic UI styling. Covers AppearanceAttribute for controlling FontColor, BackColor, FontStyle, Enabled, and Visibility on UI elements, AppearanceItemType (ViewItem, Action, LayoutItem), TargetItems, Context (ListView, DetailView, Any), Criteria-based and Method-based rules, Priority, supported UI elements matrix (grid cells, property editors in DetailView, static text, layout items, layout groups, actions), AppearanceController events (AppearanceApplied, CustomApplyAppearance, CollectAppearanceRules), IAppearanceFormat/IAppearanceEnabled/IAppearanceVisibility interfaces, and AddConditionalAppearance builder method.

>- XAF Views, layout, and navigation. Covers ListView, DetailView, DashboardView class hierarchy, View creation (Application.CreateListView/CreateDetailView/CreateDashboardView), ShowViewParameters for displaying views in new windows/popups, View.CurrentObject, ListView.CollectionSource, ListView.Editor, CompositeView.FindItem, list view data access modes (Client, Server, DataView, InstantFeedback, Queryable), list view edit modes (inline, batch, split layout MasterDetailMode), Detail View layout customization via DetailViewLayoutAttribute, DefaultClassOptionsAttribute/NavigationItemAttribute for navigation, DashboardView with DashboardViewItem, accessing selected objects, accessing UI controls via OnViewControlsCreated and CustomizeViewItemControl, View.IsRoot, and non-persistent object views. Use when someone asks about views, layouts, navigation, showing views, popups, dashboard views, list view modes, or detail view customization in XAF.

Generate a high-density A4 cheat sheet for open-book exams. Two output paths: LaTeX (XeLaTeX) or self-contained HTML with CSS print layout. Both paths produce visually consistent results.

为非多模态模型（如 deepseek-v4-pro、GLM-5.1、mimo-v2.5-pro 等纯文本模型）提供图片识别能力。当主模型无法识别图片、用户发送了截图/设计稿/UI 截图需要分析、或者用户说'看看这张图'、'分析这个截图'、'这张图片有什么问题'时，自动触发此技能。也适用于用户粘贴了图片但当前模型不支持图片输入的任何场景。支持同时识别多张图片，通过配置多个识图模型实现主备回退。使用指令 /skill:vision-support 或 /vision 也可手动触发。铁律：本技能配置的模型仅用于图片内容识别，绝不参与主逻辑推理。注意：如果当前模型本身是多模态模型（如 Claude Sonnet 4、GPT-4o、Gemini 等可以直接识图的模型），不要使用此技能，直接让主模型识别即可。

Visualize business domains as standalone HTML + inline-SVG artifacts using an opinionated editorial design system. Ships six domain-modelling types — Aggregate, Context Map, Event Storm, Context Canvas, Ubiquitous Language glossary, and Domain Model — for exploring DDD designs with stakeholders, capturing decisions from event-storming sessions, or documenting a bounded context in a repo. Use this skill whenever the user wants to sketch, explore, or document a business domain — triggered by mentions of DDD, domain-driven design, bounded contexts, aggregates, event storming, ubiquitous language, context mapping, or any request to "visualize the domain", "draw the model", "map the contexts", "show the aggregate", or "help me think through the business". Shares a skinnable style guide with diagram-design so technical and domain diagrams produced for the same project look like siblings.

| Guide for building SwiftUI components using Brad Frost's Atomic Design methodology — organizing views into Atoms, Molecules, Organisms, Templates, and Pages with Design Tokens for theming. Use this skill whenever building new SwiftUI UI components, refactoring existing views into reusable pieces, creating a design system, or organizing a component library. Also trigger when the user mentions "atomic design", "design system", "component hierarchy", "reusable components", "atoms and molecules", "design tokens", or wants to decompose a complex SwiftUI view into smaller, composable parts, or needs to implement theming/customization across a SwiftUI app.

| Create interactive iOS/mobile app UX flow prototypes as HTML documents with realistic phone mockups. (3) Documenting screen-to-screen navigation patterns, (4) Presenting iOS UI designs with annotations, (5) Prototyping app architecture before implementation. Generates self-contained HTML files with iOS-native styling, phone frames, flow arrows, and callout annotations.

Protects design and theme files from unintended changes. Locks tailwind.config, global CSS, and theme variables. Requires explicit confirmation before modifying UI components. Activate on changes to CSS, theme config, or layout components.

Analyze and extract design patterns from visual examples. Deconstructs design systems, color palettes, typography, and layout principles from reference materials.

Design interfaces using component libraries and design systems. Creates cohesive UIs with pre-built accessible component primitives.

Generate design systems and theme variations. Creates cohesive visual systems with color schemes, typography, and component styling.

Build interactive web components and artifacts. Creates interactive UI elements, visualizations, and web-based applications.

Create and edit presentation documents with full formatting. Handles slide creation, layouts, animations, and speaker notes programmatically.

Design visual layouts and compositions for web and print. Creates balanced designs with typography, color, and spacing principles applied consistently.

Architect and design web application interfaces. Plans component systems, interaction flows, and responsive layouts for web platforms.

Generates Remotion composition structure focusing ONLY on Sequence ordering, scene transitions, and duration mapping. Input is scene list with durations. Output is COMPOSITION_STRUCTURE.md with Sequence layout and timing calculations. Use when organizing scenes or when asked to "structure composition", "layout scenes", "calculate timing".

Generates individual Remotion scene components from visual direction. Input is visual/animation description for a specific scene. Output is SCENE_COMPONENT.md with complete TSX implementation. Use when implementing scenes or when asked to "create a scene component", "implement scene from spec", "build Scene1Intro".

> Load this skill when writing, reviewing, or interpreting behavioral accessibility automation — tests that manipulate a rendered page (resizing the viewport, pressing real keys, capturing and comparing screenshots) rather than only inspecting static markup or a single computed accessibility tree. Covers Reflow risk (SC 1.4.10) and Focus Visible risk (SC 2.4.7) checks. Absolutely always report indicator results separately from confirmed failures. Under no circumstances treat a clean behavioral scan as WCAG conformance, or collapse `cantTell`/test-error/indicator outcomes into a single pass/fail signal.

> Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.

> Load this skill immediately whenever a project contains an ACCESSIBILITY.md file, or whenever you are contributing to the mgifford/ACCESSIBILITY.md repository. Absolutely always read ACCESSIBILITY.md before proposing or writing any changes. Under no circumstances skip this skill when an ACCESSIBILITY.md file is present. This skill governs when and how all other accessibility topic skills must be loaded.

> Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.

Audit live URLs using Playwright and Axe combined with WCAG skills