Why Skeleton Loaders Must Mirror Actual Layouts, Not Use Generic Spinners

A skeleton loader is the most lied-to pixel in shipping software. A team will spend two weeks tuning a 200ms API call, then render a gray rectangle in the middle of a card-shaped hole and call it loading UX.

It isn't. It's an admission that the layout wasn't worth thinking about until the data arrived. A spinner — older, louder, more honest — does at least admit it has nothing to show.

Here's the rule we enforce on every async surface across the OTF kit: a skeleton has to mirror the actual layout underneath it. A generic gray box or a centered spinner is worse than showing nothing.

---

This is an excerpt. Read the full post at otf-kit.dev/blog/skeleton-loaders-mirror-the-real-thing — full-stack kits your AI coding agent can actually ship to production. Browse the kits →