ワンクリックでManusで任意のスキルを実行

$pwd:

architecture

Name: Architecture
Author: managedcode

// Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.

Manusで実行

$ git log --oneline --stat

stars:28

forks:2

updated:2026年5月5日 08:04

ファイルエクスプローラー

4 ファイル

SKILL.md

readonly

name	architecture
description	Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
compatibility	Best when project structure, service boundaries, or long-term maintainability are in scope.

.NET Architecture

Trigger On

choosing architecture for a new or evolving .NET system
reviewing layer boundaries, domain boundaries, or service decomposition
deciding whether clean architecture, vertical slices, CQRS, or microservices are justified

Workflow

Start from business capability boundaries and change frequency, not from a preferred diagram style.
Use simple modular monolith patterns by default, and move to microservices only when team autonomy, scale, or deployment boundaries justify the added operational cost.
Apply DDD and CQRS where business rules are genuinely complex; avoid forcing aggregates and command pipelines into CRUD-heavy code with no payoff.
Keep dependencies flowing inward when using clean architecture, but avoid creating extra projects that add ceremony without ownership clarity.
Make integration boundaries explicit: contracts, storage ownership, messaging, consistency model, and observability expectations.
Use aspire when local orchestration, service discovery, and developer observability are part of the architecture story.

Deliver

an architecture direction that matches system complexity
clear project and dependency boundaries
migration notes or tradeoffs when changing an existing structure

Validate

the proposed structure reduces rather than increases accidental complexity
data ownership and integration paths are explicit
the architecture is testable and operable, not just diagram-friendly

References

references/patterns.md - detailed implementations of Clean Architecture, Vertical Slices, DDD, CQRS, Modular Monolith, and Microservices with C# 12+ examples
references/anti-patterns.md - common architectural mistakes including over-abstraction, anemic domain models, premature microservices, and cargo cult patterns

related-skills.json

同じリポジトリ

analyzer-config.md

from "managedcode/Orleans.RateLimiting"

Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.

2026-05-0528

archunitnet.md

from "managedcode/Orleans.RateLimiting"

Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.

2026-05-0528

code-analysis.md

from "managedcode/Orleans.RateLimiting"

Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.

2026-05-0528

complexity.md

from "managedcode/Orleans.RateLimiting"

Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.

2026-05-0528

crap-score.md

from "managedcode/Orleans.RateLimiting"

Calculates CRAP (Change Risk Anti-Patterns) score for .NET methods, classes, or files. Use when the user asks to assess test quality, identify risky untested code, compute CRAP scores, or evaluate whether complex methods have sufficient test coverage. Requires code coverage data (Cobertura XML) and cyclomatic complexity analysis. DO NOT USE FOR: writing tests, general test execution unrelated to coverage/CRAP analysis, or general code coverage reporting without CRAP context.

2026-05-0528

csharpier.md

from "managedcode/Orleans.RateLimiting"

Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.

2026-05-0528

package.json

"author": "managedcode"

"repository": "managedcode/Orleans.RateLimiting"

GitHub リポジトリを開く Creator のリポジトリを見る

$ install --global

$ download --local

Manusで実行

$ useful --forSOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

.NET Architecture

Trigger On

choosing architecture for a new or evolving .NET system

reviewing layer boundaries, domain boundaries, or service decomposition

deciding whether clean architecture, vertical slices, CQRS, or microservices are justified

Workflow

Start from business capability boundaries and change frequency, not from a preferred diagram style.

Use simple modular monolith patterns by default, and move to microservices only when team autonomy, scale, or deployment boundaries justify the added operational cost.

Apply DDD and CQRS where business rules are genuinely complex; avoid forcing aggregates and command pipelines into CRUD-heavy code with no payoff.

Keep dependencies flowing inward when using clean architecture, but avoid creating extra projects that add ceremony without ownership clarity.

Make integration boundaries explicit: contracts, storage ownership, messaging, consistency model, and observability expectations.

Use aspire when local orchestration, service discovery, and developer observability are part of the architecture story.

Deliver

an architecture direction that matches system complexity

clear project and dependency boundaries

migration notes or tradeoffs when changing an existing structure

Validate

the proposed structure reduces rather than increases accidental complexity

data ownership and integration paths are explicit

the architecture is testable and operable, not just diagram-friendly

References

references/patterns.md - detailed implementations of Clean Architecture, Vertical Slices, DDD, CQRS, Modular Monolith, and Microservices with C# 12+ examples

references/anti-patterns.md - common architectural mistakes including over-abstraction, anemic domain models, premature microservices, and cargo cult patterns

architecture

.NET Architecture

Trigger On

Workflow

Deliver

Validate

References

このリポジトリの他の Skills

このリポジトリの他の Skills

.NET Architecture

Trigger On

Workflow

Deliver

Validate

References