Docs

Put a piece in your project.

Every element is one React file styled with Tailwind CSS v4. It uses the shadcn colour tokens, so it picks up your brand. There is no library to depend on and nothing to keep up to date: the code becomes yours.

Install

You need a React project with Tailwind CSS v4. Run the installer in its folder and name the elements you want:

bash
npx finepieces add filmstrip
npx finepieces add booking-steps day-time-picker

It reads your components.json or tsconfig.json to see where components live, writes each element to components/fine-pieces/ and shows you the import. If your project has no cn() helper yet, it adds lib/utils.ts and installs clsx and tailwind-merge with your package manager. Without shadcn colour tokens in your CSS, it adds a neutral set you can change. It asks before it writes anything and never overwrites a file unless you pass --overwrite.

Not sure of a name? List them, or filter by category or platform:

bash
npx finepieces list
npx finepieces list mobile

With the shadcn CLI

Already use shadcn? Every element is also a shadcn registry item:

bash
npx shadcn@latest add https://finepieces.net/r/filmstrip.json

Or add Fine Pieces as a named registry in your components.json once:

components.json
{
  "registries": {
    "@fine-pieces": "https://finepieces.net/r/{name}.json"
  }
}

and add pieces by name:

bash
npx shadcn@latest add @fine-pieces/filmstrip @fine-pieces/booking-steps

Copy by hand

Prefer no command at all? Open an element, go to the Code tab and paste it into your project. The only import is cn() from @/lib/utils, which shadcn adds for you. Without shadcn, this is all it needs:

lib/utils.ts
import { clsx, type ClassValue } from "clsx";
import { twMerge } from "tailwind-merge";

export function cn(...inputs: ClassValue[]) {
  return twMerge(clsx(inputs));
}

Theming

The elements read the standard shadcn tokens: background, foreground, primary, primary-foreground, muted, muted-foreground, card and border. Change them globally, or give one section its own look by setting them on a wrapper:

tsx
<div style={{ "--background": "#F4EDE6", "--foreground": "#2A201B", "--primary": "#5E4134" } as React.CSSProperties}>
  <WordmarkPhoto image="/salon.webp" lines={["Maison", "Lila"]} />
</div>

Every demo on this site works this way. The brands are made up and the photos are stock, so swap in your own content through the props.

Fonts

Body text uses your font-sans. Headings use font-display and a few use font-grotesk. Define them in your theme to get the look on this site; leave them out and the elements simply use your normal font.

app/globals.css
@theme inline {
  --font-display: "Bricolage Grotesque", sans-serif;
  --font-grotesk: "Overused Grotesk", sans-serif;
}

This site uses Bricolage Grotesque for headings, Inter for text, Overused Grotesk as a second display face and Space Mono for numbers. All four are free.

Scroll-driven pieces

Elements like Stage, Shrinking photo and Sticky avatar reviews react to scrolling. They find the nearest scrolling parent by themselves, so they work on the page and inside a scroll box. They take a pinHeight prop, which is the viewport by default. Inside a fixed-height box, pass that height:

tsx
<div className="h-[600px] overflow-y-auto">
  <Stage pinHeight="600px" blocks={blocks} />
</div>

Wheel and drag never get hijacked. The filmstrip only takes the wheel while the pointer is on it, and lets the page scroll on at either end.

Platforms

Each element carries one of three labels. Universal works with mouse, touch and keyboard and adapts to narrow screens. Mobile only is built for the phone, like the tab bar, swipe actions or the story viewer. Desktop only depends on a pointer, like the cursor label; on touch it falls back gracefully but adds little.

Motion and access

Everything moves with one easing, cubic-bezier(.22,1,.36,1), plus a sharper in-out for wipes. Under prefers-reduced-motion the movement is skipped and content shows at once. Controls are real buttons and links, sliders take arrow keys, and menus close on Escape.

With your agent

The registry index lives at /r/registry.json. With the namespace above in your components.json, the shadcn MCP server can browse and add Fine Pieces elements for you. Ask for “the booking steps from fine-pieces” and it knows where to look.

68 elements, free to use in any project.

Browse the elements →