Does this skill work with .NET and React Native?

Yes, it is specifically designed for .NET and React Native environments, though the architectural principles are applicable to many backend frameworks.

What happens if Claude is unsure about a requirement?

The skill includes built-in escalation triggers that instruct the agent to stop work immediately and ask for human clarification if requirements are ambiguous or conflict with policies.

What architectural patterns does this skill enforce?

It primarily enforces 'Screaming Architecture' using Vertical Slices, where code is organized by feature folders rather than technical layers.

How does the skill manage dependency directions?

It ensures a strict flow where Controllers depend on Services, and Services depend on Repositories, while preventing features from depending on each other except via a 'Common' directory.

Architectural Agent Contract

Name: Architectural Agent Contract
Author: ReneBossen

byReneBossen

API Development

Enforces strict architectural patterns and behavioral guarantees for AI agents to ensure code integrity and maintainability.

About

The Agent Contract skill establishes a non-negotiable framework for Claude, ensuring it adheres to high-level design principles like Screaming Architecture and Vertical Slices. By defining rigid dependency directions—from Controllers to Services to Repositories—and mandating specific quality gates, this skill prevents architectural drift and technical debt. It includes a robust escalation protocol that forces the agent to stop and seek human clarification whenever it encounters ambiguity, policy violations, or the need for new dependencies, making it an essential tool for teams requiring deterministic and reviewable AI-generated code.

Key Features

Screaming Architecture & Vertical Slice enforcement
0 GitHub stars
Automated quality gates for compilation and test passing
Mandatory traceability for every code decision and assumption
Strict dependency direction validation (Controller → Service → Repository)
Defined escalation triggers for human-in-the-loop clarification

Use Cases

Maintaining architectural consistency across complex .NET backend services
Onboarding AI agents to projects with strict compliance and documentation standards
Preventing business logic leakage into controllers or data access layers

About

Key Features

Screaming Architecture & Vertical Slice enforcement
0 GitHub stars
Automated quality gates for compilation and test passing
Mandatory traceability for every code decision and assumption
Strict dependency direction validation (Controller → Service → Repository)
Defined escalation triggers for human-in-the-loop clarification

Use Cases

Maintaining architectural consistency across complex .NET backend services
Onboarding AI agents to projects with strict compliance and documentation standards
Preventing business logic leakage into controllers or data access layers