# SexyUI product illustrations

Build the complete product state: a relevant illustration, a clear title, helpful copy and a real next action. Preserve the host product's typography, palette and spacing. Do not add a new visual identity just for an empty state.

## Find and fetch

1. Search `GET /api/search?category=Illustrations&q=project&format=text` on the SexyUI origin. Search the task, such as inbox, search, upload, connection or team.
2. Fetch one package: `GET /api/components/{slug}?format=md`. Pro packages require `Authorization: Bearer $SEXYUI_KEY`. Read the key from the environment and never print, persist or put it in a URL.
3. Use the package's files and retain its original MIT copyright and permission notices. Gravity SVGs are curated adaptations of Gravity UI illustrations, not exclusive SexyUI artwork. Original Product scenes are authored by SexyUI.

## Choose the right package

- Product scenes: original animated light/dark SVG, React state pattern, CSS and editable example copy. No animation runtime required.
- Gravity: static light/dark SVGs in the native amber palette, preserved monochrome alternatives, original upstream SVGs and portable usage instructions. Use as an image in any framework.
- Flowbite 3D: full-color people, collaboration, launch, billing and security scenes with native light/dark SVGs. Retain Themesberg's MIT notice and the included Flowbite credit.
- Need a working control? Search the existing component library for empty-state, upload, form, command, kanban or avatar. Check the exact result and its dependencies before using it.

## Fit the state to the job

Explain the actual state: first use, no results, nothing left to do, permission denied and an error need different copy and actions. A first-use action creates something. A search state clears filters. An access state explains how to request permission. Never imply an action succeeded without confirmation from the app.

Keep the illustration secondary to the title and action. Start at 240–320px wide on desktop and 160–240px on phones. Use the light source on light surfaces and the dark source on dark surfaces. Keep a 4:3 region, the SVG viewBox and its proportions. Do not invert an illustration with a CSS filter.

Use the application's font for state copy. Keep a short title at 20–24px, description at 14–16px, and a real button at least 44px tall on touch screens. Stay on one spacing scale: 8px between text, 24px to the action, 24–32px around the whole state.

SVGs shown next to equivalent text are decorative: use `alt=""` on images, or `aria-hidden="true"` on inline SVG. For an image that carries unique information, give it a concise alternative. Prefer external SVG images if you do not need to manipulate internals. If inlining an SVG multiple times, make clipPath, mask and gradient IDs unique per instance.

Wire the primary action to the real product flow. Implement loading, failure and disabled states. Never ship a button that merely changes its label to pretend that the action happened.

## Extend the original Product scenes style

When a project needs a new scene, use an existing original Product scene package as the reference for geometry and CSS. Draw from that project's actual task, never another vendor's artwork. Keep these shared rules so subsequent scenes belong together:

- Canvas: `viewBox="0 0 480 320"`; centre the subject around (240, 160), keep the useful drawing within x=64–416 and y=40–280. Leave room around the silhouette.
- Composition: one recognisable product object (folder, inbox tray, document, people or service panels), with one supporting object and one meaningful action marker. Use a shallow 5–8° tilt for paper or interface layers. Keep the state copy outside the SVG.
- Geometry: 1.5–2px rounded strokes, 8–14px corners on document and interface shapes, restrained inner detail. Filled small circles can carry a plus or check; never add unrelated stars or decorative confetti.
- Light palette: ink-blue outlines, near-white paper, mist-blue panels, muted sage, copper and rose accents. Give the main object one dominant color with a quieter supporting tone. Dark palette uses deep ink surfaces and brighter matching hues with readable edges. Use the named CSS variables in the reference package; do not apply a blanket invert filter. Monochrome variants remain available when a host product needs them.
- Motion: one small group moves no more than 6–8px, over 4–5 seconds, using transform with a calm ease. A connection can move a small packet. Keep the main object and labels stable. Under `prefers-reduced-motion: reduce`, stop all keyframes.
- Delivery: self-contained SVG and a framework-appropriate wrapper with editable title, description and a real action callback. Avoid external fonts, embedded bitmaps, network calls, animation libraries and repeated SVG IDs. Retain the original notices when adapting a source scene.

Example agent request: “Read the illustration guide, fetch one original Product scene as a style reference, then create a matching illustration for our empty saved-reports state. Use a coordinated ink-blue and sage palette, our existing typography and controls, light and dark surfaces, reduced motion, and connect Create report to our real report editor.”

## Motion and verification

Original scenes include small CSS animations and a `prefers-reduced-motion: reduce` fallback. Keep a useful still composition; no flashing, continuous camera movement or animation necessary to understand the state. Do not add motion to Gravity sources unless it helps explain a real process.

Check the actual screen at 1440px and 390px, and no horizontal page scroll at 360px. Confirm the title and action remain readable, dark sources use the correct background, keyboard focus reaches the action, and reduced motion stops the animation. Use `/SKILL.md` for the rest of SexyUI's layout rules.
