skills/docs/readme-gen/SKILL.md
Use when generating README files from project analysis.
npx skillsauth add faysilalshareef/dotnet-ai-kit readme-genInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
# {Company}.{Domain}.{Side}
{Brief description of what this service does}
## Badges


## Overview
{One-paragraph description of the service purpose and role in the system}
## Architecture
This is the **{side}** service in the {Domain} microservice system.
```mermaid
graph LR
GW[Gateway] -->|gRPC| THIS[This Service]
THIS -->|Events| SB[Service Bus]
THIS -->|SQL| DB[(Database)]
# Clone
git clone {repo-url}
cd {repo-name}
# Restore and build
dotnet restore
dotnet build
# Run (requires local SQL Server)
dotnet run --project src/{Company}.{Domain}.{Side}
cd {domain}-apphost
dotnet run
src/
{Company}.{Domain}.{Side}/ # Main application
{Company}.{Domain}.{Side}.Domain/ # Domain entities
{Company}.{Domain}.{Side}.Application/ # Handlers, queries
{Company}.{Domain}.{Side}.Infrastructure/ # DB, Service Bus
tests/
{Company}.{Domain}.{Side}.Tests/ # Unit + integration tests
| Event | Description | |---|---| | OrderCreated | New order created | | OrderUpdated | Order details changed |
| Service | RPC | Description | |---|---|---| | OrderQueries | GetOrder | Get order by ID | | OrderQueries | GetOrders | List with pagination |
Key configuration in appsettings.json:
| Key | Description | Required |
|---|---|---|
| ConnectionStrings:DefaultConnection | SQL Server | Yes |
| ServiceBus:ConnectionString | Azure Service Bus | Yes |
| ExternalServices:QueryServiceUrl | Query service URL | Yes |
dotnet test # All tests
dotnet test --filter Unit # Unit tests only
dotnet test --filter Integration # Integration tests only
See Deployment Runbook for detailed instructions.
### Umbrella README (Multi-Service)
```markdown
# {Company} {Domain} Platform
## System Overview
{Domain} is a microservice platform using CQRS + Event Sourcing.
## Services
| Service | Repository | Purpose |
|---|---|---|
| Command | [{domain}-command]({url}) | Event sourcing, business logic |
| Query | [{domain}-query]({url}) | Read projections (SQL) |
| Cosmos Query | [{domain}-cosmos-query]({url}) | Read projections (Cosmos) |
| Processor | [{domain}-processor]({url}) | Event routing |
| Gateway | [{domain}-gateway]({url}) | REST API |
| Control Panel | [{domain}-controlpanel]({url}) | Admin UI |
## Architecture
```mermaid
graph LR
CP[Control Panel] -->|REST| GW[Gateway]
GW -->|gRPC| CMD[Command]
GW -->|gRPC| QRY[Query]
CMD -->|Events| SB[Service Bus]
SB --> QRY
SB --> PROC[Processor]
See Onboarding Guide for complete setup.
### Analysis for README Generation
```bash
# Detect project type
find . -name "*.csproj" | head -5
# Get .NET version
grep "TargetFramework" Directory.Build.props 2>/dev/null || \
grep "TargetFramework" src/*/*.csproj | head -1
# Find main entry point
find . -name "Program.cs" -path "*/src/*" | head -3
# Find gRPC services
grep -r "MapGrpcService\|MapScalarApiReference" --include="*.cs" src/
# Find tests
find . -name "*Tests*" -type d | head -5
| Anti-Pattern | Correct Approach | |---|---| | Manually written README that goes stale | Generate from project analysis | | Missing setup instructions | Always include prerequisites and steps | | No architecture overview | Include Mermaid diagram | | Copy-paste from other projects | Analyze this specific project | | README without badges | Add build status and .NET version badges |
# Find existing README
find . -name "README.md" -maxdepth 2
# Check README content
head -20 README.md 2>/dev/null
# Find documentation directory
ls docs/ 2>/dev/null
data-ai
Use when about to claim work is complete, fixed, passing, or ready — before committing, creating PRs, or moving to the next task. Requires running verification commands and confirming output before making any success claims.
development
Use when encountering any bug, test failure, build error, or unexpected behavior — before proposing fixes or making changes.
development
Use when checkpointing, wrapping up, or handing off an AI-assisted development session.
development
Use when following the Specification-Driven Development lifecycle from plan through ship.