sunny:architecture

Design and review .NET, Blazor, and Azure modular monolith architectures.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/kolatts/claude-marketplace --skill sunny-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sunny:architecture
Source: https://github.com/kolatts/claude-marketplace/tree/main/plugins/sunny/skills/architecture
Command: npx skills add https://github.com/kolatts/claude-marketplace --skill sunny-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sunny's architecture principles help teams design, review, and decide on system architectures for .NET/Blazor/Azure deployments, ensuring modular boundaries and clear ownership.

Core Features & Use Cases

  • Guidance on modular monolith boundaries, feature folders, and API-first contracts.
  • Architecture assessment deliverables for design reviews, refactors, and new modules in Azure environments.
  • Real-world usage: create an opinionated design proposal for a new service within an existing app, evaluated against the non-negotiables described in the principles.

Quick Start

Draft an architecture proposal for a new feature in a modular Azure-based system using Sunny's principles.

Frequently Asked Questions about sunny:architecture

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

FAQPage Schema
How do I design a modular monolith architecture in .NET and Azure?

Sunny's architecture principles enforce clear module boundaries using API-first contracts and feature folders for .NET and Azure deployments. They require keeping state in services and avoiding the EF Core repository pattern to ensure explicit ownership and testability.

Why should I avoid the EF Core repository pattern in system design?

Avoiding the EF Core repository pattern ensures clear module boundaries and direct data access in .NET architectures. This rule prevents abstraction leaks and supports explicit ownership and testability across services within a modular monolith.

How do I conduct an architecture design review for a Blazor application?

Conduct an architecture design review by assessing proposals against principles like API-first boundaries and deployment readiness. Evaluate feature folders and technology choices in Blazor applications to ensure modular separation and testability.

Does Sunny's architecture approach work for new features in existing Azure apps?

Sunny's architecture principles work for new features in existing Azure apps by evaluating new services against non-negotiable rules. Create an opinionated design proposal enforcing API-first boundaries and state in services within the existing modular system.

What is the best way to enforce clear module boundaries in a .NET modular monolith?

The best way to enforce clear module boundaries is applying API-first contracts and feature folders. Ensure explicit ownership and deployment readiness by keeping state in services and avoiding the EF Core repository pattern across the .NET modular monolith.