Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add khadinakbarlabs/shopify-app-builder --skill ux-empty-error-statesgit clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/ux-empty-error-states)<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/ux-empty-error-states"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/ux-empty-error-states/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/khadinakbarlabs/shopify-app-builder/ux-empty-error-states"><img src="https://agentmods.dev/badge/skills/khadinakbarlabs/shopify-app-builder/ux-empty-error-states.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00135 | $0.06441 |
| Opus 5 | $0.00068 | $0.03220 |
| Sonnet 5 | $0.00027 | $0.01288 |
| Haiku 4.5 | $0.00014 | $0.00644 |
Grade A, and why
ux-empty-error-states scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 659 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Empty, Loading & Error State UX for Shopify Polaris Apps
A practical, opinionated reference for the three states that make or break a Shopify embedded app: when there's nothing yet, when something is on its way, and when something went sideways. Pulled from Polaris docs, Remix pending UI docs, and real-world patterns.
1. EmptyState — when, how, and what to put inside
What it is
EmptyState is Polaris' purpose-built component for "this page/section is empty." It composes a centered illustration, a heading, optional body text, and a primary action (and optional secondary action). It is intended for whole-page-empty experiences, not tiny empty slots inside a card sidebar.
When to use it
Use EmptyState when:
- A list/table/chart has zero rows for first-time merchants (no products, no orders, no campaigns).
- A filtered/searched view returns zero matches (different copy, same component).
- A feature requires setup before it can be used (no connected account, no plan selected).
- A merchant landed on a page that needs onboarding context before they can act.
Do not use EmptyState for:
- Small empty slots inside a
Cardwhere a simple "No notes yet" sentence is enough. - Form fields that aren't filled in — that's just normal state.
- Loading. Use
SkeletonPageinstead. - Errors. Use a
Banner(or a full-page error view) instead.
Anatomy
import { EmptyState, Page } from "@shopify/polaris";
<Page>
<EmptyState
heading="Manage your inventory transfers"
action={{ content: "Add transfer", onAction: () => navigate("/transfers/new") }}
secondaryAction={{
content: "Learn more",
url: "https://help.shopify.com/manual/inventory/transfers",
external: true,
}}
image="https://cdn.shopify.com/s/files/.../empty-state.svg"
>
<p>Track and receive your incoming inventory from suppliers.</p>
</EmptyState>
</Page>
Content rules
- Heading — a friendly sentence fragment, not a label. "Manage your inventory transfers," not "Transfers."
- Body — one or two sentences. Explain the value, not the mechanism.
- Primary action — verb-first, the single most important thing they can do. "Add transfer," "Import products," "Connect Stripe."
- Secondary action — almost always a "Learn more" link to Shopify docs or your own help article. Use
external: trueand the new-window icon will render. - Image — a Polaris illustration or your own brand-consistent SVG. ~400×250px works well. Polaris recommends ~40px of white space above when nested inside a
CardorModal.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 659 lines · 135 tokens per session scan A f499f6110be9
ux-empty-error-states is a skill published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 6,441 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…
ui-designer
Elite UI/UX Design Lead & Frontend Architect. Generates distinctive, non-templated interfaces with opinionated aesthetics, deliberate typography, and exact UX copy. Triggers on UI design, frontend styling, or layout creation.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.