Menu
popagent
publicLatest change 98a9a832366ede73ff5e61d826d68af4f775db92 - Add safe autonomous deployment and complete project guidance by AkurAI Build
--- name: popagent-ui-verification description: Verify popagent UI behavior, responsive layouts, accessibility, and visual changes in a real browser. Use when changing files under src/ui, UI-facing API contracts, or chat interaction behavior. --- # Popagent UI verification Read `../../../AGENTS_UI.md` and `../../../AGENTS_RULES.md` before testing. Also read `../../../AGENTS_CHANNELS.md`, `../../../AGENTS_BROWSER.md`, `../../../AGENTS_DOCUMENTATION.md`, or `../../../AGENTS_OBSERVABILITY.md` when the changed surface belongs to that domain. 1. Run the narrow unit or helper tests associated with changed files. 2. Run TypeScript checking with `bunx tsc --noEmit`. 3. Start the local app with `bun run dev` when its required services are available; otherwise use the documented Titan instance for authorized live validation. 4. Use the available Playwright/browser automation skill to exercise the affected flow in a real browser. 5. Check both desktop and mobile viewports for responsive changes. Include keyboard focus, dialog close/restore behavior, loading, empty, error, and running states when relevant. 6. Prefer role, label, and visible-text locators. Do not make product code depend on test-only selectors unless semantic locators cannot express the contract. 7. Report the exact paths, viewports, and states exercised. Do not claim visual verification from unit tests alone. Keep screenshots and other generated artifacts temporary unless the repository explicitly needs a committed fixture.