# fluid-design > Viewport-fluid layouts that scale as one drawing. Installs as an agent skill; the same `fluid` CLI also runs by hand (npm or a standalone binary). fluid-design puts a website on one unit. `--fluid` is 1px at your design frame (the artboard: the frame the designer draws in) and grows and shrinks with the window, following whichever axis is tighter: `min(W / base-width, H / base-height)`, floored at 0.58. Read the frame sizes off the design; the defaults are only fallbacks. The desktop frame goes in your `:root` as `--fluid-desktop-base-width` / `--fluid-desktop-base-height` (default 1440×900; for a 1680×1050 frame set 1680 / 1050, or run `fluid init --desktop 1680x1050`), the phone frame as `--fluid-phone-base-width` (default 390; a 402-wide iPhone 16 Pro frame is 402). `--fluid-desktop-container-width` (default 1680, drawn px) caps the content box and `--fluid-desktop-container-padding` (default 80) is the side margin; changing the gutter later is that one setting. Every drawn number is written as number × unit (`lg:fluid-py-120` in Tailwind v4, `calc(120 * var(--fluid))` in CSS, `fd.fluid(120)` in SCSS, `fluid(120)` in StyleX), so the page is pixel-exact at the design frame and a proportional copy on every other window: a section drawn 900 tall is exactly one screen when height is the tighter axis. To follow the width only, set `--fluid-desktop-fit-height: 0`: a short laptop then shows the design at full size and scrolls, and a wide, short monitor fills its width instead of leaving side margins. Keep the default (1) for sections drawn to fill one screen. The mobile bands always follow the width only. Status: tested on Next.js only. The scale was built and tuned on a production Next.js (App Router) + Tailwind v4 site; the other stacks (CSS, SCSS, StyleX) and frameworks (Vite, Astro, plain HTML) generate correctly and pass the pack's tests and examples, but no production site runs on them yet. Bands are ranges of window sizes, each scaling its own design: phone (390 frame), tablet (600+), landscape (a phone on its side, 500 tall or less) and desktop (1024+). With no tablet or landscape frame (the normal case) the phone design runs full width with a 32 gutter; set `--fluid-tablet-container-width: 560; --fluid-tablet-container-padding: 24;` (same for `landscape`) for a centred phone column instead. The container padding never drops below the safe-area inset, so a landscape phone under `viewport-fit=cover` clears the notch. Type roles (`--fluid-display` for headlines, `--fluid-copy` for body and labels, custom roles) shrink less than the layout; damping is how much a role shrinks with it (1 = as much as the layout, 0 = never below its drawn size), and below the desktop breakpoint type holds its size. Role box utilities size a control on its label's role: `fluid-copy-14/20` text in a `fluid-copy-h-56 fluid-copy-px-24` button (`-h`, `-w`, `-size`, `-p`, `-px`, `-py`, `-gap` on every role). `fluid-bleed-x` takes a strip inside a `fluid-container` to the window edges while its content stays aligned (a carousel track). `--fluid-ui` keeps the header and nav usable on short windows. Limits (`fluid-grow-until-1680`, `fluid-shrink-until-1280`, `fluid-ui-grow-until-1680`, `fluid-off`) stop part of a page from scaling and make it a scope (part of the page with its own settings). Structure (which rules exist) lives in a small `fluid.config.json`; change it and regenerate. Settings (the 43 numbers) are CSS variables with registered defaults in your own `:root`; they apply live. `fluid settings` lists every one with its default; `output.editor: true` also writes VS Code autocomplete (`fluid.css-data.json`) and `settings.reference.css`. `fluid init` adds a `"fluid": "npx fluid-design-cli@2"` npm script, so a team and CI run `npm run fluid -- check` without the skill. The CLI: `init`, `generate`, `check`, `settings`, `explain` (with `--url` for a live-page verdict: OK / STALE / MISMATCH / V1 / MISSING), `probe`, `migrate`, `calc`, `verify`, `audit`. It contains no animation. Claude Code is the reference host; it's plain Agent Skills format (agentskills.io), so it installs on Codex, Cursor, Antigravity, opencode, Grok Build, and Hermes too. ## Install - npm/skills.sh: `npx skills add gabros20/fluid-design-skill` - Clone + installer (per-host targets: claude | codex | cursor | antigravity | opencode | grok | hermes | agents | all): `git clone https://github.com/gabros20/fluid-design-skill && cd fluid-design-skill && ./install.sh codex` - Manual copy: `cp -R skills/fluid-design ~/.claude/skills/fluid-design` - The CLI in a Node project, no install: `npx fluid-design-cli@2 init` - The CLI without Node: `curl -fsSL https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/install-cli.sh | sh` (Windows: `install-cli.ps1`), then `fluid init` ## Docs - [README.md](https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/README.md): overview, install, workflow, and repository map. - [skills/fluid-design/SKILL.md](https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/skills/fluid-design/SKILL.md): runtime router, universal invariants, workflow, artifact contract, and completion gates. - [docs/installation.md](https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/docs/installation.md): installation and verification by client. - [docs/usage.md](https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/docs/usage.md): the by-hand guide: init, tuning, generate --watch, CI, explain and verify. - [docs/recipes.md](https://raw.githubusercontent.com/gabros20/fluid-design-skill/main/docs/recipes.md): representative starting prompts and setups. ## Reference inventory (`skills/fluid-design/references/`) - `preflight.md` — the decisions to settle before any code (stack, design frames, bands, container, roles), each with a default and a detection hint. Always first. - `config.md` — generated: every `fluid.config.json` key and every `--fluid-*` setting with its default. - `fluid-scale.md` — the model and maths of the base unit: drawn number × unit, the two axes, precision, the design frame, the ceiling, settings vs structure. - `units.md` — type roles and damping (where type holds its size), the ui unit, the header height, the container units, adding a role. - `bands.md` — phone, tablet, landscape and desktop: switches, continuity, full width by default, a designed tablet. - `limits-and-scopes.md` — one scale per page; limits (a part stops scaling at a window width) and scopes (a part with its own settings). - `browser-zoom.md` — WCAG 1.4.4: the head script, CSP, detection, the mobile handover. - `contract.md` — the checked vocabulary: browser floor per stack, utilities and band variants, SCSS/StyleX API, `fluid.ts` exports, what motion code reads. - `section-recipe.md` — the per-section checklist and shipped anatomy. - `frame-and-gutter.md` — the container: one box, the content budget, `cqw` escapes. - `typography.md` — choosing a type unit by what its box does, `/lh`, `em` tracking, fonts, browser zoom. - `media.md` — images, inline SVG and `