Borrowing it
Nothing to install: this file belongs to Genocs/genocs-library. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Genocs/genocs-library/main/.kiro/steering/solution_architect.mdgit clone --depth 1 https://github.com/Genocs/genocs-libraryWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/genocs/genocs-library/solution_architect)<a href="https://agentmods.dev/instructions/genocs/genocs-library/solution_architect"><img src="https://agentmods.dev/badge/instructions/genocs/genocs-library/solution_architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/genocs/genocs-library/solution_architect"><img src="https://agentmods.dev/badge/instructions/genocs/genocs-library/solution_architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00743 | $0.00743 |
| Opus 5.5 | $0.00297 | $0.00297 |
| Sonnet 5.5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
genocs-library solution_architect.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.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.csorComponentName.SubComponent.cs.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 27d ago First seen · 87 lines · 743 tokens per session scan A d012585a64c5
genocs-library solution_architect.md is an instructions file published in the GitHub repository Genocs/genocs-library (4 stars, last pushed 5d ago), licensed MIT. It adds 743 tokens to every session, about $0.0030 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-01.
Other instructions, from other repositories
graftcode graftcode-dotnet.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — .net backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = .net class library.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).