prompt: Your task is to convert the following English description into an ASCII tree format.
  
  config is a master directory that comprises 9 subdirectories. Notable ones include config, config-writer, deps-installer among others.
  
  Let me break down the setup for you:
  
  In the root directory, 'config' organizes 2 nested folders: src, test.
  Within directory hierarchy 'config / src', Inside 'src', you'll find it awaits content.
  At level 2, in directory path 'config > test', 'test' organizes tests across 5 separate nested folders.
  Within directory hierarchy 'config / test / fixtures', 'fixtures' encapsulates 6 various subfolders.
  In nested path 'config → test → fixtures → has-env-in-key', The 'has-env-in-key' data structure has no folders inside.
  Within directory hierarchy 'config > test > fixtures > has-number-setting', Inside 'has-number-setting', you'll find it sits empty.
  In nested path 'config / test / fixtures / never-built-dependencies', 'never-built-dependencies' is unpopulated.
  Within directory hierarchy 'config / test / fixtures / pkg-using-workspaces', The 'pkg-using-workspaces' collection is unpopulated.
  In nested path 'config → test → fixtures → pkg-with-valid-workspace-yaml', Inside 'pkg-with-valid-workspace-yaml', you'll find it is a vacant space.
  At level 4, in directory path 'config / test / fixtures / settings-in-workspace-yaml', Inside 'settings-in-workspace-yaml', you'll find it has been left empty.
  Within directory hierarchy 'config → test → global-bin-dir', 'global-bin-dir' features 1 contained folders: etc.
  At level 4, in directory path 'config → test → global-bin-dir → etc', The 'etc' compartment is vacant.
  In nested path 'config / test / global-bin-dir-windows', 'global-bin-dir-windows' stores 1 child directories: etc.
  In nested path 'config → test → global-bin-dir-windows → etc', Inside 'etc', you'll find it lacks any subdirectories.
  In nested path 'config > test > has-workspace-yaml', 'has-workspace-yaml' has yet to be populated.
  Within directory hierarchy 'config → test → using-test-pattern', The 'using-test-pattern' section contains no subdirectories.
  Back to the top level.
  In the root directory, 'config-writer' bundles 1 subdirectories: src.
  At level 2, in directory path 'config-writer → src', The 'src' folder sits empty.
  Back to the top level.
  In the root directory, 'deps-installer' incorporates 2 subdirectory elements: src, test.
  At level 2, in directory path 'deps-installer / src', The 'src' folder contains no subdirectories.
  In nested path 'deps-installer / test', The 'test' container sits empty.
  Back to the top level.
  In the root directory, 'matcher' organizes 2 subdirectories: src, test.
  Within directory hierarchy 'matcher > src', 'src' is currently empty.
  In nested path 'matcher → test', 'test' is empty.
  Back to the top level.
  At the main level, 'normalize-registries' encapsulates 1 nested folders: src.
  In nested path 'normalize-registries / src', 'src' remains unused.
  In the root directory, 'package-is-installable' possesses 2 directory entries: src, test.
  In nested path 'package-is-installable / src', The 'src' storage space contains no subdirectories.
  At level 2, in directory path 'package-is-installable / test', 'test' has been left empty.
  At the top level, 'parse-overrides' groups 2 subfolders: src, test.
  Within directory hierarchy 'parse-overrides / src', Inside 'src', you'll find it has yet to be populated.
  At level 2, in directory path 'parse-overrides / test', Inside 'test', you'll find it is unpopulated.
  In the root directory, 'pick-registry-for-package' retains 2 subdirectories: src, test.
  Within directory hierarchy 'pick-registry-for-package / src', The 'src' collection contains nothing at present.
  At level 2, in directory path 'pick-registry-for-package > test', Inside 'test', you'll find it is vacant.
  At the main level, 'plugin-commands-config' includes 2 child directories: src, test.
  At level 2, in directory path 'plugin-commands-config / src', Inside 'src', you'll find it is an empty container.
  In nested path 'plugin-commands-config / test', 'test' contains no subdirectories.
  Back to the top level.
  
  
  Format your response in this style:
  ```
  image-optimizer
   +--app
   |   +--pages
   |   |   `--api
   |   |       `--stateful
   |   `--public
   `--test
  ```
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "config\n +--config\n |   +--src\n |   `--test\n |       +--fixtures\n |       |   +--has-env-in-key\n |       |   +--has-number-setting\n |       |   +--never-built-dependencies\n |       |   +--pkg-using-workspaces\n |       |   +--pkg-with-valid-workspace-yaml\n |       |   `--settings-in-workspace-yaml\n |       +--global-bin-dir\n |       |   `--etc\n |       +--global-bin-dir-windows\n |       |   `--etc\n |       +--has-workspace-yaml\n |       `--using-test-pattern\n +--config-writer\n |   `--src\n +--deps-installer\n |   +--src\n |   `--test\n +--matcher\n |   +--src\n |   `--test\n +--normalize-registries\n |   `--src\n +--package-is-installable\n |   +--src\n |   `--test\n +--parse-overrides\n |   +--src\n |   `--test\n +--pick-registry-for-package\n |   +--src\n |   `--test\n `--plugin-commands-config\n     +--src\n     `--test", "description": "config is a master directory that comprises 9 subdirectories. Notable ones include config, config-writer, deps-installer among others.\n\nLet me break down the setup for you:\n\nIn the root directory, 'config' organizes 2 nested folders: src, test.\nWithin directory hierarchy 'config / src', Inside 'src', you'll find it awaits content.\nAt level 2, in directory path 'config > test', 'test' organizes tests across 5 separate nested folders.\nWithin directory hierarchy 'config / test / fixtures', 'fixtures' encapsulates 6 various subfolders.\nIn nested path 'config \u2192 test \u2192 fixtures \u2192 has-env-in-key', The 'has-env-in-key' data structure has no folders inside.\nWithin directory hierarchy 'config > test > fixtures > has-number-setting', Inside 'has-number-setting', you'll find it sits empty.\nIn nested path 'config / test / fixtures / never-built-dependencies', 'never-built-dependencies' is unpopulated.\nWithin directory hierarchy 'config / test / fixtures / pkg-using-workspaces', The 'pkg-using-workspaces' collection is unpopulated.\nIn nested path 'config \u2192 test \u2192 fixtures \u2192 pkg-with-valid-workspace-yaml', Inside 'pkg-with-valid-workspace-yaml', you'll find it is a vacant space.\nAt level 4, in directory path 'config / test / fixtures / settings-in-workspace-yaml', Inside 'settings-in-workspace-yaml', you'll find it has been left empty.\nWithin directory hierarchy 'config \u2192 test \u2192 global-bin-dir', 'global-bin-dir' features 1 contained folders: etc.\nAt level 4, in directory path 'config \u2192 test \u2192 global-bin-dir \u2192 etc', The 'etc' compartment is vacant.\nIn nested path 'config / test / global-bin-dir-windows', 'global-bin-dir-windows' stores 1 child directories: etc.\nIn nested path 'config \u2192 test \u2192 global-bin-dir-windows \u2192 etc', Inside 'etc', you'll find it lacks any subdirectories.\nIn nested path 'config > test > has-workspace-yaml', 'has-workspace-yaml' has yet to be populated.\nWithin directory hierarchy 'config \u2192 test \u2192 using-test-pattern', The 'using-test-pattern' section contains no subdirectories.\nBack to the top level.\nIn the root directory, 'config-writer' bundles 1 subdirectories: src.\nAt level 2, in directory path 'config-writer \u2192 src', The 'src' folder sits empty.\nBack to the top level.\nIn the root directory, 'deps-installer' incorporates 2 subdirectory elements: src, test.\nAt level 2, in directory path 'deps-installer / src', The 'src' folder contains no subdirectories.\nIn nested path 'deps-installer / test', The 'test' container sits empty.\nBack to the top level.\nIn the root directory, 'matcher' organizes 2 subdirectories: src, test.\nWithin directory hierarchy 'matcher > src', 'src' is currently empty.\nIn nested path 'matcher \u2192 test', 'test' is empty.\nBack to the top level.\nAt the main level, 'normalize-registries' encapsulates 1 nested folders: src.\nIn nested path 'normalize-registries / src', 'src' remains unused.\nIn the root directory, 'package-is-installable' possesses 2 directory entries: src, test.\nIn nested path 'package-is-installable / src', The 'src' storage space contains no subdirectories.\nAt level 2, in directory path 'package-is-installable / test', 'test' has been left empty.\nAt the top level, 'parse-overrides' groups 2 subfolders: src, test.\nWithin directory hierarchy 'parse-overrides / src', Inside 'src', you'll find it has yet to be populated.\nAt level 2, in directory path 'parse-overrides / test', Inside 'test', you'll find it is unpopulated.\nIn the root directory, 'pick-registry-for-package' retains 2 subdirectories: src, test.\nWithin directory hierarchy 'pick-registry-for-package / src', The 'src' collection contains nothing at present.\nAt level 2, in directory path 'pick-registry-for-package > test', Inside 'test', you'll find it is vacant.\nAt the main level, 'plugin-commands-config' includes 2 child directories: src, test.\nAt level 2, in directory path 'plugin-commands-config / src', Inside 'src', you'll find it is an empty container.\nIn nested path 'plugin-commands-config / test', 'test' contains no subdirectories.\nBack to the top level.\n"}