{
  "title": "English (US) community marketplace mobile brief for real estate teams",
  "product": "Example objective: Build a product design brief with concrete screens, flows, and implementation guidance.",
  "audience": "Operators, end users, and implementation teams",
  "designPrinciples": [
    "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."
  ],
  "visualDirection": [
    "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."
  ],
  "layoutSystem": [
    "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": [
    {
      "name": "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.",
      "keyElements": [
        "Recent sessions",
        "Starter prompts",
        "Primary composer",
        "Account and delivery state"
      ]
    },
    {
      "name": "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.",
      "keyElements": [
        "Messages",
        "Composer",
        "Hover actions",
        "Context drawer"
      ]
    },
    {
      "name": "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.",
      "keyElements": [
        "Recent assets",
        "Artifact summary",
        "Download action",
        "Email delivery state"
      ]
    }
  ],
  "flows": [
    {
      "name": "Start and refine a task",
      "steps": [
        "Enter the goal",
        "Attach supporting files if needed",
        "Iterate inside one active session"
      ],
      "outcome": "The user reaches a structured output without switching contexts."
    },
    {
      "name": "Generate and reuse deliverables",
      "steps": [
        "Choose the correct artifact action",
        "Inspect the generated package",
        "Download or email the result"
      ],
      "outcome": "The conversation becomes a portable asset, not just chat history."
    }
  ],
  "contentGuidelines": [
    "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."
  ],
  "implementationNotes": [
    "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."
  ]
}