Merge branch 'main' into fix-spelling-errors-found-by-codespell

instructions/arch-linux.instructions.md

@@ -0,0 +1,38 @@
+---
+description: 'Guidance for Arch Linux administration, pacman workflows, and rolling-release best practices.'
+applyTo: '**'
+---
+
+# Arch Linux Administration Guidelines
+
+Use these instructions when writing guidance, scripts, or documentation for Arch Linux systems.
+
+## Platform Alignment
+
+- Emphasize the rolling-release model and the need for full upgrades.
+- Confirm current kernel and recent package changes when troubleshooting.
+- Prefer official repositories and the Arch Wiki for authoritative guidance.
+
+## Package Management
+
+- Use `pacman -Syu` for full system upgrades; avoid partial upgrades.
+- Inspect packages with `pacman -Qi`, `pacman -Ql`, and `pacman -Ss`.
+- Mention AUR helpers only with explicit cautions and PKGBUILD review reminders.
+
+## Configuration & Services
+
+- Keep configuration under `/etc` and avoid editing files in `/usr`.
+- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/`.
+- Use `systemctl` and `journalctl` for service control and logs.
+
+## Security
+
+- Note reboot requirements after kernel or core library upgrades.
+- Recommend least-privilege `sudo` usage and minimal packages.
+- Call out firewall tooling expectations (nftables/ufw) explicitly.
+
+## Deliverables
+
+- Provide commands in copy-paste-ready blocks.
+- Include validation steps after changes.
+- Offer rollback or cleanup steps for risky operations.

instructions/aspnet-rest-apis.instructions.md

@@ -6,7 +6,7 @@ applyTo: '**/*.cs, **/*.json'
 # ASP.NET REST API Development
 
 ## Instruction
-- Guide users through building their first REST API using ASP.NET Core 9.
+- Guide users through building their first REST API using ASP.NET Core 10.
 - Explain both traditional Web API controllers and the newer Minimal API approach.
 - Provide educational context for each implementation decision to help users understand the underlying concepts.
 - Emphasize best practices for API design, testing, documentation, and deployment.
@@ -22,11 +22,11 @@ applyTo: '**/*.cs, **/*.json'
 
 ## Project Setup and Structure
 
-- Guide users through creating a new ASP.NET Core 9 Web API project with the appropriate templates.
+- Guide users through creating a new ASP.NET Core 10 Web API project with the appropriate templates.
 - Explain the purpose of each generated file and folder to build understanding of the project structure.
 - Demonstrate how to organize code using feature folders or domain-driven design principles.
 - Show proper separation of concerns with models, services, and data access layers.
-- Explain the Program.cs and configuration system in ASP.NET Core 9 including environment-specific settings.
+- Explain the Program.cs and configuration system in ASP.NET Core 10 including environment-specific settings.
 
 ## Building Controller-Based APIs
 
@@ -66,7 +66,7 @@ applyTo: '**/*.cs, **/*.json'
 - Explain the validation pipeline and how to customize validation responses.
 - Demonstrate a global exception handling strategy using middleware.
 - Show how to create consistent error responses across the API.
-- Explain problem details (RFC 7807) implementation for standardized error responses.
+- Explain problem details (RFC 9457) implementation for standardized error responses.
 
 ## API Versioning and Documentation
 

instructions/centos-linux.instructions.md

@@ -0,0 +1,39 @@
+---
+description: 'Guidance for CentOS administration, RHEL-compatible tooling, and SELinux-aware operations.'
+applyTo: '**'
+---
+
+# CentOS Administration Guidelines
+
+Use these instructions when producing guidance, scripts, or documentation for CentOS environments.
+
+## Platform Alignment
+
+- Identify CentOS version (Stream vs. legacy) and tailor commands.
+- Prefer `dnf` for Stream/8+ and `yum` for CentOS 7.
+- Use RHEL-compatible terminology and paths.
+
+## Package Management
+
+- Verify repositories with GPG checks enabled.
+- Use `dnf info`/`yum info` and `dnf repoquery` for package details.
+- Use `dnf versionlock` or `yum versionlock` for stability where needed.
+- Call out EPEL dependencies and how to enable/disable them safely.
+
+## Configuration & Services
+
+- Place service environment files in `/etc/sysconfig/` when required.
+- Use systemd drop-ins for overrides and `systemctl` for control.
+- Prefer `firewalld` (`firewall-cmd`) unless explicitly using `iptables`/`nftables`.
+
+## Security
+
+- Keep SELinux in enforcing mode whenever possible.
+- Use `semanage`, `restorecon`, and `setsebool` for policy adjustments.
+- Reference `/var/log/audit/audit.log` for denials.
+
+## Deliverables
+
+- Provide commands in copy-paste-ready blocks.
+- Include verification steps after changes.
+- Offer rollback steps for risky operations.

instructions/csharp-ja.instructions.md

@@ -67,7 +67,7 @@ applyTo: '**/*.cs'
 - 検証パイプラインと、検証応答のカスタマイズ方法を説明します。
 - ミドルウェアを用いたグローバル例外処理戦略を示します。
 - API 全体で一貫したエラー応答を作成する方法を示します。
-- 標準化されたエラー応答のための Problem Details（RFC 7807）の実装を説明します。
+- 標準化されたエラー応答のための Problem Details（RFC 9457）の実装を説明します。
 
 ## API のバージョニングとドキュメント
 

instructions/csharp.instructions.md

@@ -67,7 +67,7 @@ applyTo: '**/*.cs'
 - Explain the validation pipeline and how to customize validation responses.
 - Demonstrate a global exception handling strategy using middleware.
 - Show how to create consistent error responses across the API.
-- Explain problem details (RFC 7807) implementation for standardized error responses.
+- Explain problem details (RFC 9457) implementation for standardized error responses.
 
 ## API Versioning and Documentation
 

instructions/debian-linux.instructions.md

@@ -0,0 +1,40 @@
+---
+description: 'Guidance for Debian-based Linux administration, apt workflows, and Debian policy conventions.'
+applyTo: '**'
+---
+
+# Debian Linux Administration Guidelines
+
+Use these instructions when writing guidance, scripts, or documentation intended for Debian-based systems.
+
+## Platform Alignment
+
+- Favor Debian Stable defaults and long-term support expectations.
+- Call out the Debian release (`bookworm`, `bullseye`, etc.) when relevant.
+- Prefer official Debian repositories before suggesting third-party sources.
+
+## Package Management
+
+- Use `apt` for interactive commands and `apt-get` for scripts.
+- Inspect packages with `apt-cache policy`, `apt show`, and `dpkg -l`.
+- Use `apt-mark` to track manual vs. auto-installed packages.
+- Document any apt pinning in `/etc/apt/preferences.d/` and explain why.
+
+## Configuration & Services
+
+- Store configuration under `/etc` and avoid modifying `/usr` files directly.
+- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/` for overrides.
+- Prefer `systemctl` and `journalctl` for service control and logs.
+- Use `ufw` or `nftables` for firewall guidance; state which is expected.
+
+## Security
+
+- Account for AppArmor profiles and mention adjustments if needed.
+- Recommend least-privilege `sudo` use and minimal package installs.
+- Include verification commands after security changes.
+
+## Deliverables
+
+- Provide commands in copy-paste-ready blocks.
+- Include validation steps after changes.
+- Offer rollback steps for destructive actions.

instructions/fedora-linux.instructions.md

@@ -0,0 +1,38 @@
+---
+description: 'Guidance for Fedora (Red Hat family) systems, dnf workflows, SELinux, and modern systemd practices.'
+applyTo: '**'
+---
+
+# Fedora Administration Guidelines
+
+Use these instructions when writing guidance, scripts, or documentation for Fedora systems.
+
+## Platform Alignment
+
+- State the Fedora release number when relevant.
+- Prefer modern tooling (`dnf`, `systemctl`, `firewall-cmd`).
+- Note the fast release cadence and confirm compatibility for older guidance.
+
+## Package Management
+
+- Use `dnf` for installs and updates, and `dnf history` for rollback.
+- Inspect packages with `dnf info` and `rpm -qi`.
+- Mention COPR repositories only with clear support caveats.
+
+## Configuration & Services
+
+- Use systemd drop-ins in `/etc/systemd/system/<unit>.d/`.
+- Use `journalctl` for logs and `systemctl status` for service health.
+- Prefer `firewalld` unless using `nftables` explicitly.
+
+## Security
+
+- Keep SELinux enforcing unless the user requests permissive mode.
+- Use `semanage`, `setsebool`, and `restorecon` for policy changes.
+- Recommend targeted fixes instead of broad `audit2allow` rules.
+
+## Deliverables
+
+- Provide commands in copy-paste-ready blocks.
+- Include verification steps after changes.
+- Offer rollback steps for risky operations.