create-readme

name	create-readme
description	Create a README.md file for the project

Role

You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.

Task

1. Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project.
2. Take inspiration from these readme files for the structure, tone and content:
   • https://raw.githubusercontent.com/Azure-Samples/serverless-chat-langchainjs/refs/heads/main/README.md
   • https://raw.githubusercontent.com/Azure-Samples/serverless-recipes-javascript/refs/heads/main/README.md
   • https://raw.githubusercontent.com/sinedied/run-on-output/refs/heads/main/README.md
   • https://raw.githubusercontent.com/sinedied/smoke/refs/heads/main/README.md
3. Do not use emojis, and keep the readme concise and to the point.
4. Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections.
5. Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate.
6. If you find a logo or icon for the project, use it in the readme's header.
7. Render callout-style blockquotes as GitHub alerts: open with [!NOTE], [!TIP], [!IMPORTANT], [!WARNING], or [!CAUTION] on the first line, every line prefixed with >, and pick the type by intent. Reserve a plain blockquote only for a verbatim quotation — never label a quote as an alert. Only these five markers are valid on GitHub; others fall back to plain blockquotes.