Material System

Give a site one material — a short block in design.md that fixes its metal, field, glass, and depth settings from the brand's tokens — and a surface map that says which route carries the one GPU surface and why. Use when planning shaders, glass, liquid-metal marks, or 3D across a whole site or several sites; when asked how the liquid-logo, shader-backdrop, liquid-glass, and r3f-scene recipes fit together; when a brand wants a signature look that is consistent between its website, Open Graph images, and social clips; or before the first GPU surface lands in a repo. Produces a proposal for the b

48 stars 6 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add frankxai/claude-skills-library

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add frankxai/claude-skills-library --skill material-system
Manual install
git clone --depth 1 https://github.com/frankxai/claude-skills-library.git /tmp/claude-skills-library
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills-library/packs/web-excellence/skills/material-system ~/.claude/skills/material-system

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Material system

Four recipes can each make a good surface. Used one request at a time they
make four unrelated effects. This skill decides once, per site, what the
brand's material is and where it appears, so every later surface is a reading
of the same few numbers.

It writes two short things into the repo and builds nothing itself:

1. a **Material block** in `design.md`: the settings every recipe reads
2. a **surface map**: which route has a surface, which kind, and its job

Both change how the brand looks. Draft them as a proposal with rendered
examples and get the brand owner's approval before either lands in `design.md`.

## 1. Read before proposing

- `design.md`, `taste.md` (either case), the Tailwind config or token file.
  Quote every line about gradients, glass, 3D, canvas, and motion.
- What already renders: `grep -rnE "<Canvas|ShaderMount|@paper-design/shaders|@react-three/fiber" app components`.
- `node .claude/skills/web-steward/peer-check.mjs --root .` An unmet peer
  under an existing scene is fixed before anything is added.

A taste file that refuses decorative gradients, glass stacks, or 3D has
already answered part of this. Leave those rows of the block as `none` and
say which line decided it. For some sites the right material is paper and
type, and the whole block is `none`.

## 2. The Material block

Add it to `design.md` under its own heading. Every value is a token name or a
number; no raw colour that is not already a token.
Read the full skill on GitHub

Details

Skill name
material-system
Path
packs/web-excellence/skills/material-system/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Material System skill do?

Give a site one material — a short block in design.md that fixes its metal, field, glass, and depth settings from the brand's tokens — and a surface map that says which route carries the one GPU surface and why. Use when planning shaders, glass, liquid-metal marks, or 3D across a whole site or several sites; when asked how the liquid-logo, shader-backdrop, liquid-glass, and r3f-scene recipes fit together; when a brand wants a signature look that is consistent between its website, Open Graph images, and social clips; or before the first GPU surface lands in a repo. Produces a proposal for the b

How do I install the Material System skill?

Claude Code plugin: /plugin marketplace add frankxai/claude-skills-library. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Material System popular?

It lives in frankxai/claude-skills-library, which has 48 GitHub stars and 6 forks.

Related skills

Acos Meta

48

frankxai/claude-skills-library

ACOS self-description and configuration skill. Documents how ACOS works, how to extend it, how to add new skills/commands/agents, and how to debug the hook system. Use when building new ACOS capabilities, understanding the system architecture, or onboarding to ACOS for the first time.

Software Development

Acos Visual Gen

48

frankxai/claude-skills-library

Generate research-grounded visuals using the InfoGenius pipeline. Use when creating infographics, diagrams, educational visuals, or any image that benefits from factual accuracy. Supports 8 visual styles (3D, technical, minimalist, photorealistic, futuristic, vintage, cartoon, standard) and 4 audience levels.

Images, Video & Audio

Agent Harness Construction

48

frankxai/claude-skills-library

Shape an agent's tools, observations, and recovery without adding a second coordinator. Use when defining a tool, a skill, a hook, or a worktree lane.

AI, LLMs & Agents

Next Best Practices

43

0xranx/agentbrief

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Frontend & Design

Lottie

48

frankxai/claude-skills-library

Lottie and dotLottie adapter patterns for HyperFrames. Use when embedding lottie-web JSON animations, .lottie files, @lottiefiles/dotlottie-web players, registering instances on window.__hfLottie, or making After Effects exports deterministic in HyperFrames.

Frontend & Design

Nextjs

48

frankxai/claude-skills-library

Next.js 15+ App Router development patterns including Server Components, Client Components, data fetching, layouts, and server actions. Use when creating pages, routes, layouts, components, API route handlers, server actions, loading states, error boundaries, or working with Next.js navigation and metadata.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.