# SexyUI

> UI component library and design skill for developers and coding agents. Search first, fetch one component, apply the design rules.

## Find a component (public, no key)
- GET /api/search?q={words}&format=text  -> one line per match: slug | title | category | access. Options: category=, access=free|pro, limit=1-50 (default 10).
- GET /api/categories  -> category names with counts.
- /catalog.json is the full list (large). Prefer /api/search.

## Fetch a component
- GET /api/components/{slug}?format=md  -> source files, dependencies, setup and license as markdown. Smallest response.
- GET /api/components/{slug}  -> the same as JSON.
- GET /api/components/{slug}?fields=meta  -> file paths, byte sizes and dependencies only.
- Free components need no credentials. Pro needs the header Authorization: Bearer {license key}.

## Design skill (public)
- /SKILL.md  -> layout, spacing, sizing and typography rules. Read before writing UI.
- /skill/sizes.md  -> size table for buttons, inputs, cards, navigation, tables, overlays, forms, page sections.
- /skill/review.md  -> measurable pre-ship checklist and fault-to-fix table.
- /skill/tokens.css and /design-tokens.json  -> the scales as CSS variables and JSON.
- /design-rules.csv  -> the rules as a spreadsheet.

## Rules for agents
- Keep the license key in the SEXYUI_KEY environment variable. Never put it in a URL, a file or output.
- Fetch a component only when it is relevant to the task. Keep the license notice with redistributed source.
- 401: ask the user for authorized access. 403: the key was not accepted. 429: wait 60 seconds. 503: retry later.