Update documentation, workflows, and best practices

- Added a new funding platform in `FUNDING.yml`.
- Overhauled `copilot-instructions.md` with a role description.
- Introduced `.NET architect` and `Code Reviewer` guidelines.
- Added best practices for .NET Core in `solution_architect.mdc`.
- Updated GitHub Actions to include `develop` branch triggers.
- Improved `nuget-publish.yml` syntax for environment variables.
- Upgraded `Roslynator.Analyzers` to version 4.14.1.
- Removed unnecessary `genocs.cli.csproj.user` file.
- Added "Documentation Writer Mode" for API and code documentation.

Author: giovanninocco

.cursor/rules/solution_architect.mdc

@@ -0,0 +1,88 @@
+---
+description: This rule provides comprehensive best practices for developing dotnet applications, covering code organization, security, performance, testing, and common pitfalls. It aims to improve code quality, security posture, and overall efficiency when working with the .NET Core framework.
+globs: *.tf,*.bicep,*.json,*.yml,*.yaml,*.cs,*.csproj,*.sln
+alwaysApply: false
+---
+
+# .NET Core Library Best Practices and Coding Standards
+
+This document outlines the recommended best practices for developing applications and infrastructure using Microsoft .NET Core, Azure DevOps and Azure services. It covers various aspects including solution setup, code organization, security, and tooling to ensure robust, scalable, and secure solutions.
+
+## 1. Code Organization and Structure
+
+A well-organized codebase is crucial for maintainability, scalability, and collaboration. The following guidelines provide a structured approach to organizing your .NET projects.
+
+### Directory Structure Best Practices
+
+Adopt a modular and logical directory structure based on the application's architecture and components.
+
+*   **`devops/`**: Contains the root folder for DevOps pipelines for your application.
+    *   **`azure/`**: Contains the source code of Azure DevOps pipelines for your application.
+*   **`infrastructure/`**: Contains the source code of IaC and platform setup scripts for your application.
+    *   **`bicep/`**: Contains the source code of Bicep templates for your application.
+    *   **`terraform/`**: Contains the source code of Terraform templates for your application.
+*   **`scripts/`**: Automation scripts for deployment, build processes, etc.
+*   **`src/`**: Contains the source code of your application.
+
+
+Example:
+
+root-project/
+├── .cursor/
+│   └── rules/
+├── .git/
+├── .github/
+│   ├── chatmode
+│   ├── instructions
+│   └── workflows/
+├── devops/
+│   └── azure/
+├── infrastructure/
+│   ├── bicep/
+│   └── terraform/
+├── scripts/
+├── src/
+├── .editorconfig
+├── .gitattributes
+├── .gitignore
+├── CHANGELOG.md
+├── CODE_OF_CONDUCT.md
+├── Directory.Build.props
+├── Directory.Build.targets
+├── dotnet.ruleset
+├── global.json
+├── stylecop.json
+├── nuget.config
+├── project.sln
+└── README.md
+
+
+### File Naming Conventions
+
+Maintain consistency in file naming to improve readability and searchability.
+
+*   Use descriptive names that reflect the file's purpose.
+*   Use a consistent case (e.g., camelCase or kebab-case).
+*   Use appropriate file extensions (e.g., `.cs`, `.csproj`, `.tf`, `.bicep`).
+*   For CSharp components, use `ClassName.cs` or `ComponentName.SubComponent.cs`.
+
+Example:
+
+*   `user-service.js` (for a user service module)
+*   `UserProfile.jsx` (for a user profile component)
+*   `storage-account.tf` (for a Terraform file defining a storage account)
+
+### Module Organization
+
+Divide the application into independent and reusable modules based on functionality.
+
+*   Each module should have a clear responsibility and a well-defined interface.
+*   Minimize dependencies between modules to promote loose coupling.
+*   Consider using a module bundler (e.g., Webpack, Parcel) to manage dependencies and optimize the build process.
+
+Example:
+
+A `user-management` module could contain components and services related to user authentication, authorization, and profile management.
+
+
+By following these best practices, you can build robust, scalable, secure, and maintainable .NET applications.

.github/FUNDING.yml

@@ -1,3 +1,3 @@
 # These are supported funding model platforms
 open_collective: genocs
-custom: ['https://www.buymeacoffee.com/genocs']
+custom: ["https://www.buymeacoffee.com/genocs"]

.github/agents/code_reviewer.agent.md

@@ -0,0 +1,34 @@
+---
+name: code_reviewer
+target: vscode
+description: Review code for quality and adherence to best practices.
+argument-hint: The user will provide code snippets or files to review.
+tools: ["search/codebase", "usages", "vscodeAPI", "problems", "fetch", "githubRepo", "search"]
+---
+
+# Code Reviewer Mode
+
+You are an experienced senior developer conducting a thorough code review. Your role is to review the code for quality, best practices, and adherence to [project standards](../copilot-instructions.md) without making direct code changes.
+
+## Analysis Focus
+
+- Analyze code quality, structure, and best practices
+- Identify potential bugs, security issues, or performance problems
+- Evaluate accessibility and user experience considerations
+- Assess maintainability and readability
+
+## Communication Style
+
+- Provide constructive, specific feedback with clear explanations
+- Highlight both strengths and areas for improvement
+- Ask clarifying questions about design decisions when appropriate
+- Suggest alternative approaches when relevant
+
+## Important Guidelines
+
+- DO NOT write or suggest specific code changes directly
+- Focus on explaining what should be changed and why
+- Provide reasoning behind your recommendations
+- Be encouraging while maintaining high standards
+
+When reviewing code, structure your feedback with clear headings and specific examples from the code being reviewed.

.github/agents/documentation_writer.agent.md

@@ -0,0 +1,22 @@
+---
+name: documentation_writer
+description: Document code and its functionality.
+tools: [search]
+---
+
+# Documentation Writer Mode
+You are a Documentation Writer. Your task is to create clear, concise, and comprehensive documentation for codebases, APIs, libraries, and software projects. You should focus on explaining complex technical concepts in an accessible manner, ensuring that the documentation is useful for both novice and experienced developers.
+
+## Documentation Focus
+- Write clear and concise explanations of code functionality
+- Include usage examples and code snippets where applicable
+- Document any dependencies, configurations, or setup steps required
+- Ensure that the documentation is kept up-to-date with code changes
+
+## Communication Style
+- Use simple, straightforward language
+- Break down complex concepts into manageable sections
+- Use bullet points, numbered lists, and headings to organize information
+- Provide context and background information when necessary
+- Write WebAPI endpoint documentation to be used by MCP server and AI agent along with developers
+- Write the web API endpoint documentation in the OpenAPI format, with short summaries and descriptions for each endpoint, including request and response schemas.

.github/copilot-instructions.md

@@ -1,103 +1,6 @@
-# Genocs CLI - Copilot Instructions
+---
+applyTo: '**'
+---
 
-## Project Overview
-This is a .NET 9 CLI tool packaged as a global dotnet tool (`genocs`) that provides templates for Genocs microservice solutions. The tool generates project scaffolding for various frontend and backend architectures.
-
-## Architecture & Structure
-
-### Core Components
-- **Single executable**: `src/Program.cs` contains all CLI command logic in a top-level program pattern
-- **Template bootstrapping**: Commands call specific `Bootstrap*SolutionAsync()` methods that invoke `dotnet new` with Genocs templates
-- **Command pattern**: Simple string parsing with format `genocs <template-type> <command> <project-name>`
-
-### Supported Templates
-Available via commands like `genocs [template] new CompanyName.ProjectName`:
-- `angular` - Angular frontend projects
-- `react` - React frontend projects  
-- `blazor-clean` - Clean Blazor applications
-- `blazor-wasm` - Blazor WebAssembly projects
-- `clean-webapi` - Clean Architecture Web APIs
-- `libra-webapi` - Libra Web API template
-- `micro-webapi` - Microservice Web API template
-
-### Project Naming Convention
-Uses `ToCapitalCase()` extension method (in `StringExtensions.cs`) to convert input like "company.project" to "Company.Project" format for proper C# namespace conventions.
-
-## Development Workflows
-
-### Building & Testing
-```bash
-# From repository root
-dotnet build
-dotnet run --project src/genocs.cli.csproj -- genocs -i
-
-# From src/ directory  
-dotnet build genocs.cli.csproj
-dotnet run -f net9.0 genocs -i
-```
-
-### Local Installation & Testing
-```bash
-# Pack for local installation
-dotnet pack --output nupkgs
-dotnet tool install --global --add-source ./nupkgs genocs.cli
-
-# Test template installation
-genocs install  # or genocs i
-```
-
-### Template Management
-- `genocs install|i` - Installs/updates Genocs templates from remote repositories
-- `genocs update|u` - Alias for install command
-- Templates are installed via `dotnet new install` commands in bootstrap methods
-
-## Build Configuration
-
-### Project Structure
-- **Single project solution**: Only `src/genocs.cli.csproj` with solution items folder
-- **Global build props**: `Directory.Build.props` enforces StyleCop, Roslynator analyzers, nullable reference types
-- **Tool packaging**: Configured as `<PackAsTool>true</PackAsTool>` with command name `genocs`
-
-### Code Quality
-- **StyleCop + Roslynator**: Enforced via `Directory.Build.props` with custom `stylecop.json` rules
-- **Nullable enabled**: All projects use `<Nullable>enable</Nullable>`
-- **Documentation**: `GenerateDocumentationFile` enabled for XML docs
-- **Global using**: `System.Guid` aliased as `DefaultIdType`
-
-## Key Patterns
-
-### Command Parsing
-Simple imperative parsing in `Program.cs`:
-```csharp
-string firstArg = args[0].Trim().ToLower();
-if (firstArg == "install" || firstArg == "i" || firstArg == "update" || firstArg == "u")
-{
-    await InstallTemplates();
-    return;
-}
-```
-
-### Error Handling
-Basic validation with console output:
-```csharp
-if (args.Length != 3)
-{
-    Console.WriteLine("Invalid command. Use something like: genocs angular new <CompanyName.ProjectName>");
-    return;
-}
-```
-
-### Resource Management
-- `MainResource.resx` for embedded strings/resources
-- `Figgle` dependency for ASCII art rendering
-- `icon.png` and license files embedded in NuGet package
-
-## CI/CD Pipeline
-- **GitHub Actions**: `build_and_test.yml` runs on .NET 9 with restore, build, test, pack
-- **NuGet publishing**: Separate workflow for package deployment
-- **Version management**: `PackageVersion` in csproj, uses SemVer
-
-## Dependencies & External Integration
-- **Figgle**: ASCII art rendering for CLI branding
-- **Genocs Templates**: External template repositories installed via `dotnet new install` 
-- **NuGet**: Published as global tool with command name `genocs`
+You are a experienced software engineer. Your role is to design and oversee the implementation of library components based on .NET Core. Your responsibilities include selecting appropriate pattern and best practice, ensuring security and compliance, optimizing performance and stability.
+Your expertise in Microsoft .NET Core, along with your knowledge of algorithms, security, and DevOps practices, will be crucial in delivering scalable and reliable solutions production ready.

.github/instructions/dotnet_solution_architect.instructions.md

@@ -2,10 +2,9 @@ name: Build test and pack
 
 on:
   push:
-    branches: ["main"]
-
+    branches: [main, develop]
   pull_request:
-    branches: ["main"]
+    branches: [main, develop]
 
 jobs:
   build:

.github/workflows/build_and_test.yml

@@ -41,7 +41,7 @@ jobs:
         run: dotnet test --no-build --verbosity normal
 
       - name: Pack
-        run: dotnet pack -c Debug -o out -p:PackageVersion=${{github.event.inputs.version}} --no-build --verbosity normal
+        run: dotnet pack -c Debug -o out -p:PackageVersion=${{ github.event.inputs.version }} --no-build --verbosity normal
 
       - name: Push packages to Nuget
-        run: dotnet nuget push ./out/*.nupkg -k ${{secrets.NUGET_API_KEY}} -s https://api.nuget.org/v3/index.json --skip-duplicate --no-symbols
+        run: dotnet nuget push ./out/*.nupkg -k ${{ secrets.NUGET_API_KEY }} -s https://api.nuget.org/v3/index.json --skip-duplicate --no-symbols

.github/workflows/nuget-publish.yml

@@ -9,7 +9,7 @@
         <Nullable>enable</Nullable>
     </PropertyGroup>
     <ItemGroup>
-        <PackageReference Include="Roslynator.Analyzers" Version="4.14.0">
+        <PackageReference Include="Roslynator.Analyzers" Version="4.14.1">
             <PrivateAssets>all</PrivateAssets>
             <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets>
         </PackageReference>