Knowledge RAG
Submit principleDesign Knowledge Base
Community-maintained principles reviewed before publication and retrieved as Agent design constraints.
4 published principles / 192 in library
Resource Licensingillustration / empty-state
Friendly Asset Governance for Empty States
Illustrations, emoji, and Lottie can make empty states friendlier, but they must first serve reason, next action, license record, alt text, and reduced-motion.
Friendly assets are not the main actor in an empty state. They reinforce tone, reduce anxiety, or aid understanding; the real interface value is clear reason, next action, and legally reusable asset metadata.95%Interaction Responsive Motionempty-state / recoveryEmpty State Recovery Contract
Empty states should explain system status and cause before offering an action that resolves that cause, instead of filling silence with illustration.
An empty state is completed system feedback: users need to know why content is absent, whether the request has finished, what they can do, and whether access, configuration, retry, or waiting is required.90%Design Systems Page Patternsempty-state / projectsEmpty Project Start State
Empty Project Start State turns a frequent interface judgment into an executable constraint before generation.
An empty project page should move users toward the first real outcome, not explain product features.85%Visual Foundationsempty-state / onboardingEmpty State Composition
Empty State Composition turns a frequent interface judgment into an executable constraint before generation.
An empty state is not illustration filler; it is the first step into the workflow.84%