Design Projects workspace, autonomous chat and dashboard flows #1844

Open
opened 2026-11-04 23:34:57 +00:00 by jason.woltje · 0 comments
Owner

Owner design request, 2026-11-04: redesign the current Chat/project/thread experience around familiar chat conventions and Jakob's Law. The current screenshots show weak orientation, sparse labels, no visual hierarchy, and session administration preceding the conversation. The goal is autonomous work with clear project context, not user-operated orchestration.

Design only. Use collaborating GPT subagents to establish flows and low-fidelity wireframes, then generate visual design images. No application coding, scaffolding, dependency changes, PRD edits, policy/schema changes, deployment or live operations.

Owner requirements: rename Chat area to Projects; section-dependent sidebar; expandable projects with active agent sessions; customizable item display; clicking a project opens its dashboard. Dashboard provides project context/settings, KPI bar for active/stalled/finished agents, changes, total/open PRs, uncommitted data, and useful additional metrics; clickable project issues and direct north-star/PRD access. PRD changes alert agents. Preserve a room-wide message/command with explicit audience. Use familiar chat layout, strong labels/breadcrumbs, and put advanced session/recovery management out of the primary path.

Start with supplied Mosaic/T3/Desktop screenshots. Mobbin MCP is not connected yet; owner will configure it at the homelab. Do useful initial design now; mark later research and unimplemented capabilities honestly. Wireframes should cover project dashboard, agent conversation, room broadcast, and first-request/autonomous progress/decision states. Include accessibility, stale/unknown metric states, metric definitions, and responsive navigation. Proposed behavior is not a claim that the backend already provides it.

Acceptance for this design phase: coherent navigation and interaction map, draft wireframes visible in the conversation, image mockups derived from those wireframes, explicit user requirements versus design assumptions, unresolved high-impact choices, and a Mobbin research/refinement pass once available. Product implementation requires a later agreed design and plan.

Tracking: Vikunja #816. Related: request lifecycle #1839 / #797; source recovery #1843 / #815. This is a distinct design assignment.

Owner design request, 2026-11-04: redesign the current Chat/project/thread experience around familiar chat conventions and Jakob's Law. The current screenshots show weak orientation, sparse labels, no visual hierarchy, and session administration preceding the conversation. The goal is autonomous work with clear project context, not user-operated orchestration. Design only. Use collaborating GPT subagents to establish flows and low-fidelity wireframes, then generate visual design images. No application coding, scaffolding, dependency changes, PRD edits, policy/schema changes, deployment or live operations. Owner requirements: rename Chat area to Projects; section-dependent sidebar; expandable projects with active agent sessions; customizable item display; clicking a project opens its dashboard. Dashboard provides project context/settings, KPI bar for active/stalled/finished agents, changes, total/open PRs, uncommitted data, and useful additional metrics; clickable project issues and direct north-star/PRD access. PRD changes alert agents. Preserve a room-wide message/command with explicit audience. Use familiar chat layout, strong labels/breadcrumbs, and put advanced session/recovery management out of the primary path. Start with supplied Mosaic/T3/Desktop screenshots. Mobbin MCP is not connected yet; owner will configure it at the homelab. Do useful initial design now; mark later research and unimplemented capabilities honestly. Wireframes should cover project dashboard, agent conversation, room broadcast, and first-request/autonomous progress/decision states. Include accessibility, stale/unknown metric states, metric definitions, and responsive navigation. Proposed behavior is not a claim that the backend already provides it. Acceptance for this design phase: coherent navigation and interaction map, draft wireframes visible in the conversation, image mockups derived from those wireframes, explicit user requirements versus design assumptions, unresolved high-impact choices, and a Mobbin research/refinement pass once available. Product implementation requires a later agreed design and plan. Tracking: Vikunja #816. Related: request lifecycle #1839 / #797; source recovery #1843 / #815. This is a distinct design assignment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1844