Common Agent Mistakes — AuraGlass by AuraOne

#Do Not Do This

Do not invent component names such as `GlassNavbar` unless the installed package exports that name. Use documented names like `GlassNavigation`, `GlassHeader`, `GlassSidebar`, or the relevant recipe.

Do not import from private paths such as `aura-glass/dist/*`, `src/*`, or this website repository. Public examples should import from `aura-glass`, `aura-glass/styles`, and documented subpaths only.

Do not omit `import 'aura-glass/styles'`. Unstyled components usually mean the setup is wrong, not that the component should be restyled from scratch.

Do not add 3D, media, AI, chart, or realtime peers unless the generated code imports that feature family.

Do not place viewport-oriented components inside cards without containment props. Use `contained`, `compact`, fixed height, and disabled portal toggles when available.

#Bad and Good Examples

Bad examples are usually too bare or too magical: a nonexistent component, no stylesheet, no data, no client boundary, or a heavy peer installed without explanation.

Good examples use valid imports, state where the stylesheet belongs, provide realistic props, and describe any optional peer or client-boundary requirement.

Bad import

import { GlassNavbar } from 'aura-glass';

Good navigation

import { GlassNavigation, GlassHeader, GlassSidebar } from 'aura-glass';

Bad setup

Render components but omit the stylesheet

Good setup

Import `aura-glass/styles` once in `app/layout.tsx` or `main.tsx`

Bad preview

<GlassSidebar /> inside a fixed-height card

Good preview

#Required Final Report

Agents should finish with a short technical report: changed files, components used, optional peers added, checks run, and any unchecked browser behavior. This makes review concrete and prevents hollow “done” responses.