Agent skill

Gradient

by bergside in bergside/awesome-design-skills

Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

MITAuto-check passedFrontend & Design

Install Gradient

skills CLI
$ npx skills add bergside/awesome-design-skills --skill gradient -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bergside/awesome-design-skills gradient --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bergside/awesome-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/gradient .claude/skills/gradient && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gradient
GitHub stars
3.1k
Used in
1 other repo
Token cost
~868 tokens
SKILL.md length
383 words
Files
2
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

  • Works in 6 steps: Restate the design intent in one… → Define tokens and foundational… → Specify component anatomy, states,… → …
  • Tasks that involve Accessibility
  • SKILL.md covers Mission, Brand, Style Foundations and Accessibility, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gradient is an agent skill from bergside/awesome-design-skills. Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `DESIGN.md`).

It sits in Frontend & Design, covering Accessibility. The repository describes itself as: List of 67 awesome DESIGN.md and SKILL.md design skill files for agentic tools like Claude Design, Google Stitch, Codex, Cursor, and other AI tools. The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility

Example prompts

  • “/gradient”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.

What it can do on your machine

Read from SKILL.md and the folder at commit f631a09. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gradient loads about 868 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 383 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~868

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bergside/awesome-design-skills at commit f631a09, republished under its MIT licence (© bergside). 383 words, ~868 tokens.

Download SKILL.mdSave it as .claude/skills/gradient/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gradient
description
Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.
license
MIT
metadata.author
typeui.sh
<!-- TYPEUI_SH_MANAGED_START -->

Gradient Design System Skill (Universal)

Mission

You are an expert design-system guideline author for Gradient. Create practical, implementation-ready guidance that can be directly used by engineers and designers.

Brand

Gradient design style

Style Foundations

  • Visual style: modern, playful
  • Typography scale: 12/14/16/18/24/30/36 | Fonts: primary=Montserrat, display=Space Grotesk, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#990FFA, secondary=#E60076, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
  • Spacing scale: 8pt baseline grid

Accessibility

WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, 44px+ touch targets

Writing Tone

concise, confident, helpful

Rules: Do

  • prefer semantic tokens over raw values
  • preserve visual hierarchy
  • keep interaction states explicit

Rules: Don't

  • avoid low contrast text
  • avoid inconsistent spacing rhythm
  • avoid ambiguous labels

Expected Behavior

  • Follow the foundations first, then component consistency.
  • When uncertain, prioritize accessibility and clarity over novelty.
  • Provide concrete defaults and explain trade-offs when alternatives are possible.
  • Keep guidance opinionated, concise, and implementation-focused.

Guideline Authoring Workflow

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.
Show full SKILL.md (159 more words)Show less

Required Output Structure

When generating design-system guidance, use this structure:

  • Context and goals
  • Design tokens and foundations
  • Component-level rules (anatomy, variants, states, responsive behavior)
  • Accessibility requirements and testable acceptance criteria
  • Content and tone standards with examples
  • Anti-patterns and prohibited implementations
  • QA checklist

Component Rule Expectations

  • Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
  • Describe interaction behavior for keyboard, pointer, and touch.
  • State spacing, typography, and color-token usage explicitly.
  • Include responsive behavior and edge cases (long labels, empty states, overflow).

Quality Gates

  • No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
  • Every accessibility statement must be testable in implementation.
  • Prefer system consistency over one-off local optimizations.
  • Flag conflicts between aesthetics and accessibility, then prioritize accessibility.

Example Constraint Language

  • Use "must" for non-negotiable rules and "should" for recommendations.
  • Pair every do-rule with at least one concrete don't-example.
  • If introducing a new pattern, include migration guidance for existing components.
<!-- TYPEUI_SH_MANAGED_END -->

© bergside, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/gradient of bergside/awesome-design-skills.

  • SKILL.md
  • DESIGN.md

Open the folder on GitHubat commit f631a09

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in bergside/awesome-design-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gradient next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gradient compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gradient this skillbergside/awesome-design-skills3.1k1 repos~868Automated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.5k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed
  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.5k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from bergside/awesome-design-skills

All 67 skills in this repo
  • Agentic

    bergside/awesome-design-skills

    Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

    3.1k GitHub starsUsed in 1 repo~991 tokens
    Auto-check passed
  • Ant

    bergside/awesome-design-skills

    Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

    3.1k GitHub starsUsed in 1 repo~956 tokens
    Auto-check passed
  • Artistic

    bergside/awesome-design-skills

    High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

    3.1k GitHub starsUsed in 1 repo~938 tokens
    Auto-check passed
  • Basic

    bergside/awesome-design-skills

    Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

    3.1k GitHub starsUsed in 1 repo~969 tokens
    Auto-check passed
  • Bento

    bergside/awesome-design-skills

    Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.

    3.1k GitHub starsUsed in 1 repo~878 tokens
    Auto-check passed
  • Bold

    bergside/awesome-design-skills

    Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

    3.1k GitHub starsUsed in 1 repo~854 tokens
    Auto-check passed

Questions about Gradient

What does Gradient do?

Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth. Gradient is an agent skill from bergside/awesome-design-skills. Smooth color transitions and gradient-rich surfaces for modern, playful interfaces with visual depth.

When should I use Gradient?

Gradient fits situations like: tasks that involve Accessibility.

How do I install Gradient in Claude Code?

Run `npx skills add bergside/awesome-design-skills --skill gradient -a claude-code`. Or copy the skill folder (skills/gradient in bergside/awesome-design-skills) into .claude/skills/gradient in your project. Claude Code loads it when a task matches its description.

How do I install Gradient in Codex?

Run `npx skills add bergside/awesome-design-skills --skill gradient -a codex`. Or copy the skill folder (skills/gradient in bergside/awesome-design-skills) into .agents/skills/gradient in your project. Codex loads it when a task matches its description.

Can I use Gradient in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bergside/awesome-design-skills --skill gradient -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gradient, .gemini/skills/gradient, .github/skills/gradient and .opencode/skills/gradient in your project.

What does Gradient need to run?

SKILL.md names no scripts, command-line tools or credentials: Gradient is instructions for the agent only.

Does Gradient access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gradient safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gradient use?

Gradient is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gradient use?

About 868 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gradient?

Skills that share tags, products or a category with Gradient: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gradient?

bergside (a GitHub organization) maintains it in bergside/awesome-design-skills, which has 3,081 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on June 28, 2026.

Source: bergside/awesome-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.