prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  pages
   +--[id]
   `--api
       `--pets
  ```
  
  Convert this description:
  
  sync is a top-level directory that consolidates 6 subdirectories. Notable ones include layout-access, layout-has, layout-spread among others.
  
  Let me break down the design for you:
  
  In the root directory, 'layout-access' features 2 subfolders: client, server.
  In nested path 'layout-access → client', The 'client' folder hasn't been filled with any content.
  Within directory hierarchy 'layout-access > server', 'server' has yet to be populated.
  Back to the top level.
  In the root directory, 'layout-has' shelters 2 child directories: client, server.
  In nested path 'layout-has → client', The 'client' directory is blank.
  Within directory hierarchy 'layout-has → server', 'server' has no content.
  At the main level, 'layout-spread' houses 2 subfolders: client, server.
  At level 2, in directory path 'layout-spread / client', Inside 'client', you'll find it lacks any subdirectories.
  In nested path 'layout-spread > server', The 'server' container is currently empty.
  In the root directory, 'page-access' comprises 2 folders: client, server.
  At level 2, in directory path 'page-access / client', 'client' has no content.
  Within directory hierarchy 'page-access > server', 'server' appears to be unused.
  Back to the top level.
  In the root directory, 'page-has' organizes 2 directory entries: client, server.
  In nested path 'page-has → client', 'client' hasn't been filled with any content.
  Within directory hierarchy 'page-has > server', 'server' is vacant.
  Back to the top level.
  At the main level, 'page-spread' encompasses 2 child directories: client, server.
  In nested path 'page-spread → client', 'client' remains unused.
  In nested path 'page-spread → server', 'server' is unpopulated.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "sync\n +--layout-access\n |   +--client\n |   `--server\n +--layout-has\n |   +--client\n |   `--server\n +--layout-spread\n |   +--client\n |   `--server\n +--page-access\n |   +--client\n |   `--server\n +--page-has\n |   +--client\n |   `--server\n `--page-spread\n     +--client\n     `--server", "description": "sync is a top-level directory that consolidates 6 subdirectories. Notable ones include layout-access, layout-has, layout-spread among others.\n\nLet me break down the design for you:\n\nIn the root directory, 'layout-access' features 2 subfolders: client, server.\nIn nested path 'layout-access \u2192 client', The 'client' folder hasn't been filled with any content.\nWithin directory hierarchy 'layout-access > server', 'server' has yet to be populated.\nBack to the top level.\nIn the root directory, 'layout-has' shelters 2 child directories: client, server.\nIn nested path 'layout-has \u2192 client', The 'client' directory is blank.\nWithin directory hierarchy 'layout-has \u2192 server', 'server' has no content.\nAt the main level, 'layout-spread' houses 2 subfolders: client, server.\nAt level 2, in directory path 'layout-spread / client', Inside 'client', you'll find it lacks any subdirectories.\nIn nested path 'layout-spread > server', The 'server' container is currently empty.\nIn the root directory, 'page-access' comprises 2 folders: client, server.\nAt level 2, in directory path 'page-access / client', 'client' has no content.\nWithin directory hierarchy 'page-access > server', 'server' appears to be unused.\nBack to the top level.\nIn the root directory, 'page-has' organizes 2 directory entries: client, server.\nIn nested path 'page-has \u2192 client', 'client' hasn't been filled with any content.\nWithin directory hierarchy 'page-has > server', 'server' is vacant.\nBack to the top level.\nAt the main level, 'page-spread' encompasses 2 child directories: client, server.\nIn nested path 'page-spread \u2192 client', 'client' remains unused.\nIn nested path 'page-spread \u2192 server', 'server' is unpopulated.\n"}