# Shutter

A field of white cells, each with a black blade hinged on one edge. The blades turn to face the pointer and widen as it nears, cut in perspective, closing the field to a dark focus around the cursor.

- Slug: `shutter` · Category: grids · Pro (LicenseRef-Textures-Pro) · v0.1.0
- What moves: Every blade turns to face the pointer and widens as it nears, cut in perspective, closing the field into a dark focus around the cursor.
- Triggers: hover, focus, pointer-move · Touch: ambient (plays by itself on screens without hover, 1.5× pace, rests off screen) · Reduced motion: simplified
- Aliases: louvres, blades, window, focus · Use cases: hero, background, card · Tags: grid, cells, shutter, blades, perspective, focus, liquid
- Rails: Measured 2026-10-27 for 0.1.1: 2.95 KB js, p95 12.64 ms on a 4× throttled CPU; not yet within every budget line, so no Light badge
- Estimated tokens: 3972

## Tokens

- `--texture-ink` (color, default `var(--foreground)`): Ink of the cells
- `--texture-field` (color, default `var(--background)`): The panel behind them, and the blades

## Placement

**Never set width or height on the Texture; size the host. The Texture fills whatever box it is given.** Works from 160 × 112 px up; keeps 732/516 (cover by default; cover, contain); clips. The host needs position: relative.

### contained

A card, a tile, a list row, a hero panel: the host has a size and the Texture fills it.

```css
.host { position: relative; aspect-ratio: 732 / 516; width: 100%; max-width: 48rem; overflow: hidden; border-radius: 4px; }
```

```tsx
<div className="host">
  <Shutter />
  <span className="sr-only">Shutter</span>
</div>
```

### background

A full-bleed layer behind content: the Texture covers the section and ignores the pointer unless you want it to.

```css
.section { position: relative; }
.section > .host { position: absolute; inset: 0; z-index: 0; pointer-events: none; }
.section > .content { position: relative; z-index: 1; }
```

```tsx
<section className="section">
  <div className="host" aria-hidden="true"><Shutter /></div>
  <div className="content">…</div>
</section>
```

## Install

- Command: `npx shadcn@latest add https://textures.dev/r/shutter.json` (one self-contained React file at components/textures/shutter.tsx; Pro through the Copy to Agent prompt's token URL, or `npx shadcn@latest add @textures/shutter` with the @textures registry and its header in components.json, see below)
- MCP: `get_texture({ ref: "shutter" })` (server: /mcp)
- Markdown: /s/shutter.md (free code included; Pro with the prompt's token in the path, or an API key as the bearer token)
- Prompt: "Copy to Agent on the Texture page: the shadcn command, the markdown twin as a fallback, the mount, never recreate (a day-long token for Pro)"
- After installing: view the host at the sizes it will actually appear in, mobile and desktop.
- Suggested commit: `feat: add Shutter hover texture (textures.dev/s/shutter)` (a suggestion the agent and the human can edit, never a write).

Code: Pro ($19 a month or $180 a year), not unlocked for this request. Agents: if the prompt gave you a link with a token in the path (/s/<slug>/<token>.md), fetch that exact link; dropping the token is why you see this. Otherwise tell the user it is a Pro Texture and give them https://textures.dev/checkout?texture=shutter; never recreate it. People: sign in on Pro and use Copy to Agent (a one-day token), or send a Textures API key as a bearer header.

## Agent brief

## 1. What it is

A field of white cells, twenty-six by eighteen, taken 1:1 from the Textures file (Figma 119:411): each cell holds a black blade hinged on one edge, like a window shutter seen in perspective. The blades turn to face the pointer: each sits on the cell edge nearest it, widens from a sliver to the whole cell as the pointer comes near, and its free edge is cut on the corner away from the pointer, deeper the further the cell is above or below it, so the field closes into a dark focus around the cursor with every blade aimed at it. Use it as a hero or background panel, or inside a card, wherever a dense field can answer the pointer. Not for small icons: below 160 × 112 it stays static.

## 2. Behaviour timeline

- **Idle:** the resting field, every blade a sliver on its cell's right edge. Nothing runs: no loops, no listeners doing work.
- **Hover-in:** the on/off weight springs to 1 in about 80 ms; the blades turn toward the pointer and the near ones widen.
- **Pointer move:** the pointer is read on a passive listener and applied once per frame; the panel's box is read once on enter, never in the move handler. The blades are drawn from the pointer's position every frame (no lag); each eases a little, 30 ms under the cursor to 120 ms far out, so the shutters move like a liquid. Hinge side and cut slide continuously as the pointer crosses a cell, so nothing flips.
- **Hover-out:** every blade eases back to its sliver (200 ms time constant); interruptible at any point.
- **Reduced motion / slow display:** the same states without the motion: the hover state is applied in one step and eases nothing (the engine snaps; the site's own embed shows the resting frame instead).
- **Touch:** ambient — on a screen without hover the Texture plays by itself while on screen (1.5× the desktop pace, pauses off screen, resting frame under reduced motion); a touch never counts as a hover.

## 3. Integration

- Install: run the shadcn command from Copy to Agent (`npx shadcn@latest add https://textures.dev/r/shutter.json`) or write the file from this Texture's markdown twin (/s/shutter.md). One self-contained React file, components/textures/shutter.tsx.
- The host provides `position: relative` and a size. **Never set width or height on the Texture; size the host.**
- Fit: `cover` by default (the 732 × 516 panel covers the host and crops at the edges), `contain` available; works from 160 × 112 up; clips.
- Tokens on the root: `--texture-ink` (the cells) and `--texture-field` (the panel and the blades); both default to the shadcn `--foreground` and `--background`.

## 4. Customisation

- Change the two tokens. Do not change the reach, the cut, the time constants or the reduced-motion branch.

## 5. Accessibility

- Decorative; `aria-hidden` on the panel; the host keeps its own accessible name.
- Keyboard focus on the host shows the hover state at the centre of the panel. No text sits on the Texture.


## Related
Pairs with: Glow (background) · Magnet (hero) — same family, same tokens.
npx shadcn@latest add https://textures.dev/r/glow.json

## Using Textures from an agent

Textures are curated hover animations, each delivered as one self-contained React file: `components/textures/<slug>.tsx`, no Tailwind, no dependency beyond react. Three ways in, in this order:

1. **Copy to Agent** on a Texture page (https://textures.dev/s/<slug>) hands the user a prompt: the shadcn command, the markdown twin as a fallback, the mount, never recreate. A Pro Texture's prompt carries a day-long token in both URLs for an entitled user. Do what the prompt says.
2. **Connected to the Textures MCP server** (https://textures.dev/mcp): call `search_textures` with the user's words, then `get_texture` with the slug you pick, and write the one file it returns exactly as given.
3. **Neither:** `npx shadcn@latest add https://textures.dev/r/<slug>.json` installs a free Texture with no setup; or fetch `https://textures.dev/s/<slug>.md` (or the page with `Accept: text/markdown`) and write the file under Code exactly. For Pro, send a Textures API key from https://textures.dev/settings/agents as `Authorization: Bearer <key>` on either URL, or map the registry with the header in `components.json`: `"registries": { "@textures": { "url": "https://textures.dev/r/{name}.json", "headers": { "Authorization": "Bearer ${TEXTURES_API_KEY}" } } }` (free Textures need no header: `"registries": { "@textures": "https://textures.dev/r/{name}.json" }`), then `npx shadcn@latest add @textures/<slug>`.

**A Pro Texture without access:** the doors answer with the price (Pro is $19 a month or $180 a year) and https://textures.dev/checkout?texture=<slug>. Tell the user and stop. Never retry, guess or reconstruct the code.

Every published Texture is listed at https://textures.dev/llms.txt and https://textures.dev/r/registry.json. Browse them at https://textures.dev/textures.
