log-architect

Configures centralized logging architecture for .jsvascript-enabled ASP.NET Core apps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kongliuli/VibeSkills --skill log-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-architect
Source: https://github.com/kongliuli/VibeSkills/tree/main/Skills/C%23/common/log-architect
Command: npx skills add https://github.com/kongliuli/VibeSkills --skill log-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C# projects often struggle with inconsistent logging, scattered configurations, and lack of structured data. The log-architect skill provides a clear approach to designing a centralized logging architecture, integrating Serilog or NLog, and standardizing outputs across environments.

Core Features & Use Cases

  • Structured logging design with Serilog/NLog integration for consistent data capture.
  • Multi-output support including Console, File, Seq, and Elasticsearch.
  • Centralized log level strategy and formatting to improve observability across services.

Quick Start

Use the log-architect skill to configure a .NET project to log structured events to the console and a file, with a basic startup setup.

Frequently Asked Questions about log-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure structured logging in ASP.NET Core with Serilog?

Structured logging in ASP.NET Core captures log events as structured data using Serilog or NLog, enabling consistent formatting and centralized log level strategies across multiple output targets like Console, File, Seq, and Elasticsearch.

What's the best way to centralize log configuration across multiple .NET projects?

Centralizing log configuration across .NET projects involves establishing a unified logging architecture that standardizes outputs and applies consistent log level strategies across both ASP.NET Core apps and shared libraries.

Can I use NLog for multi-target logging outputs in C# applications?

Yes, you can use NLog for multi-target logging in C# applications to direct structured log events to outputs including Console, File, Seq, and Elasticsearch, ensuring no business logic is embedded in the logging configuration.

How do I set up Serilog to log structured events to a file and console?

Setting up Serilog to log structured events to a file and console requires configuring a basic startup architecture that defines multi-output sinks, allowing your .NET application to capture consistent event data during execution.

Does the log-architect skill embed business logic when integrating logging frameworks?

No, the log-architect skill ensures no business logic is embedded, focusing solely on configuring a robust logging architecture and integrating frameworks like Serilog or NLog for structured data capture.