搜索「figma design image icon」的结果

io.github.thedaviddias/Front-End-Checklist/horizontal-scroll

适用于所有 CSS 布局规则。检查容器上的 width、min-width、固定像素值，以及 overflow、white-space、word-break 属性。审计响应式设计或 WCAG 2.1 AA 合规时使用。在 320px 视口宽度和 400% 浏览器缩放下测试。

io.github.thedaviddias/Front-End-Checklist/cascade-layers

审查存在优先级问题的 CSS 架构、搭建设计系统，或把大型代码库从 utility-first 迁移到分层架构时使用。

io.github.thedaviddias/Front-End-Checklist/content-without-css

审查可能依赖表现层传递语义的渲染 HTML、布局组件或设计系统模式时使用。检查 DOM 顺序、语义结构、表单关联，以及 CSS 生成内容是否承载了关键信息。

io.github.thedaviddias/Front-End-Checklist/css-custom-properties

审查样式表、组件样式与响应式行为，落实“用 CSS 自定义属性承载设计令牌”这一规则时使用。提出修复前要在各断点和交互状态下检查实际渲染布局。

io.github.thedaviddias/Front-End-Checklist/css-at-property

实现动画渐变、涉及自定义属性取值的复杂 CSS transition，或构建类型化设计令牌系统（希望自定义属性误用能直接报错）时使用。

io.github.nodejs/node/v8-understanding

Guides the methodology for investigating V8 concepts, codebase structure, performance, memory, and architecture. MANDATORY to use whenever triaging bugs, investigating crashes, reading C++ files, analyzing compiler optimizations (Ignition, Maglev, TurboFan, Turboshaft), or doing static research on V8 subsystems. Essential for locating high-level design documents in the local docs/ directory before reading C++ code. Do not use for raw build commands or Git workflows.

io.github.heygen-com/hyperframes/motion-graphics

以运动本身传递信息的短设计型 motion graphic——动态字体、数字滚动、图表/数据可视化呈现、logo 片头/品牌定格、下三分之一字幕条/浮层/社媒 overlay、动画地图（区域高亮、地点连线、缩放到某地）、推文/新闻文章/标题动画、网页/UI 动画（滚动、光标、callout），或将真实图片的几何结构融入图表。通常 10 秒以内（最长约 30 秒），无旁白与真人实拍；渲染为 MP4 或透明 overlay。更长的/有旁白的/多场景的用 /general-video；不明确的用 /hyperframes。

io.github.heygen-com/hyperframes/hyperframes-keyframes

当 HyperFrames 合成需要推近、拉出、缩放、改构图、Ken Burns 效果、运镜、视觉匹配/甩镜交接，或其他 seek-safe 的 2D/3D 关键帧时使用；也用于 GSAP、CSS keyframes、Anime.js、WAAPI、FLIP、路径、遮罩、SVG morph/draw、文字拖尾、3D 纵深，或 `hyperframes keyframes` 诊断。不要用于宽泛的场景策略、品牌设计、素材获取、字幕或一般视频规划。

io.github.asgeirtj/system_prompts_leaks/requirements-clarification

Clarify a material user-owned product decision before substantive implementation commitments. Use only when request and named/governing evidence still leave a choice that would materially change scope, platform support, user-facing surface, data/API contract, domain values, project placement, or cross-system architecture; also use when a truncated request omits such a choice. On the initial turn, inspect only named or governing requirements evidence, then ask directly without loading: prefer structured input; ask one blocking outcome question or at most three coupled questions; wait. After the answer, load the body before write or delegation. Do not use for implement/build/fix/debug/refactor work when expected behavior is settled, plan/design deliverables owned by Plan, complexity/greenfield/integration alone, agent-owned technical choices, locally discoverable facts, reversible defaults, permission to begin, or stop/no-tool turns. Never re-ask supplied facts or turn clarification into refusal.

io.github.asgeirtj/system_prompts_leaks/taste

Mandatory preflight for web frontend visual design. If available, call read_skill for bundled:taste before the first frontend create or edit tool call whenever creating or visually styling a human-viewed web page, component, app, dashboard, or interactive report. Do not load it for non-visual frontend logic or machine-only HTML. If unavailable, continue without warning. Negative constraints only; user requests and other explicit styles still win.

io.github.TriliumNext/Trilium/maintaining-docker-hub

Use when working on Trilium's published Docker images on Docker Hub or GHCR rather than on the Dockerfiles — "how many pulls does the image get?", "why is the Docker Hub repository so big?", "clean up old tags", "delete untagged images", "which tags do we publish?", the legacy repositories (triliumnext/notes, zadam/trilium) and their mirroring, the main-docker.yml copy-to-Docker-Hub step, mirror-legacy-docker.yml, Docker Hub categories, stars or the overview. Includes hub.mjs (stats, tag listing/deletion, the manifest inventory and a safe untagged-image purge, all dry-run by default) and the storage model that decides how a cleanup works. Do NOT use for building or running the image locally (see the Developer Guide's Docker page).

io.github.nextlevelbuilder/ui-ux-pro-max-skill/ui-ux-pro-max

面向 web、移动端与桌面的 UI/UX 设计智能库。在设计、构建、审查或修复界面时使用，覆盖页面、组件、设计体系、无障碍、交互、响应式布局、字体排印、色彩、图表以及特定技术栈的 UI 实现。本地可检索数据：79 种风格（可检索，50 种在用）、192 套产品配色与推理画像、74 组字体搭配、119 条 UX 准则、105 个图标、17 个 GSAP 预设、25 种图表类型与 22 个技术栈。

io.github.The-Vibe-Company/quivr/mermaid-diagrams

Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.

io.github.K-Dense-AI/scientific-agent-skills/adaptyv

如何使用 Adaptyv Bio Foundry API 与 Python SDK 进行蛋白实验设计、提交与结果获取。只要用户提到 Adaptyv、Foundry API、蛋白结合实验、蛋白筛选实验、BLI/SPR 实验、热稳定性实验，或想提交蛋白序列进行实验表征，就使用本技能。当代码导入 `adaptyv`、`adaptyv_sdk`、`FoundryClient`，或引用 `foundry-api-public.adaptyvbio.com` 时也应触发。

io.github.K-Dense-AI/scientific-agent-skills/statsmodels

Python 统计模型库。当需要具体的模型类（OLS、GLM、混合模型、ARIMA）并要详尽的诊断、残差与推断时使用。最适合计量经济学、时间序列，以及带系数表的严格推断。需要引导式统计检验选择与 APA 报告时使用 statistical-analysis。

io.github.K-Dense-AI/scientific-agent-skills/optimize-for-gpu

将科学 Python 工作负载加速到 NVIDIA GPU 上，并验证结果正确且更快。适用于 CUDA/GPU 优化；CPU 受限的 NumPy、SciPy、pandas、scikit-learn、NetworkX、scikit-image、向量检索、图像处理、图、仿真或文件 I/O 负载；CuPy、cuDF、cuML、cuGraph、cuVS、cuCIM、KvikIO、Warp、Newton、Numba-CUDA、RAFT 相关问题；以及性能剖析、内存搬运、kernel 或多 GPU 瓶颈。当大规模数据并行的 Python 代码很慢且 GPU 加速是合理选项时也应使用，即使用户没有提到 CUDA。

io.github.affaan-m/ECC/mybatis-patterns

MyBatis and MyBatis-Spring patterns for mapper design, XML and annotation SQL, result mapping, dynamic SQL safety, transactions, batching, pagination, and query performance. Use when building or reviewing Java persistence code with MyBatis, Spring Boot, MyBatis-Spring, or MyBatis-based legacy applications.

io.github.Stirling-Tools/Stirling-PDF/ui-walkthrough

对当前分支功能做完整的 UI 调查。枚举每个视图与状态（空态、有数据、加载、错误、每个对话框/菜单/面板、响应式断点、浅色+暗色+RTL），用内置 Playwright 工装捕获，汇总为带全局明暗切换滑杆的单图 HTML 走查，随后跑两轮审查：视觉/一致性（对齐、间距、专业感、明暗一致、对比度、截断）与 UX/易用性（流程、可发现性、可供性、空态/错误态、预期）。当被要求做 UI 走查、截图审查、设计或 QA 巡检、「找出可以更易用/更好的地方」或前端工作合并前使用。加 --fix 自动应用安全的前端修复并重新捕获；--theme 限定主题；--no-rtl 跳过 RTL。

io.github.deepseek-ai/deepseek-harness/dsh-trim-cot-leakage

在审计或修正读起来像泄漏推理记录的文案时使用——例如（决策 N）、审计条目编号等指向未提交草稿的陈旧设计会话引用；used to、no longer、this cut 之类的变更叙述；基于栈或评审视角的表述（本 stack 中后续的 PR、评审中被否决）；面向评审者的辩解；控制流叙述；以及注释、JSDoc、文档、Agent Notes 中残留的规划性试探语气。

io.github.affaan-m/ECC/redis-patterns

Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications. Use when adding caching, a distributed lock, rate limiting, or pub/sub with Redis, or when key design needs review.

io.github.affaan-m/ECC/swift-actor-persistence

Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design. Use when persisting data in Swift and a data race or thread-safety problem needs designing out.

io.github.affaan-m/ECC/jpa-patterns

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot. Use when designing JPA entities or relationships, or when a Hibernate query, transaction, or N+1 problem needs fixing.

io.github.affaan-m/ECC/make-interfaces-feel-better

Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.

io.github.affaan-m/ECC/postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices. Use when designing PostgreSQL schemas, indexes, or RLS policies, or when a query is too slow.