Choose the Right AuraGlass Component

#Selection Intent Map

Use valid public names before inventing a component. If a user asks for a product surface rather than a single component, compose several components or start from a recipe.

Choose boring, reliable components first. Add 3D, visualizers, or realtime only when the prompt clearly asks for those capabilities.

#Selection Heuristics

For dashboards, prioritize layout and data density: `GlassDashboard`, `GlassSidebar`, `GlassCard`, `GlassDataGrid`, and charts when chart peers are acceptable. For command centers, prioritize keyboard flow: `GlassCommandPalette`, `GlassTabs`, cards, and grids.

For constrained embeds, docs cards, and previews, prefer components that support `contained`, `compact`, `height`, and `maxHeight`. These props prevent viewport-oriented components from escaping their container.

#Example Composition

A good agent-generated composition has enough props to be believable and bounded. Avoid bare `<Component />` examples when the component normally needs data, state, size, or containment.

import { GlassCard, GlassCommandPalette, GlassDataGrid } from 'aura-glass';
import 'aura-glass/styles';

export function AiCommandCenter() {
  return (
    <GlassCard depth="medium">
      <GlassCommandPalette
        open
        contained
        compact
        positionStrategy="inline"
        placeholder="Search agents, jobs, and documents..."
      />
      <GlassDataGrid />
    </GlassCard>
  );
}