'dialogs' 검색 결과

Use when implementing PyQt/PySide6 dialogs - standard dialogs (QFileDialog, QMessageBox, QInputDialog, QColorDialog, QFontDialog), custom QDialog patterns, modal vs modeless dialogs, input validation, Qt 6 dialog APIs

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review dialogs to check whether screen readers can announce their purpose when they open. Identify missing or unclear labels, suggest title or label associations, and explain how to verify the changes with accessibility tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking names on modal dialogs
• Reviewing labels on alert dialogs
• Auditing shared dialog components

Control visible local apps and external browser windows through Orca, including clicks, typing, menus, dialogs, and screenshots. Use it for tasks that require interacting with a screen and cannot be completed through commands or APIs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Entering text and clicking controls in a local app
• Handling menus and dialogs in an external browser
• Capturing screenshots of a visible window

Review modal dialogs for keyboard and screen reader accessibility. The skill checks dialog roles, title labels, focus movement within the modal, Escape dismissal, and focus returning to the opening control, then identifies issues and ways to verify fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing keyboard operation in modal dialogs
• Checking focus movement when opening and closing modals
• Reviewing dialog titles and screen reader labels

Turn descriptions of 3D shapes and CAD tasks into FreeCAD Python scripts. Create models with adjustable dimensions, automate repeated operations with macros, convert meshes and solids, or build custom dialogs and workbench tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create 3D models from written descriptions
• Build models with adjustable dimensions
• Automate repeated CAD operations with macros

Build and review JetBrains plugin interfaces using Swing and IntelliJ Platform components. Follow concrete rules for layouts, theme colors, fonts, spacing, dialogs, and tool windows while keeping shared style values consistent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building tool windows and settings screens
• Reviewing theme colors, fonts, and spacing
• Choosing components for dialogs and notifications

Design and improve SaaS upgrade screens, paywalls that restrict access to paid features, and upsell dialogs. Use it to shape screens that encourage paid subscriptions and support experiments with pricing pages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing screens that encourage upgrades to paid plans
• Improving paywalls for paid features
• Designing dialogs that offer additional purchases

Review pop-ups, modals, and banners that obscure page content. Identify mobile usability and search visibility concerns, then improve dismissal controls and keyboard focus, the element currently receiving keyboard input.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review promotional pop-ups on mobile
• Check keyboard dismissal of modals
• Verify focus movement when dialogs open and close

Review keyboard focus, the element currently selected for interaction, to check that Tab navigation follows the page’s visual order. Identify HTML ordering issues and verify focus stays within dialogs and returns to their triggers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing a page’s Tab navigation order
• Checking focus when dialogs open and close
• Reviewing HTML order and tabindex values

Review where keyboard focus, the current target for keyboard input, moves when dialogs open, views change, or content updates. Identify misplaced or lost focus and propose changes that help keyboard and screen reader users continue navigating.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking focus when dialogs open and close
• Reviewing focus after SPA navigation
• Keeping keyboard navigation usable during content updates

Build Blazor interfaces with Microsoft Fluent UI components. The skill guides library setup, forms, selection controls, dialogs, notifications, and themes, and helps troubleshoot missing interface elements caused by provider configuration or JavaScript integration issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up Fluent UI in a Blazor application
• Building forms with selection and autocomplete controls
• Adding dialogs and toast notifications

Build iOS and Android interfaces with HeroUI Native components such as buttons, cards, text fields, and dialogs. The skill covers setup, documentation lookup, and theme configuration with Uniwind, which brings Tailwind styling to React Native.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up HeroUI Native in an Expo project
• Build mobile cards and input fields
• Configure light and dark themes

Test Qwen Code through realistic keyboard interactions in tmux, a terminal session tool. Capture readable screen snapshots at each step and produce a report documenting dialogs, commands, outcomes, and observed side effects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing authentication dialogs and keyboard navigation
• Checking slash command interactions
• Reviewing intermediate screens for regressions

Update visible interfaces in Lite and but.dev using @gitbutler/ui-react. It guides component reuse, relevant design references, concise screen text, and visual checks in light and dark themes for forms, dialogs, notifications, and other surfaces.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add forms or confirmation dialogs
• Improve empty states and notifications
• Rewrite labels and hints

Build React interfaces for Kortix using @kortix/ui components. The skill covers forms, dialogs, notifications, and chat views, with shared styling rules, brand customization through CSS variables, and checks for types, controls, and responsive layouts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building forms and dialogs with existing components
• Adding a chat view with SessionThread
• Adapting component colors and logos to another brand

Inspect the current QM web interface through its HTML and structured app state, with optional stylesheets and a rendered image. Use it to explain visible UI elements, help with interface questions, or check how a canvas appeared.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Help with questions about the current QM screen
• Check a canvas's appearance and placement
• Inspect the state of panes and open dialogs

Build and modify Native SDK apps with guidance on project structure, configuration, native features, packaging, and testing. Explains the default TypeScript and Native markup approach, plus WebViews, embedded web interfaces, and their permissions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identify where to change an existing app
• Connect a web interface to native features
• Configure permissions for windows and dialogs

Build reusable React components that save settings in browser storage and support keyboard selection. The patterns cover settings dialogs and command palettes, with guidance on TypeScript types, storage keys, and managing keyboard focus.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Keeping app settings across page reloads
• Building command selection with arrow keys and Enter
• Creating reusable settings dialogs

Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll. Use when: the shim picks the wrong runtime, fails to load any runtime, shows unexpected .NET 3.5 Feature-on-Demand (FOD) dialogs, unexpectedly does NOT show FOD dialogs, loads both v2 and v4 into the same process causing failures, or any time someone is wondering "what is happening with .NET Framework activation?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses .NET Framework CLR activation issues using CLR activation logs (CLRLoad logs) produced by mscoree.dll. Use when: the shim picks the wrong runtime, fails to load any runtime, shows unexpected .NET 3.5 Feature-on-Demand (FOD) dialogs, unexpectedly does NOT show FOD dialogs, loads both v2 and v4 into the same process causing failures, or any time someone is wondering "what is happening with .NET Framework activation?"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and improve the accessibility of the timepicker-ui documentation site (docs-app/) - landmarks, heading order, skip links, keyboard nav, focus management in the command menu / sidebar / dialogs, color contrast, alt text, ARIA on custom components (tabs, native dialogs), reduced motion - against WCAG 2.2 AA. Use when the user wants an a11y audit/fix of the docs site. Drives the docs-accessibility subagent in an audit → approve → apply flow. Does NOT cover the library (use /a11y for that).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rules and patterns for writing tests of Avalonia UI visual elements (controls, dialogs, panels). Use when creating or modifying tests for XAML controls, dialogs, or panels.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rules and patterns for creating Avalonia UI visual elements (controls, dialogs, panels, windows). Use when creating or modifying XAML controls, dialogs, panels, or windows in this project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure platform-level global search in a Salesforce org — per-object Search Layouts (Search Results, Lookup Dialogs, Lookup Phone Dialogs, Tab columns), the Setup → Search Settings page (Sidebar Search, Lookup Auto-Completion, Drop-Down List size), and Synonym Groups (Setup → User Interface → Synonyms). NOT for Einstein Search personalization signals or Natural Language Search (use agentforce/einstein-search-personalization), NOT for Experience Cloud site Search Manager (use lwc/experience-cloud-search-customization), NOT for SOSL query authoring (use data/sosl-search-patterns), NOT for Commerce storefront search tuning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.