* Delete outdated development instructions for Next.js + Tailwind and Python; add comprehensive guidelines for PostgreSQL DBA, Angular, ASP.NET REST APIs, Azure Functions with TypeScript, Bicep, Blazor, CMake with vcpkg, C#, .NET MAUI, GenAIScript, Terraform for Azure, localization, and markdown standards. * Update documentation and prompts for consistency and clarity - Standardized description formatting in various markdown files to use single quotes. - Added error handling utility in update-readme.js for safer file operations. - Improved title extraction logic in update-readme.js to handle frontmatter more robustly. - Updated chat modes section in README to reflect new emoji and sorted chat mode links. - Cleaned up various instruction files for better readability and consistency. - Ensured all markdown files end with a newline for better compatibility with version control. * Remove standardize-frontmatter.js script * Add usage instructions for creating and switching chat modes in README.md * Update README.md generation script to enhance instructions and usage details for custom chat modes * Update README.md and update-readme.js for improved instruction clarity and consistency * Refactor README.md links and update readme script for improved clarity and consistency in instructions * Update README.md and update-readme.js for improved instruction clarity and consistency * Changing from a patch to regen approach for the readme * Bit more cleanup for how to show things in the readme * Adding missing description * Another missing description --------- Co-authored-by: Aaron Powell <me@aaron-powell.com>
813 B
813 B
| description | applyTo |
|---|---|
| TypeScript patterns for Azure Functions | **/*.ts, **/*.js, **/*.json |
Guidance for Code Generation
- Generate modern TypeScript code for Node.js
- Use
async/awaitfor asynchronous code - Whenever possible, use Node.js v20 built-in modules instead of external packages
- Always use Node.js async functions, like
node:fs/promisesinstead offsto avoid blocking the event loop - Ask before adding any extra dependencies to the project
- The API is built using Azure Functions using
@azure/functions@4package. - Each endpoint should have its own function file, and use the following naming convention:
src/functions/<resource-name>-<http-verb>.ts - When making changes to the API, make sure to update the OpenAPI schema (if it exists) and
README.mdfile accordingly.