'layout' 검색 결과

System reference for the crouton layout engine (@fyit/crouton-layout) — the LayoutTree/layout_configs data model, the croutonLayoutBlocks registry and sizing contract, the viability metric, the deterministic placer (#709), and how layouts persist and seed. Use when reasoning about WHY a layout renders/composes/persists the way it does, when a question is shaped like "what is a LayoutTree / where do layouts live / why did the placer pick this arrangement / why won't this pane shrink / where does minWidth get read", or when a generated POC boots with the wrong (or no) default layout. Trigger phrases: "layout tree", "layout_configs", "viability check", "composeDefaultLayout", "block sizing contract", "why is my layout not viable". For authoring a block component, use the block-authoring skill instead.

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

Use when designing or reviewing list views, compact layouts, highlights panels, and search-result presentation so users can scan, find, and act on records quickly across desktop and mobile. Covers the deployable ListView, CompactLayout, SearchLayouts and ProfileSearchLayouts metadata: filterScope, booleanFilter, sharedTo, compactLayoutAssignment, and the package.xml shapes for each. Triggers: 'too many list views', 'compact layout not showing the right fields', 'search layouts vs list views', 'mobile highlights panel', 'list view missing after sandbox refresh', 'deploy a list view between orgs', 'list view column deployed blank', 'compact layout deploy failed', 'compact layout was named in package.xml but was not found in zipped directory'. NOT for page layouts or record types — use admin/record-types-and-page-layouts. NOT for Dynamic Forms — use admin/dynamic-forms-and-actions.

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

Use when designing or refactoring record types across objects with many profiles, business processes, or picklist variations. Covers layout assignment explosion, Dynamic Forms migration, and record type ID portability. NOT for basic record type setup or page layout assignment — use admin/record-types-and-page-layouts. NOT for converting one page layout to Dynamic Forms — use admin/dynamic-forms-migration. Trigger keywords: record type consolidation, layout assignment matrix, recordTypeVisibilities, layoutAssignments, Master record type default, bulk RecordTypeId migration, record type audit, RecordType wildcard package.xml.

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

Layout structure for web interfaces, from grouping and alignment to reading order, progressive disclosure, and adaptive breakpoints. Use when structuring a page or component, spacing or aligning controls, deciding what collapses at small sizes, handling RTL layout direction, or reviewing frontend code for layout. Triggers on layout, spacing, alignment, grouping, negative space, whitespace, visual hierarchy, reading order, progressive disclosure, breakpoints, responsive layout, container queries, safe area, full-bleed, edge-to-edge, layout margins, RTL layout, logical properties.

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

Choose automatic layouts for diagrams made of connected nodes. Match algorithms and tools to the graph structure, then plan connector routes, overlap handling, and stable placement so readers can follow relationships and edits remain predictable.

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

• Reducing crossings in a dependency graph
• Routing ERD connectors around tables
• Choosing layouts for trees and networks

Use when designing, auditing, or simplifying Record Types and Page Layouts. Triggers: 'record type', 'page layout', 'different picklist values', 'different fields per team', 'dynamic forms', 'business process', 'recordTypeVisibilities', 'layoutAssignments', 'record type deploy failed', 'businessProcess required', 'layout assignment matrix'. NOT for layout explosion across many profiles — use admin/record-type-strategy-at-scale. NOT for sharing rules — use admin/sharing-and-visibility. NOT for FLS — use admin/permission-sets-vs-profiles.

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

Collage as a web design aesthetic — overlapping elements, mixed media, cut-out shapes, scrapbook layouts, and editorial magazine spreads adapted for the web. CSS techniques for layered compositions using z-index stacking, clip-path, mix-blend-mode, parallax layering, and grid-breaking layouts. Activate on 'collage web', 'editorial layout', 'magazine layout', 'overlapping elements', 'scrapbook', 'cut-out aesthetic', 'mixed media web', 'layered composition', 'grid-breaking', 'editorial web design', 'fashion website layout', 'David Carson'. NOT for photo collage/gallery grids (use collage-layout-expert), maximalist density (use maximalist-web-design), neobrutalism (use neobrutalist-web-designer).

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

Collage as a web design aesthetic — overlapping elements, mixed media, cut-out shapes, scrapbook layouts, and editorial magazine spreads adapted for the web. CSS techniques for layered compositions using z-index stacking, clip-path, mix-blend-mode, parallax layering, and grid-breaking layouts. Activate on 'collage web', 'editorial layout', 'magazine layout', 'overlapping elements', 'scrapbook', 'cut-out aesthetic', 'mixed media web', 'layered composition', 'grid-breaking', 'editorial web design', 'fashion website layout', 'David Carson'. NOT for photo collage/gallery grids (use collage-layout-expert), maximalist density (use maximalist-web-design), neobrutalism (use neobrutalist-web-designer).

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

Capture Remotion Studio timelines with matching framing and create a video that wipes between the before and after images. The workflow also covers recreating an older layout from a historical code revision.

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

• Create a video comparing timeline layouts
• Recapture a layout from an older code revision
• Save before and after screenshots with matching framing

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

Create structured web layouts with thin borders, L-shaped corner marks, and subtle diagonal backgrounds. Align sections, headings, controls, and media to a shared grid, with consistent spacing and a single-column layout on narrow screens.

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

• Design a web page with clearly framed sections
• Align headings, controls, and media to a shared grid
• Add subtle diagonal textures and corner marks

Generate and edit presentation slides as PPTX files. Also create LinkedIn carousels and manage reusable slide layouts. TRIGGERS - Use this skill when user says: - "create slides for [brand]" / "generate presentation for [brand]" / "make slides for [brand]" - "create a carousel for [brand]" / "linkedin carousel" / "make a carousel about [topic]" - "edit this pptx" / "update the slides" / "modify this presentation" - "create a new layout" / "add a layout to the cookbook" / "make a [type] layout template" - "edit the [name] layout" / "update the cookbook" / "improve the [name] template" - Any request mentioning slides, presentations, carousels, PPTX, or layouts with a brand name Creates .pptx files compatible with PowerPoint, Google Slides, and Keynote. Creates PDF carousels for LinkedIn (square 1:1 format).

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

Avalonia Layout with Zafiro.Avalonia workflow skill. Use this skill when the user needs Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Automatic graph layout using dagre with React Flow (@xyflow/react). Use when implementing auto-layout, hierarchical layouts, tree structures, or arranging nodes programmatically. Triggers on dagre, auto-layout, automatic layout, getLayoutedElements, rankdir, hierarchical graph.

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

Design a layout system — spacing scale, grid columns, and layout primitives. Use when asked to "design a spacing system", "set up a layout grid", or "build layout primitives".

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

Use this skill when configuring object-specific quick actions or global actions in Salesforce: choosing between action types, editing action layouts, pre-filling fields with predefined values, and adding actions to Lightning page layouts or mobile navigation. Trigger keywords: quick action, global action, action layout, pre-fill fields, predefined values, Salesforce mobile actions. NOT for building an LWC that runs as a quick action — use lwc/lwc-quick-actions. NOT for converting Classic JavaScript or URL buttons — use admin/custom-button-to-action-migration. NOT for Dynamic Actions visibility rules on a Lightning record page — use admin/dynamic-forms-and-actions. Also covers the QuickAction metadata type: quickAction-meta.xml, quickActionLayout, fieldOverrides, targetObject, targetParentField, targetRecordType, flowDefinition, and the Layout platformActionList and quickActionList entries that place an action.

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

UIKit iOS/iPadOS UI フレームワーク。 UIViewController, UINavigationController, UITabBarController, UISplitViewController, UIView, UILabel, UIButton, UITextField, UIScrollView, UIStackView, UITableView, UICollectionView, diffable data source, NSDiffableDataSourceSnapshot, UICollectionViewCompositionalLayout, Auto Layout, NSLayoutConstraint, NSLayoutAnchor, UILayoutGuide, intrinsicContentSize。 UIArrangementViewController, UISplitArrangement, UIOverlayArrangement, UIView.ReservedRegion, UIHingeInteraction, 縦軸バー, iPhone Duo adaptive layout (iOS 27.1+), scene-based life cycle 移行, UISceneAccessory。SwiftUI ArrangementView とは別 API。

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

Locate CCSCustomHudLayout_SetDialogVariableString in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableString" (symbol CCSCustomHudLayout_SetDialogVariableString). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableString, CCSCustomHudLayout_SetDialogVariableString

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

Locate CCSCustomHudLayout_SetHasClass in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClass" (symbol CCSCustomHudLayout_SetHasClass). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClass, CCSCustomHudLayout_SetHasClass

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

Locate CCSCustomHudLayout_SetHasClassForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClassForPlayer" (symbol CCSCustomHudLayout_SetHasClassForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClassForPlayer, CCSCustomHudLayout_SetHasClassForPlayer

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

Locate CCSCustomHudLayout_SetInputCaptureEnabled in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetInputCaptureEnabled" (symbol CCSCustomHudLayout_SetInputCaptureEnabled). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetInputCaptureEnabled, CCSCustomHudLayout_SetInputCaptureEnabled

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

Locate CCSCustomHudLayout_SetDialogVariableStringForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetDialogVariableStringForPlayer" (symbol CCSCustomHudLayout_SetDialogVariableStringForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetDialogVariableStringForPlayer, CCSCustomHudLayout_SetDialogVariableStringForPlayer

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

Review fixed pixel values in fonts, widths, and spacing, then suggest relative units that adapt to available space and browser font preferences. Check rendered layouts at different screen widths and during interactions before proposing changes.

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

• Adapting text to browser font size preferences
• Replacing fixed widths with flexible layouts
• Reviewing spacing units within components

Review CSS layouts for unwanted horizontal scrolling on narrow screens and at high browser zoom. Identify fixed widths, overflowing media, and unbroken text, then apply layout fixes that keep content readable within the viewport.

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

• Fix horizontal scrolling on mobile pages
• Check page layouts at 400% browser zoom
• Review wrapping for long URLs and large images