| name | azure-functions-common |
| title | Azure Functions Common References |
| description | Shared Azure Functions reference material for the Azure Functions skill suite: runtime/language routing, trigger/binding extension references, official docs and repository pointers. Use only when another Azure Functions skill needs reusable language or binding context. Not intended as a standalone user-facing workflow. |
| category | reference |
Azure Functions Common References
Use this suite-internal skill as the shared reference pack for Azure Functions skills.
This skill is intentionally workflow-light. Do not load all references up front. Use routing.md to choose only the runtime/language and trigger/binding reference files needed for the current task.
Scope
Shared references include:
- Language/runtime references in
references/languages/.
- Trigger/binding extension references in
references/extensions/.
- Local emulator and development-service guidance in
references/local-emulators.md.
- Routing rules in
references/routing.md.
Task-specific skills keep their own workflows, scripts, evidence checklists, and output formats. For example, diagnostics owns diagnostic workflow and health evidence rules; this skill only owns reusable Azure Functions reference material.
Next steps
This is a shared reference skill. Return to the calling Azure Functions skill after loading only the relevant references.
Loading rules
- Load exactly one language reference when the runtime is known, plus Durable only when Durable is involved.
- Load only extension references matching the app's triggers/bindings or the symptom.
- Load
references/local-emulators.md when local E2E verification involves a non-HTTP trigger, service-backed binding, emulator, container, or temporary development resource.
- Load Extension Bundles only for non-.NET apps or extension-version/binding-resolution symptoms.
- Prefer official documentation, official repositories, official samples, and package/container registries before broader web sources.
