prompt: Your task is to convert an English description into an ASCII tree format using this style:
  ```
  go-winio
   +--internal
   |   +--fs
   |   +--socket
   |   `--stringbuffer
   `--pkg
       `--guid
  ```
  
  Convert this description:
  
  production-runtime is a principal directory that encompasses 4 subdirectories. Notable ones include content, cypress, plugins among others.
  
  The project source code seems to be organized in the 'src' folder.
  
  Let me break down the design for you:
  
  At the top level, 'content' includes 1 contained folders: posts.
  In nested path 'content → posts', 'posts' is unpopulated.
  Back to the top level.
  In the root directory, 'cypress' encompasses 3 folders: fixtures, integration, support.
  In nested path 'cypress > fixtures', Inside 'fixtures', you'll find it contains no subdirectories.
  In nested path 'cypress → integration', Inside 'integration', you'll find it appears to be unused.
  At level 2, in directory path 'cypress > support', Inside 'support', you'll find it has no content.
  Back to the top level.
  In the root directory, 'plugins' keeps 2 subdirectories: gatsby-plugin-local, gatsby-theme-local.
  Within directory hierarchy 'plugins > gatsby-plugin-local', 'gatsby-plugin-local' has yet to be populated.
  Within directory hierarchy 'plugins > gatsby-theme-local', 'gatsby-theme-local' encapsulates 1 directory entries: src.
  At level 3, in directory path 'plugins → gatsby-theme-local → src', The 'src' repository retains 2 folders for code organization.
  At level 4, in directory path 'plugins → gatsby-theme-local → src → components', Inside 'components', you'll find it is blank.
  Within directory hierarchy 'plugins > gatsby-theme-local > src > pages', Inside 'pages', you'll find it has been left empty.
  At the top level, 'src' keeps 3 subdirectories that organize the source code.
  At level 2, in directory path 'src > gatsby-theme-about', 'gatsby-theme-about' comprises 3 folders: components, pages, templates.
  In nested path 'src > gatsby-theme-about > components', Inside 'components', you'll find it appears to be unused.
  At level 3, in directory path 'src / gatsby-theme-about / pages', 'pages' is blank.
  At level 3, in directory path 'src > gatsby-theme-about > templates', The 'templates' collection lacks any subdirectories.
  Within directory hierarchy 'src > gatsby-theme-local', 'gatsby-theme-local' incorporates 1 subdirectory elements: components.
  At level 3, in directory path 'src > gatsby-theme-local > components', Inside 'components', you'll find it holds no subdirectories at the moment.
  In nested path 'src → pages', The 'pages' storage space has yet to be populated.
  Back to the top level.
  
  
  Provide your answer wrapped in <ascii_formatted> tags.
verification_info: {"ground_truth": "production-runtime\n +--content\n |   `--posts\n +--cypress\n |   +--fixtures\n |   +--integration\n |   `--support\n +--plugins\n |   +--gatsby-plugin-local\n |   `--gatsby-theme-local\n |       `--src\n |           +--components\n |           `--pages\n `--src\n     +--gatsby-theme-about\n     |   +--components\n     |   +--pages\n     |   `--templates\n     +--gatsby-theme-local\n     |   `--components\n     `--pages", "description": "production-runtime is a principal directory that encompasses 4 subdirectories. Notable ones include content, cypress, plugins among others.\n\nThe project source code seems to be organized in the 'src' folder.\n\nLet me break down the design for you:\n\nAt the top level, 'content' includes 1 contained folders: posts.\nIn nested path 'content \u2192 posts', 'posts' is unpopulated.\nBack to the top level.\nIn the root directory, 'cypress' encompasses 3 folders: fixtures, integration, support.\nIn nested path 'cypress > fixtures', Inside 'fixtures', you'll find it contains no subdirectories.\nIn nested path 'cypress \u2192 integration', Inside 'integration', you'll find it appears to be unused.\nAt level 2, in directory path 'cypress > support', Inside 'support', you'll find it has no content.\nBack to the top level.\nIn the root directory, 'plugins' keeps 2 subdirectories: gatsby-plugin-local, gatsby-theme-local.\nWithin directory hierarchy 'plugins > gatsby-plugin-local', 'gatsby-plugin-local' has yet to be populated.\nWithin directory hierarchy 'plugins > gatsby-theme-local', 'gatsby-theme-local' encapsulates 1 directory entries: src.\nAt level 3, in directory path 'plugins \u2192 gatsby-theme-local \u2192 src', The 'src' repository retains 2 folders for code organization.\nAt level 4, in directory path 'plugins \u2192 gatsby-theme-local \u2192 src \u2192 components', Inside 'components', you'll find it is blank.\nWithin directory hierarchy 'plugins > gatsby-theme-local > src > pages', Inside 'pages', you'll find it has been left empty.\nAt the top level, 'src' keeps 3 subdirectories that organize the source code.\nAt level 2, in directory path 'src > gatsby-theme-about', 'gatsby-theme-about' comprises 3 folders: components, pages, templates.\nIn nested path 'src > gatsby-theme-about > components', Inside 'components', you'll find it appears to be unused.\nAt level 3, in directory path 'src / gatsby-theme-about / pages', 'pages' is blank.\nAt level 3, in directory path 'src > gatsby-theme-about > templates', The 'templates' collection lacks any subdirectories.\nWithin directory hierarchy 'src > gatsby-theme-local', 'gatsby-theme-local' incorporates 1 subdirectory elements: components.\nAt level 3, in directory path 'src > gatsby-theme-local > components', Inside 'components', you'll find it holds no subdirectories at the moment.\nIn nested path 'src \u2192 pages', The 'pages' storage space has yet to be populated.\nBack to the top level.\n"}