'interaction' 검색 결과

Review styles written directly in HTML or embedded style blocks, and move suitable rules into external stylesheets. Check layouts across screen sizes and interaction states while preserving justified exceptions for critical styles and dynamic values.

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

• Reviewing styles written directly in HTML
• Moving embedded styles into external stylesheets
• Checking exceptions for critical CSS and dynamic values

Review CSS loading that delays a page’s first visible content. Help inline essential styles and defer other stylesheets, using preload and media conditions, while checking rendered layouts at different screen widths and interaction states.

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

• Investigating CSS that delays initial page display
• Separating essential styles from styles loaded later
• Reviewing preload and media-based stylesheet loading

Review the loading order of CSS and JavaScript to address rendering delays and flashes of unstyled content. Suggest changes to the document head, script loading, and critical styles, while checking layouts across screen sizes and interaction states.

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

• Investigating flashes of unstyled content
• Reviewing CSS and JavaScript order in the document head
• Checking deferred scripts and critical styles

Guides Avalonia interface layout with Zafiro.Avalonia, using shared styles, reusable components, and purpose-specific containers. Helps reduce repeated XAML, the markup used to define interfaces, and simplify deeply nested layouts.

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

• Simplifying deeply nested screen layouts
• Sharing styles across multiple screens
• Extracting reusable interface components

Test app interfaces on an Android emulator using ADB, a command-line device tool. Inspect element positions, perform taps and text entry, then check screenshots and React Native logs to verify behavior and investigate layout or interaction bugs.

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

• Verify app interfaces after UI changes
• Investigate layout and interaction bugs
• Check feature behavior through automated interactions

Structure Avalonia interfaces with Zafiro.Avalonia using shared styles, reusable components, and purpose-built layout containers. Guides reductions in duplicated XAML, the interface markup, and deeply nested layouts, while covering themes, icons, and interaction behavior.

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

• Consolidating repeated visual settings into shared styles
• Simplifying deeply nested screen layouts
• Extracting repeated layouts into reusable components

Write game interface specifications for individual screens, interaction flows, and the HUD, the information shown during play. Also document shared interaction patterns and project-wide accessibility requirements, with section depth guided by project settings.

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

• Writing specifications for game screens and navigation flows
• Designing the HUD information shown during play
• Documenting shared interaction patterns

Automate browser actions such as filling forms, clicking buttons, and switching tabs. Inspect page snapshots, network requests, and console messages to check website behavior, record interactions, and support work on Playwright tests.

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

• Checking form submission and page navigation
• Investigating browser errors and network requests
• Recording browser interactions as video

Refine interface details such as rounded corners, shadows, typography, icon alignment, and animations. Use concrete implementation rules to improve visual consistency and interaction feedback, with changes documented in before-and-after tables.

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

• Refining the appearance of existing UI components
• Improving button and icon interaction feedback
• Reviewing entrance and exit animations

Create screen mockups at three levels: text wireframes, standalone HTML files, or working prototype pages. Use requirements, existing app styles, and real project data to show layouts and interactions for review or testing.

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

• Sketch screen layouts while writing requirements
• Deliver HTML mockups alongside requirements
• Test interactions with existing components

Choose, create, and review software diagrams that explain structure, interactions, workflows, states, or data relationships. Select suitable notation and rendering tools, then plan static exports or interactive views with readable layouts, accessible controls, and validation.

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

• Explain login interactions with a sequence diagram
• Turn a database schema into an entity relationship diagram
• Document application architecture with C4

Test and debug rendered web apps by reproducing interaction bugs, checking layouts and console errors, making focused fixes, and validating again. Results include screenshots, observed state changes, and a QA report explaining coverage and remaining gaps.

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

• Reproducing and fixing broken UI interactions
• Checking desktop and mobile layouts
• Investigating blank pages and console errors

Analyze a reference video's layout, typography, motion, and interactions to create a detailed prompt for rebuilding or adapting the experience. Include asset requirements, implementation choices, mobile behavior, and alternatives for users who prefer reduced motion.

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

• Turn a reference video into a detailed build prompt
• Describe scroll effects and transitions precisely
• Plan image and video assets for a recreation

Turn a working web effect or interaction into a reusable skill by extracting its core mechanism, documenting tested parameters and pitfalls, and packaging a demo that preserves the reference design and proves the behavior.

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

• Reuse a successful scroll effect across projects
• Package a canvas effect with a working demo
• Document tested parameters and hard-won fixes

Analyze strategic interactions in markets, including firm entry, pricing, auctions, and bargaining. Guides equilibrium selection and computation, explains how to handle multiple possible outcomes, and helps assess whether data can identify the model's parameters.

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

• Choosing and computing an equilibrium
• Planning an analysis of firm entry or price competition
• Handling multiple equilibria in empirical models

Spatial analysis of cell neighborhoods and interactions in IMC data. Covers neighbor graphs, spatial statistics, and interaction testing. Use when analyzing spatial relationships between cell types, testing for neighborhood enrichment, or identifying cell-cell interaction patterns in imaging mass cytometry data.

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

Specify one micro-interaction completely — trigger, rules, feedback, loops, and modes. Use when handing a single interaction to engineering. For motion craft alone use `animation-principles`; for multi-state components use `state-machine`.

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

Design the small details -- triggers, rules, feedback, loops and modes -- that separate good products from great ones. Use when the user mentions "microinteraction", "button feedback", "loading state", "toggle design", "animation detail", "state transitions", "input feedback", "the interface feels dead", "make the UI feel responsive", or "add polish to interactions". Also trigger when designing form-validation responses, progress indicators, confirmation dialogs, or any element where the user expects immediate feedback. Covers trigger design, state rules, feedback mechanisms, and progressive loops. For overall UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

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

Intelligent Core Web Vitals analysis with automated workflows and decision trees. Measures LCP, CLS, INP with guided debugging that automatically determines follow-up analysis based on results. Includes workflows for LCP deep dive (5 phases), CLS investigation (loading vs interaction), INP debugging (latency breakdown + attribution), and cross-skill integration with loading, interaction, and media skills. Use when the user asks about Core Web Vitals, LCP optimization, layout shifts, or interaction responsiveness. Compatible with Chrome DevTools MCP.

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

Query protein-protein and gene interaction databases (STRING, BioGRID, IntAct, SIGNOR, Reactome, HuRI, HuMAP, OmniPath, ConsensusPathDB, DIP). Use when building PPI networks, choosing between physical vs functional vs genetic interactions, signed/directed vs undirected, high-throughput vs curated, picking confidence thresholds, aggregating across resources, or navigating license constraints. Encodes the database decision matrix, STRING v12 channel semantics, OmniPath as meta-database, SIGNOR for signed signaling, and per-resource rate limits.

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

Provides utilities for identifying drug-target interactions for sets of small molecule or gene/protein identifiers. The required drug-target interaction information is obained from a local SQLite instance of the ChEMBL database. ChEMBL has been chosen for this purpose, because it provides one of the most comprehensive and best annotatated knowledge resources for drug-target information available in the public domain.

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

Systematic 3D interaction calls and differential analysis for Hi-C and HiChIP. The HiC-DC+ (Hi-C/HiChIP direct caller plus) package enables principled statistical analysis of Hi-C and HiChIP data sets – including calling significant interactions within a single experiment and performing differential analysis between conditions given replicate experiments – to facilitate global integrative studies. HiC-DC+ estimates significant interactions in a Hi-C or HiChIP experiment directly from the raw con

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

Use Grok 4.5 as the required external design advisor when a task needs UI critique, UX critique, component-choice review, interaction-flow review, design imagery markdown, art direction, visual hierarchy judgment, design-system fit, color/type/layout suggestions, HTML mockups, SVG icons, handwritten SVG wordmarks, or file-based feedback on existing UI. Trigger on requests like "design a page", "generate design imagery", "give design advice", "optimize this UI", "improve UX", "optimize user flow", "review interaction", "check usability", "reduce friction", "choose the right component", "review this design", "create an icon", "suggest colors", "UI mockup", "visual direction", "lettering", "wordmark", "handwritten logo", or when another agent needs a second opinion on visual or interaction quality.

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

Think and work like an expert Human–Computer Interaction Researcher. Use when a task calls for Human–Computer Interaction Researcher judgment. Reasons from situated context, Fitts/GOMS/KLM, and CHI contribution types; runs contextual inquiry through LMM/CLMM analysis with SUS/NASA-TLX triangulation; uses Prolific/OSF and treats demand characteristics, novelty effects, ordinal misuse, and WEIRD samples as first-class failure modes.

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