GitHub Actions
# Project coding standards ## General GitHub Actions Standards - Use **YAML workflows** stored in `.github/workflows/`. - Name workflow files clearly (e.g., `build.yml`, `deploy-prod.yml`, `test-back...
Python + FastAPI
# Project coding standards ## General FastAPI Standards - Use **Python 3.10+** with type hints and `pyproject.toml`-based dependency management. - Structure the project using FastAPI's recommended la...
Svelte + TypeScript
# Project coding standards ## General Svelte + TypeScript Standards - Use **SvelteKit** for full-stack or SSR apps; use standalone Svelte for lightweight components or embedded widgets. - Use `<scrip...
ASP.NET Core Minimal API
# Project coding standards ## General ASP.NET Core Minimal API Standards - Define endpoints using `MapGet`, `MapPost`, `MapPut`, `MapDelete` directly on the `WebApplication` instance. - Keep the `Pro...
SharePoint Framework (SPFx)
# Project coding standards ## General SPFx + TypeScript Standards - Use **SPFx v1.18+** or the latest supported version aligned with your SharePoint Online tenant. - Always scaffold web parts and ext...
Kubernetes Manifests
# Project coding standards ## General Kubernetes YAML Standards - Use **apiVersion** appropriate for the cluster’s Kubernetes version (e.g., `apps/v1`, `networking.k8s.io/v1`). - Always define `metad...
Dockerfiles
# Project coding standards ## General Dockerfile Standards - Always use **official base images** where possible (e.g., `node:18-alpine`, `python:3.11-slim`, `mcr.microsoft.com/dotnet/aspnet:8.0`). - ...
Terraform
# Project coding standards ## General Terraform Standards - Use **Terraform v1.5+** and maintain backwards compatibility only when needed. - Structure Terraform code using **modules** to promote reus...
Bicep
# Project coding standards ## General Bicep Standards - Use **parameterized** templates to support reusability across environments. - Always provide default values or `allowed` lists for parameters w...
Vue 3 + TypeScript
# Project coding standards ## General Vue 3 + TypeScript Standards - Enable full TypeScript support with `strict: true` in `tsconfig.json`. - Prefer `defineProps` and `defineEmits` over the Options A...
Next.js + TanStack
# Project coding standards ## General Next.js + TanStack Query Standards - Use the **App Router** (`/app` directory) and **React Server Components** where applicable. - Use `@tanstack/react-query` fo...
Tanstack
# Project coding standards ## General TypeScript and TanStack Query Standards - Use **strict TypeScript settings** (`strict`, `noImplicitAny`, `strictNullChecks`, etc.). - Use `@tanstack/react-query`...
Angular with Signals and TypeScript
# Project coding standards ## General Angular + Signals + TypeScript Standards - Use Angular's **signal-based reactivity model** for local and shared state management. - Enable strict TypeScript sett...
Angular with Standalone Components
# Project coding standards ## General Angular Standalone Component Standards - Use Angular’s standalone component architecture (`standalone: true`) instead of declaring components in NgModules. - Use...
Angular + TypeScript
# Project coding standards ## General Angular and TypeScript Coding Standards - Use Angular CLI to generate components, services, and modules to ensure consistency. - Enable strict TypeScript options...
React with TypeScript
# Project coding standards ## General TypeScript and React Coding Standards - Use strict TypeScript settings (`strict`, `noImplicitAny`, `strictNullChecks`, etc.). - Always define explicit types for ...
Python Data Science
# Project coding standards ## General Python Coding Standards - Follow [PEP 8](https://peps.python.org/pep-0008/) where applicable. - Use type hints when possible, especially in utility or reusable f...
Python CLI Tools
# Project coding standards ## General Python Coding Standards - Follow [PEP 8](https://peps.python.org/pep-0008/) for formatting and naming conventions. - Use type hints consistently for function arg...
PowerShell
# Project coding standards ## General PowerShell Best Practices - Always use `PascalCase` for function names (e.g., `Get-UserInfo`) and `camelCase` for variables. - Follow the verb-noun convention in...
CSharp
# Project coding standards ## General C# Coding Standards - Use `var` only when the type is obvious from the right-hand side; otherwise, use explicit types. - Use consistent indentation and always us...
Blazor
# Project coding standards ## General C# Coding Standards - Use `var` only when the type is obvious; otherwise, use explicit types. - Keep line length under 120 characters. - Use consistent indentati...