CopilotHub
SearchPromptsInstructionsAgentsToolsMCPs
  1. Home
  2. Instructions
  3. azure functions typescript.instructions
Back to Instructions

azure functions typescript.instructions

Coding standards for azure functions typescript.instructions

typescript
0 downloads
31 views
0

Tags

async
api

Related Instructions

View all →

API Route Security

app/api/**/*.ts

Security best practices for Next.js API routes

typescript
nextjs
security
api
+2
0
57

TypeScript Error Handling

*.ts

Comprehensive error handling patterns for TypeScript applications

typescript
typescript
error-handling
+1
0
57

React Component Best Practices

*.tsx

Guidelines for creating maintainable and performant React components

typescript
react
react
typescript
+2
0
62

WordPress Development — Copilot Instructions

Coding standards for wordpress.instructions

typescript
testing
security
+5
1
116

VueJS 3 Development Instructions

Coding standards for vuejs3.instructions

typescript
react
testing
security
+6
0
104

TypeScript MCP Server Development

Coding standards for typescript mcp server.instructions

typescript
express
testing
security
+5
0
81
Browse More Instructions

CopilotHub

A curated collection of prompts, instructions, agents, and tools for AI-powered development.

Quick Links

  • Prompts
  • Instructions
  • Agents
  • Tools
  • MCPs
  • Search

Browse by Category

  • Code Generation
  • Debugging
  • Documentation
  • Refactoring
  • Testing
  • Security

Legal

  • Guidelines
  • About
  • Privacy Policy
  • Terms of Service

Community

GitHub

© 2026 CopilotHub.

Guidance for Code Generation

  • Generate modern TypeScript code for Node.js
  • Use async/await for asynchronous code
  • Whenever possible, use Node.js v20 built-in modules instead of external packages
  • Always use Node.js async functions, like node:fs/promises instead of fs to avoid blocking the event loop
  • Ask before adding any extra dependencies to the project
  • The API is built using Azure Functions using @azure/functions@4 package.
  • 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.md file accordingly.