# English (US) AI workspace redesign brief for consulting firms

Product: Example objective: Build a product design brief with concrete screens, flows, and implementation guidance.
Audience: Operators, end users, and implementation teams

## Design Principles
- Reduce visible complexity until only the next action feels primary.
- Keep the main work lane visually dominant and push supporting tools to secondary positions.
- Make system state legible without turning the interface into a dashboard.

## Visual Direction
- Use one primary accent with restrained chrome so content stays dominant.
- Favor layered surfaces, clear spacing, and stable typography over decorative noise.
- Use motion to explain state changes, not to decorate idle surfaces.

## Layout System
- Primary conversation or work surface in the center lane.
- Secondary controls revealed contextually instead of permanently occupying space.
- Mobile layout should collapse utility chrome before compressing the content lane.

## Screens
### Workspace Home
- Objective: Orient the user fast and provide a clear way to start or resume work.
- Layout: Left navigation, central launch surface, contextual support rail.
- Element: Recent sessions
- Element: Starter prompts
- Element: Primary composer
- Element: Account and delivery state

### Active Conversation
- Objective: Keep reading and composing efficient while preserving access to advanced capabilities.
- Layout: Main message lane with contextual side actions and compact top navigation.
- Element: Messages
- Element: Composer
- Element: Hover actions
- Element: Context drawer

### Asset Review
- Objective: Let the user understand what was generated and download or reuse it immediately.
- Layout: Compact asset list with summaries, timestamps, and download actions.
- Element: Recent assets
- Element: Artifact summary
- Element: Download action
- Element: Email delivery state

## Flows
### Start and refine a task
- Step: Enter the goal
- Step: Attach supporting files if needed
- Step: Iterate inside one active session
- Outcome: The user reaches a structured output without switching contexts.

### Generate and reuse deliverables
- Step: Choose the correct artifact action
- Step: Inspect the generated package
- Step: Download or email the result
- Outcome: The conversation becomes a portable asset, not just chat history.

## Content Guidelines
- Lead with the outcome and strip explanatory copy once the user is already inside the workflow.
- Use labels that describe deliverables, not internal system mechanics.
- Prefer one strong instruction over stacked helper paragraphs.

## Implementation Notes
- Treat action visibility as explicit state, not fragile hover-only CSS.
- Use one shared content width per surface so header, timeline, and composer stay aligned.
- Preserve consistent component language across desktop and mobile before adding new chrome.