cencon-generate

Analyze .NET source code to generate CenCon documentation files.

94|11|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/thefrederiksen/cc-director --skill cencon-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cencon-generate
Source: https://github.com/thefrederiksen/cc-director/tree/main/.claude/skills/cencon-generate
Command: npx skills add https://github.com/thefrederiksen/cc-director --skill cencon-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive documentation for .NET projects, ensuring that architecture, security, and index files are always up-to-date with the source code.

Core Features & Use Cases

  • Automated Documentation Generation: Analyzes .NET source code to produce architecture_manifest.yaml, security_profile.yaml, and INDEX.md.
  • Code-Driven Accuracy: Ensures documentation reflects the actual codebase, reducing manual errors and drift.
  • Use Case: A development team can use this Skill to automatically generate and maintain up-to-date architectural and security documentation for their .NET applications, streamlining compliance and onboarding processes.

Quick Start

Use the cencon-generate skill to analyze the current .NET project and generate documentation files.

Frequently Asked Questions about cencon-generate

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

FAQPage Schema
How do I generate architecture documentation from .NET source code?

Generating architecture documentation from .NET source code is done by analyzing .cs and .csproj files to produce an architecture_manifest.yaml, security_profile.yaml, and INDEX.md. This process discovers repository context, containers, components, and external systems.

What is the best way to keep .NET security documentation up-to-date with my codebase?

Keeping .NET security documentation up-to-date is achieved through code-driven analysis that generates a security_profile.yaml directly from the source. This reduces manual errors and prevents documentation drift by reflecting the actual codebase.

Can I preview .NET architecture documentation changes before committing them?

Previewing .NET architecture documentation changes is supported through dry-run and diff view modes. These modes analyze the .NET source code and display the potential changes to the architecture_manifest.yaml without altering the actual files.

Does automated .NET documentation generation work without external dependencies?

Automated .NET documentation generation works without external dependencies, relying solely on analyzing .cs and .csproj files. It discovers containers, components, and external systems directly from the repository context.

How does CenCon documentation handle external system discovery in .NET projects?

CenCon documentation handles external system discovery by analyzing the .NET source code structure and project files. It extracts information about connected external systems and documents them within the architecture_manifest.yaml.