Goal
Redesign the PawWork home screen as a calm task starter centered on the composer. It should feel like a desktop workbench empty state, not a capability showcase, prompt gallery, or marketing page.
Visual baseline
Use these mockups as the baseline for layout, density, color, hierarchy, and the home-to-session transition.
Home starter
This is the home screen baseline.
Session continuation
This shows the same visual language after a Skill starts inside a normal conversation. It is included to keep the transition coherent. The right-panel information architecture and first-phase 进展 / Summary redesign are tracked in #154.
Broader UI language
The visual language established here should carry into the session workspace, including the existing right-side panel as part of the overall UI reshaping. #151 owns the home starter and transition model. #154 owns the right-panel information architecture.
Keep
Main canvas: no centered paw logo, modest Chinese title with the meaning of “今天想做什么？”, exactly three Skill entries above the composer: 整理文件, 数据分析, 帮我写作.
Skill entries: lightweight workflow entry points, not example prompts and not large feature cards.
Skill start card: after a Skill is submitted, show the selected Skill as a compact card in the conversation flow, similar to a Codex-style tool or status card. Do not keep the selected Skill as a persistent chip inside the composer.
Composer: primary visual object, spacious typing area, plus attachment button, placeholder, orange send button, and subtle local-processing reassurance note. On the home screen, a workspace selector may remain if needed for local scope selection. In an active session, the workspace chip belongs next to the conversation title, not inside the composer.
Sidebar: PawWork logo plus name plus dropdown only in the header. Navigation has one New conversation row, Search, Plugins, Remote control, Automatic tasks, then Pinned, All conversations, and Settings. Do not duplicate the New conversation affordance in the header.
Visual tone: warm light theme, restrained orange accents, tasteful low-saturation Skill icon colors, neutral chip backgrounds and borders, no orange composer border.
Behavior
Skill entries are selectors, not example prompts.
Clicking a Skill entry prepares that Skill as the intended workflow without inserting a persistent Skill chip into the composer.
Sending still creates a normal session first, then inserts a lightweight Skill start card in the conversation flow and starts the Skill inside that session.
Skill details are collected through the existing question flow inside the session, not on the home screen.
Use one default run mode. Hide or remove run-mode selection from the home composer.
Non-goals
Do not implement plugin management here.
Do not implement remote control here.
Do not implement automatic task scheduling here.
Do not build configurable pinned Skill/plugin shortcuts here.
Do not define the detailed session right-panel information architecture here. That is tracked in #154.
Do not add prompt suggestion experiments, large feature cards, right panel on the home screen, mascot, centered logo, or dense toolbar.
Goal
Redesign the PawWork home screen as a calm task starter centered on the composer. It should feel like a desktop workbench empty state, not a capability showcase, prompt gallery, or marketing page.
Visual baseline
Use these mockups as the baseline for layout, density, color, hierarchy, and the home-to-session transition.
Home starter
This is the home screen baseline.
Session continuation
This shows the same visual language after a Skill starts inside a normal conversation. It is included to keep the transition coherent. The right-panel information architecture and first-phase
进展 / Summaryredesign are tracked in #154.Broader UI language
The visual language established here should carry into the session workspace, including the existing right-side panel as part of the overall UI reshaping. #151 owns the home starter and transition model. #154 owns the right-panel information architecture.
Keep
Main canvas: no centered paw logo, modest Chinese title with the meaning of “今天想做什么？”, exactly three Skill entries above the composer: 整理文件, 数据分析, 帮我写作.
Skill entries: lightweight workflow entry points, not example prompts and not large feature cards.
Skill start card: after a Skill is submitted, show the selected Skill as a compact card in the conversation flow, similar to a Codex-style tool or status card. Do not keep the selected Skill as a persistent chip inside the composer.
Composer: primary visual object, spacious typing area, plus attachment button, placeholder, orange send button, and subtle local-processing reassurance note. On the home screen, a workspace selector may remain if needed for local scope selection. In an active session, the workspace chip belongs next to the conversation title, not inside the composer.
Sidebar: PawWork logo plus name plus dropdown only in the header. Navigation has one New conversation row, Search, Plugins, Remote control, Automatic tasks, then Pinned, All conversations, and Settings. Do not duplicate the New conversation affordance in the header.
Visual tone: warm light theme, restrained orange accents, tasteful low-saturation Skill icon colors, neutral chip backgrounds and borders, no orange composer border.
Behavior
Skill entries are selectors, not example prompts.
Clicking a Skill entry prepares that Skill as the intended workflow without inserting a persistent Skill chip into the composer.
Sending still creates a normal session first, then inserts a lightweight Skill start card in the conversation flow and starts the Skill inside that session.
Skill details are collected through the existing question flow inside the session, not on the home screen.
Use one default run mode. Hide or remove run-mode selection from the home composer.
Non-goals
Do not implement plugin management here.
Do not implement remote control here.
Do not implement automatic task scheduling here.
Do not build configurable pinned Skill/plugin shortcuts here.
Do not define the detailed session right-panel information architecture here. That is tracked in #154.
Do not add prompt suggestion experiments, large feature cards, right panel on the home screen, mascot, centered logo, or dense toolbar.