Individual skill

postcss-pro

Build CSS pipelines with PostCSS: autoprefixer, nesting, custom plugins, and integration with bundlers. Use when processing CSS in modern build setups.

skills/postcss-pro/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 56
Repository last updated: Oct 10, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
ai-agents-automation Repository topic
ai-skills Repository topic
awesome Repository topic
awesome-list Repository topic
chatgpt Repository topic
claude-skills Repository topic
meta-ai Repository topic
muse-ai Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 4,387 bytes

Read excerpt


# PostCSS Pro

A practical guide to PostCSS: the CSS transformation pipeline — autoprefixer, nesting, custom media, import handling, writing your own plugins, and wiring it into Vite/webpack/standalone builds.

## Overview

PostCSS parses CSS into an AST and runs **plugins** that transform it. It's not a preprocessor with its own syntax — it's a pipeline: you compose exactly the transforms you need (vendor prefixes, future CSS, minification, linting). Most projects meet PostCSS through Tailwind (which is a PostCSS plugin) or autoprefixer, but the standalone pipeline is worth understanding.

## When to use

- Autoprefixing and future-CSS features without a full preprocessor.
- Custom CSS transforms (design-token injection, RTL flipping, px→rem).
- CSS minification and optimization in the build.
- Understanding the pipeline under Tailwind or cssnano.