2.1천건 · 관련도순
Turn text or structured data into infographics with selected layouts and visual styles. The skill can refine image prompts and, across multiple generation rounds, review the images and rank the results for selection.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create, modify, debug, and review Windows Forms applications while preserving their editable layouts in Visual Studio Designer. Covers resizing, data binding, asynchronous UI behavior, and checks that distinguish successful builds from actual screen and designer verification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Configure and troubleshoot custom build logic in MSBuild. Check hooks, import order, control properties, and NuGet package layouts to explain why extension files are missing, skipped, or replaced, including paths for specific target frameworks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and render fanout, implement semantically safe fixes, and verify behavior plus repository budgets. Use for trace files, reported profiling durations or call chains, dropped frames, long tasks, resize or scroll jank, render storms, layout thrashing, selector hot paths, interaction latency, or requests to locate exact source-level bottlenecks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Golang project layout and workspace setup — cmd/internal/pkg directory conventions, module and package naming, go.work workspaces, and essential configuration files. Use when starting a new Go project, organizing an existing codebase, setting up a monorepo with multiple packages, creating CLI tools with multiple main packages, or discussing package restructuring, package splits, or module splits. Not for restructuring existing code without a layout change (→ See `samber/cc-skills-golang@golang-refactoring` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build SwiftUI layouts using stacks, grids, lists, scroll views, forms, and controls. Covers VStack/HStack/ZStack, LazyVGrid/LazyHGrid, List with sections and swipe actions, ScrollView with ScrollPosition and scroll-driven reveal surfaces, Form with validation, Toggle/Picker/Slider, .searchable, and overlay patterns. Use when building data-driven layouts, collection views, paged detail reveals, settings screens, search interfaces, or transient overlay UI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
경영 회의와 제안용 슬라이드를 설계 규칙과 62종 HTML 구성 요소로 만듭니다. 배치를 검사해 HTML과 PDF로 제공하며, 요청하면 기존 자료의 서식에 맞춘 PPTX도 만듭니다.
Dielectric substrates, metal conductors, multi-layer stackups, and loss models (FR4, Rogers, Teflon) for RF PCB simulation. TRIGGER: user asks to set up a substrate, define dielectric properties, create a stackup, select a PCB material (FR4, Rogers, Teflon, etc.), or configure metal conductors. Invoke BEFORE writing dielectric() or metal() code — the API for named vs custom materials differs significantly. SKIP: PCB layout assembly (use matlab-assemble-pcb-layout), transmission line design (use matlab-design-pcb-transmission-line), EM analysis (use matlab-analyze-em), importing a PCB file (use matlab-read-pcb-layout).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Export pcbComponent designs to Gerber files with RF connectors and fab service formatting for PCB manufacturing. TRIGGER: user asks to export a PCB design to Gerber, generate manufacturing files, or write out a pcbComponent for fabrication. Invoke BEFORE writing export code — gerberWrite signature (pcbComponent, connectors, filename) is non-obvious. SKIP: importing/reading PCB files (use matlab-read-pcb-layout), building PCB geometry (use matlab-assemble-pcb-layout), EM analysis (use matlab-analyze-em), material/stackup setup (use matlab-manage-pcb-material).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Import Gerber, ODB++, Allegro .brd, .mcm files for PCB boards and IC packages. Inspect nets, layers, shapes, and stackups. TRIGGER: user asks to import, read, or open a PCB layout file. Gerber files use gerberRead or PCBReader; ODB++, Allegro .brd, .mcm, and native formats use pcbFileRead. Also when inspecting nets, layers, components, or stackups from an imported board. Invoke BEFORE writing import code — the query API (cadnet, cadnetList, componentList) is specialized. SKIP: EM analysis or S-parameter extraction (use matlab-analyze-em), PDN/IR-drop analysis (use matlab-analyze-pcb-pdn), building custom geometry (use matlab-assemble-pcb-layout), material/stackup definition only (use matlab-manage-pcb-material).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SwiftUI framework skills — data flow (identity, Observation, state ownership), layout & containers (Layout protocol, lazy-stack performance), AlarmKit, 3D charts, rich text editing, customizable toolbars, and WebKit embedding. Use for SwiftUI state/rendering bugs, custom layouts, scroll performance, or these feature areas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement ViewBinding, RecyclerView, and XML layouts correctly on Android. Use when changing XML view binding or RecyclerView behavior, including its item animations and layout managers; defer standalone animation or layout-manager questions unrelated to RecyclerView.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
.NET MAUI safe area and edge-to-edge layout guidance for .NET 10+. Covers the new SafeAreaEdges property, SafeAreaRegions enum, per-edge control, keyboard avoidance, Blazor Hybrid CSS safe areas, migration from legacy iOS-only APIs, and platform-specific behavior for Android, iOS, and Mac Catalyst. USE FOR: "safe area", "edge-to-edge", "SafeAreaEdges", "SafeAreaRegions", "keyboard avoidance", "notch insets", "status bar overlap", "iOS safe area", "Android edge-to-edge", "content behind status bar", "UseSafeArea migration", "soft input keyboard", "IgnoreSafeArea replacement". DO NOT USE FOR: general layout or grid design (use Grid and StackLayout), app lifecycle handling (use maui-app-lifecycle), theming or styling (use maui-theming), or Shell navigation structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parse complex documents with IBM's open-source Docling library, which turns PDFs and Office files into structured Markdown or JSON. Use when a user asks to parse a document with tables, extract figures from a document, handle multi-column layouts, convert a complex PDF to structured data, extract content from academic papers, or process documents with mixed layouts. Handles tables, figures, headers, footers, and multi-column text.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement high-quality blog post and article page layouts with professional typography, spacing, and visual hierarchy. Use when building blog pages, article templates, technical documentation readers, use-case pages, or long-form content layouts. Covers dark and light themes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Figma 转 Photoshop (PSD) (Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及).) Master OS — automated mastery of Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及).: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on Figma → Photoshop (PSD) 设计稿转换 (从业者视角) — 把 Figma 设计文件高保真转换为 Photoshop 分层 PSD, 核心是对齐两个工具的概念/渲染差异, 让产出的设计稿视觉一致. 覆盖: (a) 概念映射 — Figma frame / auto-layout / component / variant / constraint / vector-network / boolean / effect (drop·inner shadow / layer·background blur) / mask / blend mode / gradient / text-engine / color 与 Photoshop artboard / group / smart-object / linked / layer-style / shape-layer / path / clipping·layer mask / blend-mode 的对应关系与不可逆损耗点; (b) 转换方法栈 — 插件直出 PSD / 导出图层 (PNG·SVG) 再重组 / SVG·PDF 桥接 / 手工重建 / Figma REST API + Photoshop UXP·ExtendScript 脚本化, 各法在保真度-可编辑性-工时上的权衡与选型; (c) 保真度 QA — 字体回退与缺字处理 / 颜色空间 (sRGB·ICC profile) / 效果参数对齐 / @Nx·DPI 与栅格化 / 像素 diff 验收; (d) 两种交付目标 — 可编辑分层 PSD vs 像素保真扁平 PSD 的方法选择. 主战场 = Figma Community 插件 + Adobe 官方文档/论坛 + 设计交付 (design handoff) 实践 + 设计师社区. 不含: PSD→Figma 反向转换 / Sketch / Adobe XD / 纯前端 code handoff (HTML·CSS) / 印刷 CMYK 专业制版 (仅触及). problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「figma 转 psd」「figma to psd」「figma 转 photoshop」「figma 导出 psd」「设计稿转换」
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Animate state-driven layout/layoutId changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design multi-device layouts with Container Queries, clamp() fluid typography, :has() selector, subgrid, and modern CSS units (dvh/svh/lvh). Use when user asks to make a layout responsive, handle mobile/tablet/desktop breakpoints, create fluid typography, or use Container Queries. Do NOT use for full-page layouts (use landing-craft), component design (use component-forge), or animation-specific responsive (use motion-craft).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit existing layout patterns in a codebase — find ad-hoc spacing, inconsistent grids, and missing primitives. Use when asked to "audit our layout patterns", "we have ad-hoc spacing everywhere", or "our grids are inconsistent".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive UI design guidance based on Refactoring UI principles covering design personality, color theory, layout strategy, visual hierarchy, typography, spacing, mobile-first responsive design, and writing copy that doesn't read like AI wrote it. Use this skill whenever the user is creating new pages, building components, making design additions or changes, reviewing UI code, asking about design decisions (colors, fonts, spacing, layout), writing or editing interface copy, or discussing visual improvements. Trigger for any design-related conversation including "how should this look", "what color", "font size", "spacing", "layout", "responsive", "mobile", "this copy", "headline", "button text", "microcopy", or when reviewing/critiquing existing interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
调用 KLayout 0.30.8 执行 GDSII 导出（stream out）、GDS-level DRC、或导出后 verify。PD 流程末尾产出最终 .gds（signoff 产物）。触发场景：(1) bba-guru-pd routed 后 GDS export；(2) GDS 层 DRC 检查；(3) 导出后 verify；(4) 显式 /bb-invoke-klayout。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve layout composition, spacing systems, grouping, and visual rhythm. Use when the user mentions weak layout structure, arbitrary spacing, weak grouping, crowded composition, or layout monotony rather than priority/emphasis problems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design Shiny application UIs using bslib for theming, layout_columns for responsive grids, value boxes, cards, and custom CSS/SCSS. Covers page layouts, accessibility, and brand consistency. Use when building a new Shiny app UI from scratch, modernizing an existing app from fluidPage to bslib, applying brand theming, making a Shiny app responsive across screen sizes, or improving accessibility of a Shiny application.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.