This repository contains curated instruction sets to guide AI-assisted development across multiple technology stacks. The goal is to ensure consistency, performance, and adherence to best practices when generating code with GitHub Copilot or similar AI tools.
- General Instructions
- Angular Development
- C# / .NET Development
- How to Use
- Principles
- Resources
- Output Expectations
git.instructions.md
Git workflow and commit guidelines:- Meaningful commit messages and regular pulls from main
- Always ask before proceeding with git operations
general.instructions.md
Core rules and conventions for all Angular development in this project:- Follow Angular version from
package.json - Standalone components, signals, new control flow (
@if/@for/@switch) - SOLID principles, naming conventions, and strict TypeScript usage
- RxJS best practices and observable handling
- ESLint + Prettier compliance
- Respecting existing project structure
- Follow Angular version from
kendo.instructions.md
Specific guidelines for Kendo UI component usage:- Typed + performant
KendoGridsetup (client & server ops) - Naming, DRY, and code quality rules
- Tooling compliance (lint + format)
- SCSS restrictions (use Kendo themes)
- Typed + performant
angular.instructions.md
Persona-based instruction set targeting Angular v20+ and cutting-edge practices:- Signals for state management (
signal,computed,update) - Standalone components with OnPush change detection
- Modern templates using native control flow
- Service patterns with
inject()andprovidedIn: 'root' - RxJS integration (no manual
subscribe(), usetoSignal,| async) - Strong typing, clean architecture, performance optimization
- Signals for state management (
c-sharp.instructions.md
Comprehensive C# and .NET development guidelines:- Modern C# features (file-scoped namespaces, records, pattern matching)
- SOLID principles and clean architecture patterns
- Dependency injection and configuration best practices
- Async/await patterns with proper cancellation support
- Performance and memory optimization guidelines
- Comprehensive error handling and logging strategies
dotnet-8-isolated.instructions.md
Specialized guidelines for Azure Functions Isolated Worker on .NET 8:- Cold start optimization and performance considerations
- Azure SDK integration and Managed Identity usage
- Function-specific patterns (triggers, bindings, hosting)
- Observability with OpenTelemetry and structured logging
- Security best practices for cloud environments
-
Load into Copilot: Use these instruction files as system prompts or reference guidelines when working with AI-assisted code generation.
-
Technology-Specific Rules: Choose the appropriate instruction set for your development context:
- Angular Projects: Combine
general.instructions.mdwith eitherkendo.instructions.mdorangular.instructions.md - C# Projects: Use
c-sharp.instructions.mdfor general .NET development - Azure Functions: Use
dotnet-8-isolated.instructions.mdfor serverless applications - Git Operations: Reference
git.instructions.mdfor version control workflows
- Angular Projects: Combine
-
Consistency: Generated code must follow these instructions:
- Angular: No
anytypes; preferunknown+ narrowing. NongClass/ngStyle→ use native property bindings. - C#: Use nullable reference types, modern language features, and proper async patterns.
- General: No new directories unless explicitly required. Analyzer/linter clean output.
- Angular: No
- Maintainability: Small, focused components and services.
- Performance: Optimization appropriate to the platform (signals for Angular, async patterns for .NET).
- Clarity: Explicit naming, no abbreviations, no magic numbers.
- Consistency: Follow official style guides and project conventions.
- Signals: Use for state management and reactive patterns.
- OnPush: Prefer OnPush change detection for performance.
- Virtualization: Use for large data sets in grids.
- Immutability: Prefer records and readonly collections.
- Dependency Injection: Use built-in DI container with proper lifetimes.
- Async/Await: Default to async patterns with cancellation support.
- .NET Documentation
- C# Programming Guide
- Azure Functions Documentation
- .NET Dependency Injection
- Async Programming Patterns
When using these instruction sets, Copilot should generate code that is:
- Framework version aligned (from project configuration files)
- Typed, clean, maintainable
- Linter/analyzer compliant
- Respectful of existing project structure
- Production-ready without post-cleanup
- Signals and OnPush for performance
- Standalone components with modern template syntax
- ESLint + Prettier compliant
- Nullable reference types enabled and respected
- Modern C# language features utilized appropriately
- Async/await patterns with proper cancellation
- Dependency injection and configuration patterns
- Dependency injection and configuration patterns
This repository includes several focused prompt templates and stack-specific instruction sets located in the pre-built-LLM-prompts/ folder. Use these files as ready-to-use system prompts or developer guidance for each target environment.
- pre-built-LLM-prompts/README_Angular19_UI.md: Frontend guidelines for Angular 19+ projects (strict TypeScript, signals, OnPush, standalone components).
- pre-built-LLM-prompts/README_AWS_Lambda_Node_TS.md: Serverless backend patterns for AWS Lambda using Node.js + TypeScript (handlers, strict typing, local run instructions).
- pre-built-LLM-prompts/README_AzureFunctions_NET8_Isolated.md: Azure Functions (.NET 8 isolated) guidance (DI, observability, thin functions, local development).
- pre-built-LLM-prompts/README_General_LLM_Control_Prompt.md: High-integrity LLM control prompt to reduce hallucinations and enforce clarification and transparency.
- pre-built-LLM-prompts/README_LLM_Control_Prompt_Token_Optimized.md: Compact, token-optimized control prompt variant for concise high-quality responses.
Refer to each file for full details and example usage patterns.