Token导航 LogoToken导航

Agent Skill · 前端设计

elevation-and-depth(高程和深度)

elevation-and-depth 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

elevation-and-depth 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 5,235。

总安装 710周安装 29GitHub Stars 6下载 227核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:elevation-and-depth(高程和深度)
来源仓库:https://github.com/dembrandt/dembrandt-skills
仓库路径:skills/elevation-and-depth
安装命令:
npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-and-depth
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-and-depth

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

elevation-and-depth 处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,支持项目协作管理。适用于围绕仓库状态、代码变更或协作事项进行整理和分析的场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。

安装前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/elevation-and-depth

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-a…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

elevation-and-depth 怎么安装?

在终端执行 npx skills add https://github.com/dembrandt/dembrandt-skills --skill elevation-and-depth。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

elevation-and-depth 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

elevation-and-depth 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

elevation-and-depth 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

elevation-and-depth 用的人多吗?

公开数据是累计安装 710 次,近一周安装 29 次,下载 227 次,GitHub 6 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

elevation-and-depth 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

前端设计类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
frontend-design

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
elevation-and-depth

高程和深度 · 本页

7106只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Elevation and Depth

Elevation uses shadow and layering to communicate that an element sits above the base surface — giving UI a sense of physical depth. Combined with border-radius, it creates the tactile quality that makes cards graspable, modals clearly floating, and dropdowns feel like they've appeared on top of content.

The Elevation Scale

Define a small set of elevation levels as tokens. Each level maps to a specific UI role.

LevelTokenShadowRole
0--shadow-nonenoneFlat surface, inline elements
1--shadow-xs0 1px 2px rgba(0,0,0,0.06)Subtle card, table row hover
2--shadow-sm0 1px 3px rgba(0,0,0,0.10), 0 1px 2px rgba(0,0,0,0.06)Card, input focus ring area
3--shadow-md0 4px 6px rgba(0,0,0,0.08), 0 2px 4px rgba(0,0,0,0.06)Dropdown, popover
4--shadow-lg0 10px 15px rgba(0,0,0,0.08), 0 4px 6px rgba(0,0,0,0.05)Modal, dialog, side drawer
5--shadow-xl0 20px 25px rgba(0,0,0,0.08), 0 8px 10px rgba(0,0,0,0.04)Command palette, full-screen overlay

Keep shadows subtle. Dark, heavy shadows feel dated and visually aggressive. Light, diffuse shadows feel modern and material.

The "Shadow + Border" Rule

A subtle shadow on a white surface can sometimes "wash out," making the edge of a card feel fuzzy or indistinct.

  • Rule: For elevated white cards or sections, pair the shadow with a 1px border that is slightly darker (1.5x to 2x) than the shadow's core tone (e.g., a medium grey like #E2E8F0 or grey-200).
  • Effect: The border defines the physical boundary of the card, while the shadow provides the depth. Together, they make the component "pop" with much higher clarity than using either alone.

Subtle Gradients for Depth

Gradients can be used to bring "liveliness" to an interface and reinforce the sense of elevation.

  • The Lighting Metaphor: A subtle linear gradient (top-to-bottom) that is slightly lighter at the top mimics natural overhead lighting. This makes a surface feel more physical and elevated than a flat fill.
  • The 5% Rule: Keep the gradient extremely subtle. A change in lightness of only 2–5% between the top and bottom is usually enough. If the user can easily see where the gradient starts and ends, it is likely too heavy.
  • Usage: Apply to primary buttons, hero cards, and header sections to improve visual hierarchy and brand personality.

Pairing Elevation with Border-Radius

Border-radius and shadow work together to define the character of a surface. The combination signals the element's role and the product's visual tone.

SurfaceShadowBorder-RadiusTone
Inline chip / tagnone--radius-full (pill)Flat, lightweight
Card--shadow-sm--radius-md (8–12px)Graspable, contained
Dropdown / popover--shadow-md--radius-md (8px)Floating, contextual
Modal / dialog--shadow-lg--radius-lg (12–16px)Prominent, focused
Toast / notification--shadow-md--radius-mdEphemeral, above content
Buttonnone or --shadow-xsconsistent across all buttons — see below

Border-Radius Consistency Rule

Button border-radius must not vary within a product. All buttons — primary, secondary, destructive, ghost — use the same radius token. Varying radius between button types breaks visual consistency and implies a semantic difference that does not exist.

/* Correct: one radius for all buttons */
.btn { border-radius: var(--radius-button); }

/* Wrong: different radii for different button variants */
.btn-primary { border-radius: 8px; }
.btn-secondary { border-radius: 4px; }  /* ← breaks consistency */

The button radius token is a brand decision — set it once, apply it everywhere.

Text Shadow for Contrast and Separation

text-shadow can lift text off a background without changing colours — useful when contrast is marginal or text sits on a photograph, gradient, or complex background.

The effect must be imperceptible as a shadow. If the user notices the shadow, it is too strong.

/* On images or complex backgrounds */
.hero-title {
  text-shadow: 0 1px 3px rgba(0, 0, 0, 0.25);
}

/* Very subtle separation from a near-matching background */
.label-on-tinted-surface {
  text-shadow: 0 1px 2px rgba(0, 0, 0, 0.12);
}

/* White text on light background — use a dark shadow, not white */
.inverted-text {
  text-shadow: 0 1px 4px rgba(0, 0, 0, 0.30);
}

Rules:

  • Opacity: stay below 0.30 — above that it reads as a design choice rather than a refinement
  • Blur: 2–4px maximum — higher values make text feel dirty
  • Offset: 0 1px or 0 0 — directional offsets above 2px look like retro Web 2.0
  • Never use text-shadow to compensate for a contrast failure — fix the colour first. Use it only when colours are already close to passing and a nudge is needed, or when text sits on unpredictable imagery

Dark Mode Shadows

Shadows are less visible on dark backgrounds. On dark surfaces, compensate with:

  • Slightly higher opacity on shadow values
  • Adding a subtle border (1px solid rgba(255,255,255,0.08)) to define card edges
  • Increasing the elevation level by one step for the same perceived depth

Review Checklist

  • Is there a defined elevation scale as design tokens (not one-off shadow values per component)?
  • Does each elevated element use the correct level for its role (card ≠ modal)?
  • Are shadows light and diffuse, avoiding heavy black (#000) defaults?
  • For white cards on light backgrounds, is the shadow paired with a 1px border for better definition?
  • Is border-radius consistent across all button variants?
  • Do shadows feel subtle and diffuse rather than heavy and dark?
  • On dark surfaces, are card/panel edges visible through border or adjusted shadow?
  • Is elevation used to communicate layering — not just decoration?
  • If gradients are used, are they subtle (2–5% lightness change) and used to reinforce the lighting/elevation metaphor?

Common Anti-Patterns

Anti-patternProblemFix
Different border-radius on primary vs secondary buttonsImplies semantic difference that doesn't existSingle --radius-button token for all buttons
Heavy box-shadow: 0 8px 16px rgba(0,0,0,0.4)Feels dated and visually aggressiveUse low-opacity, multi-layer diffuse shadows
Shadow on every element regardless of roleElevation loses meaning when everything is elevatedReserve shadow for genuinely floating elements
Flat cards with no elevation on a white backgroundCard edge disappears into the pageUse --shadow-sm or a 1px border to define the card boundary

平台分布

Codex

33.55%
按下载量换算76

Claude

31.36%
按下载量换算71

Cursor

17.54%
按下载量换算40

Gemini CLI

9.67%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills