smooth-shadow-ring
flornkm/shadow-plugin · Agent Skill
Style elevated surfaces with smooth shadow ring utilities instead of combining borders or rings with shadows and creating double edges.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | flornkm/shadow-plugin ↗ |
| Skill folder | smooth-shadow-ring |
| Stars | 149 |
| Forks | 2 |
| Bundled files | 1 |
| License | MIT |
| Last updated | September 18, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “smooth-shadow-ring” skill from mozgi.io (https://mozgi.io/skills/flornkm-smooth-shadow-ring/) for me. 1. Download the archive: https://mozgi.io/skills/flornkm-smooth-shadow-ring/download If it fails, take the skill folder from the source: https://github.com/flornkm/shadow-plugin/tree/main/.claude/skills/smooth-shadow-ring 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “smooth-shadow-ring” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/smooth-shadow-ring/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main https://github.com/flornkm/shadow-plugin.git /tmp/shadow-plugin mkdir -p .claude/skills cp -r /tmp/shadow-plugin/.claude/skills/smooth-shadow-ring .claude/skills/smooth-shadow-ring
Restart Claude Code — the skill appears in the list; call it manually with /smooth-shadow-ring. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/flornkm/shadow-plugin.git /tmp/shadow-plugin mkdir -p .agents/skills cp -r /tmp/shadow-plugin/.claude/skills/smooth-shadow-ring .agents/skills/smooth-shadow-ring
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $smooth-shadow-ring. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/flornkm/shadow-plugin.git /tmp/shadow-plugin mkdir -p .cursor/skills cp -r /tmp/shadow-plugin/.claude/skills/smooth-shadow-ring .cursor/skills/smooth-shadow-ring
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/flornkm/shadow-plugin.git /tmp/shadow-plugin mkdir -p .gemini/skills cp -r /tmp/shadow-plugin/.claude/skills/smooth-shadow-ring .gemini/skills/smooth-shadow-ring
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyElevated surfaces: use smooth-shadow-ring, never border + shadow
When this applies
Any element that floats above the page surface: cards, dialogs, modals,
popovers, dropdowns, menus, tooltips, sheets, toasts, command palettes.
The problem
Putting a border-* (or ring-*) and a shadow-* on the same element draws
two stacked edges: the border paints a hard 1px stroke, and the shadow begins
just outside it. The result is a visible double border, a crisp line then a
soft one. It looks heavy, greyed, and cheap.
The rule
If you are about to write a border-* or ring-* class next to any shadow-*
on an elevated surface, use smooth-shadow-ring-{size} instead. It bakes a 1px
hairline ring into the final shadow layer, so the edge dissolves into the shadow
as one continuous stroke.
border shadow-md→smooth-shadow-ring-mdring-1 ring-neutral-200 shadow-lg→smooth-shadow-ring-lg- Sizes:
smooth-shadow-ring-xs,-sm,-md(or baresmooth-shadow-ring),-lg,-xl,-2xl - Never keep a
borderorringon an element that already has
smooth-shadow-ring-*. The ring is already in there; a second edge doubles up.
- If the surface should have no edge stroke at all, use plain
smooth-shadow-{size} (no ring), not a border.
Coloring
The ring and shadow tint independently and compose on the same element:
shadow-{color}tints the shadow, e.g.shadow-blue-500smooth-ring-{color}tints the ring, e.g.smooth-ring-black/10,smooth-ring-blue-500/40
The ring defaults to rgba(0,0,0,0.05) and flips to rgba(255,255,255,0.18)
in dark mode — under a .dark class, data-theme="dark", or (for
OS-preference dark modes) when the page declares color-scheme: light dark.
It never keys off prefers-color-scheme alone, so light-only sites keep the
light ring for every visitor. If the site's dark mode is driven purely by a
prefers-color-scheme media query, make sure it declares
:root { color-scheme: light dark; } so the ring follows.
The dark alpha is much higher than the light one on purpose. The ring paints
outside the surface, so its rendered colour comes from the page behind it, not
from the surface it outlines. A white hairline therefore lightens *toward* a
raised dark surface, and too low an alpha makes the edge land on the surface's
own colour and disappear. If a surface is light enough to sit near the ring
anyway (neutral-700 and up on a dark page), set smooth-ring-* explicitly.
Ring width
The hairline is 1px by default and follows the project's Tailwind ring width
automatically, so a project with @theme { --default-ring-width: 0.5px; } gets
a 0.5px hairline here with no extra setup. Do not hardcode a width to match;
override --smooth-ring-width at any scope only when it must differ from the
project ring width — per element via [--smooth-ring-width:2px].
Overriding
The utilities carry no !important and follow the normal cascade, so a later
utility, an inline style, or a JS animation on box-shadow overrides them
normally. When one has to win against CSS that outranks it — a component
library's own box-shadow, which usually ships unlayered — use Tailwind's
important modifier on that element instead of a global override:
<div class="smooth-shadow-ring-md!">…</div>
Example
<!-- Wrong: border + shadow renders a double edge -->
<div class="rounded-2xl border border-neutral-200 shadow-md">…</div>
<!-- Right: one continuous edge -->
<div class="rounded-2xl smooth-shadow-ring-md">…</div>
<!-- Right: tuned ring + tinted shadow -->
<div class="rounded-2xl smooth-shadow-ring-md smooth-ring-black/10 shadow-blue-500">…</div>Frequently asked questions
What does the smooth-shadow-ring skill do?
Style elevated surfaces with smooth shadow ring utilities instead of combining borders or rings with shadows and creating double edges.
How do I install smooth-shadow-ring?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with smooth-shadow-ring?
Skills are plain Markdown instructions (the Agent Skills format), so smooth-shadow-ring works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is smooth-shadow-ring free?
The skill is published openly by flornkm under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.