Minimal CSS for semantic HTML, rewritten in plain modern CSS.
Write the markup, get a clean, accessible, themeable page. No classes required, no JavaScript.
Pico Reforged is an independent fork of Pico CSS v2.1.1 (MIT). It is not affiliated with or endorsed by the Pico CSS project. The Pico CSS name and logo belong to their authors.
Pico Reforged continues Pico CSS v2.1.1, the final upstream release, which is MIT licensed and archived. Pico CSS and its original design are the work of Lucas Larroche and the Pico contributors. This project is a fork with its own name. It is not the official Pico CSS and is not affiliated with it. The Pico CSS name and logo belong to the original project.
It is a drop-in for v2.1.1 markup with a modern default look. The classes, attributes and --pico-* variables of v2.1.1 are kept, and the CDN file names in css/ are the same, so most pages work by changing one URL.
- A modern default look: a 16px root, 42px controls, 8px corners, a 1px ring instead of heavy shadows, a near-neutral dark scheme, tonal secondary buttons and solid focus outlines. Field borders and focus rings reach 3:1 in every theme. See ADR 0002.
- Plain CSS source in
src/, no Sass. Cascade layers (pico.tokens,pico.theme,pico.core,pico.extras,pico.utilities), so your own CSS wins without!important. - OKLCH colors and
light-dark(). Light and dark are written once. - The same 20 themes, plus custom themes from a single color.
- Opt-in extras for apps: tabs, alert, toast, badge, avatar, skeleton, app shell, data table, pagination, stepper and empty state.
- Popover and anchor positioning patterns, animated dialogs and accordions. The old markup still works.
- A compiler and CLI for custom bundles, scoping, classless builds and purging unused CSS.
- Vite and PostCSS integrations that purge unused rules in production, safely by default.
- An opt-in
moderntarget (Chrome and Edge 123, Firefox 128, Safari 17.5) that ships native nesting andlight-dark()for a smaller file. - Files for AI agents:
llms.txton the site, an agent skill,AGENTS.md, a component manifest and DTCG design tokens. - Size: the minified
pico.min.cssis 84.2 kB raw, 12.5 kB gzipped and 11 kB with brotli. v2.1.1 minified is 83.3 kB, 11.7 kB and 10.1 kB, so the raw file is 1% larger and the compressed file 7% to 9% larger, with the popover and anchor positioning patterns, forced colors support and the new look included. The classless file is 73.9 kB raw against 71 kB, 11.4 kB gzipped against 10.3 kB. Details are in docs/architecture.md.
npm install @rusticstack/pico-reforged
# or
pnpm add @rusticstack/pico-reforgedLink a built file from node_modules/@rusticstack/pico-reforged/css/ or use the CDN:
<link
rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/@rusticstack/pico-reforged@2.0.1/css/pico.min.css"
/>The files in css/ use the same names as v2.1.1:
| File | What it is |
|---|---|
css/pico.min.css |
the full build, azure theme |
css/pico.<theme>.min.css |
the full build in one of the 20 themes |
css/pico.classless.min.css |
classless |
css/pico.classless.<theme>.min.css |
classless in one theme |
css/pico.conditional.min.css |
scoped to .pico, class build |
css/pico.classless.conditional.<theme>.min.css |
scoped to .pico, classless |
css/pico.fluid.classless.min.css |
classless with a full width container |
css/pico.colors.min.css |
color and background utility classes |
css/pico.extras.min.css, css/extras/<name>.min.css |
the opt-in extras (all of them, or one) |
Every file also has an unminified version without .min.
With Vite or Next.js you can import the package once in your CSS and get a purged stylesheet in production, see Build integrations.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" href="css/pico.min.css" />
<title>Hello</title>
</head>
<body>
<main class="container">
<h1>Hello, world</h1>
<button>Click me</button>
</main>
</body>
</html>More pages are in examples/. Run pnpm build once, then open them in a browser.
The classless build styles the elements and needs no classes. body > header, body > main and body > footer become the centered container.
<link rel="stylesheet" href="css/pico.classless.min.css" />The conditional build only styles what is inside .pico, so Pico can live next to other CSS:
<link rel="stylesheet" href="css/pico.conditional.min.css" />
<section class="pico">...</section>Pick a theme by file name, for example css/pico.jade.min.css. The themes are amber, azure, blue, cyan, fuchsia, green, grey, indigo, jade, lime, orange, pink, pumpkin, purple, red, sand, slate, violet, yellow and zinc.
Dark mode follows the system by default. Force it with data-theme on any element:
<html data-theme="dark"></html>Make a theme from one color with the CLI:
npx pico-reforged build --theme "#e5484d" --minify --out public/pico.cssSee docs/customization.md for variables, layers, scoped builds and a runtime theme with relative colors.
Extras are separate and never part of pico.css. They use semantic HTML and ARIA, so there are no classes to learn.
<link rel="stylesheet" href="css/pico.min.css" />
<link rel="stylesheet" href="css/pico.extras.min.css" />Or load one: css/extras/tabs.min.css. The extras are tabs, alert, toast, badge, avatar, skeleton, app-shell, data-table, pagination, stepper and empty-state. examples/dashboard.html uses several of them.
npx pico-reforged build --theme jade --extras tabs,badge --minify --out pico.css| Command | What it does |
|---|---|
pico-reforged build [options] |
compile one stylesheet |
pico-reforged matrix [outDir] |
write the full file set, default css |
pico-reforged purge <outDir> |
remove unused Pico rules from a built site |
pico-reforged themes |
list the built-in themes |
pico-reforged modules |
list the modules that can be excluded |
pico-reforged extras |
list the opt-in extras |
Run pico-reforged --help for every build option (--no-classes, --scope, --exclude, --fluid, --purge, --targets and more).
Import the package once in your CSS. In production the plugin scans your project and keeps only the rules you use.
// vite.config.ts
import { defineConfig } from "vite";
import pico from "@rusticstack/pico-reforged/vite";
export default defineConfig({ plugins: [pico()] });/* src/app.css */
@import "@rusticstack/pico-reforged";
@pico {
theme: jade;
extras: tabs badge;
}Next.js uses the PostCSS plugin, @rusticstack/pico-reforged/postcss. Purging is safe by default: a rule is dropped only when a class, an id or an attribute name it needs is nowhere in your sources, so components, routers and scripts cannot lose a style they need. purge: aggressive also judges tags and attribute values and saves more, but needs @source or a safelist for markup that only exists at run time. Static site generators can run pico-reforged purge <outDir> on the built folder.
Setup for Vite, Astro, SvelteKit, Nuxt, Next.js and static generators is in docs/integrations.md. Working configs are in examples/vite and examples/next.
The ready-made files are already small, and a build can make yours smaller:
- The minified files merge sibling selectors into
:is()(only when specificity stays the same) and write each OKLCH color with the shortest digits that give the same 8-bit sRGB value. - With the Vite or PostCSS plugin, unused rules are dropped. On the example Vite app (
examples/vite, jade theme and the badge extra, minified, counting only the Pico part of the stylesheet) the default safe purge takes it from 81,642 to 65,564 bytes, about 20% less, andpurge: aggressiveto 33,311 bytes, about 59% less. A page that uses more of Pico drops less: on the kitchen sink test page safe saves about 1%. --targets modern(ortargets: "modern"in the config) skips the lowering for older browsers:pico.min.cssdrops to 75.7 kB raw and 10.8 kB with brotli, classless to 66.2 kB and 9.9 kB.- When you host the files yourself, precompress them with brotli at quality 11. Most CDNs compress on the fly at a lower level, which costs about 1 kB more.
Chrome and Edge 111, Firefox 128 and Safari and iOS Safari 16.4, the same floor as Tailwind CSS v4. There is no legacy build. Newer features (popover, anchor positioning, @starting-style) are additive and degrade to a working page. Details are in docs/browser-support.md.
Most pages work by swapping the CDN URL. The changes that matter (the browser floor, Sass settings and the new default look, with a block of variables that brings most of the v2.1.1 look back) are in docs/migration.md.
AGENTS.md is the guide for coding agents working on this repository. Agents writing pages that use Pico Reforged should read skills/pico-reforged/SKILL.md, which also ships in the npm package. ai/ holds the component manifest and the design tokens as JSON, and the site serves llms.txt and llms-full.txt.
- Site: pico.rusticstack.com, source in rusticstack/pico-reforged-website
- Docs: architecture, integrations, customization, migration
- Issues: github.com/RusticStack/pico-reforged/issues, questions and ideas in discussions
- Contributing: .github/CONTRIBUTING.md, code of conduct, security policy
Pico Reforged is an independent fork of Pico CSS v2.1.1 (MIT). It is not affiliated with or endorsed by the Pico CSS project. The Pico CSS name and logo belong to their authors.
MIT. Copyright (c) 2019-2024 Pico (Lucas Larroche and contributors), copyright (c) 2026 rusticstack.
