← All examples

SaaS Dashboard

App shell, KPIs, and a searchable invoice table — composed from Card, Table, Badge, Input, Avatar, and Progress.

Acme Billing
GP

Overview

Last 30 days · all activity

Revenue

$48,290

+12.4%

Invoices

142

+8 this week

Outstanding

$6,180

3 overdue

Collection rate

94%

Recent invoices

Search by client or invoice ID

Showing 5 of 5 invoices
InvoiceClientAmountStatusDate
INV-1042GP Corp$4,200.00paidApr 28
INV-1041Globex Ltd$1,860.00pendingApr 27
INV-1040Initech$3,500.00paidApr 26
INV-1039Hooli$ 720.00overdueApr 24
INV-1038Stark Industry$9,900.00paidApr 22

Components used

  • Card — KPI tiles (elevated) and table container (outlined)
  • Table — invoice list with hoverable rows
  • Badge — status chips with dot indicator
  • Input + Field — search
  • Avatar — user, with status="online"
  • Progress — collection rate
  • Button — primary action (variant="accent")

Prompt that produces this layout

With @usevyre/ai-context installed in your agent rules, this prompt yields valid component code on the first try:

Build a SaaS dashboard with useVyre:
- App bar with brand + avatar
- Sidebar nav: Overview, Invoices, Customers, Reports, Settings
- 4 KPI cards (Revenue, Invoices, Outstanding, Collection rate)
- Recent invoices table with search input
- Use Card variant="elevated" for KPIs, "outlined" for the table card
- Status badges: paid=success, pending=warning, overdue=danger
Why this matters: Without AI context, agents commonly invent props like variant="blue" or color="primary" that don't exist in useVyre. The context file constrains generation to actual valid props.