skills.rest
sridherj
sridherjCOMMUNITY
Explore all skills by this author →
GitHub

mvcs-compliance

Validate codebases against MVCS architectural rules for layering and transactions.

3|3|Updated Apr 7, 2026
Search Tags:#architecture#code review#best practices#mvcs#layer responsibilities
One-click install
npx skills add https://github.com/sridherj/linkedout-oss --skill mvcs-compliance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mvcs-compliance
Source: https://github.com/sridherj/linkedout-oss/tree/main/.claude/skills/mvcs-compliance
Command: npx skills add https://github.com/sridherj/linkedout-oss --skill mvcs-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides detailed guidelines for maintaining proper MVCS (Model-View-Controller-Service) architecture, helping developers create clean, maintainable, and scalable codebases.

Core Features & Use Cases

  • Code Review Assistance: Guides review of code to ensure layer responsibilities are correctly followed, such as services not exposing entities or controllers managing transactions.
  • Architecture Enforcement: Helps teams validate that database queries include tenant and business unit identifiers.
  • Best Practice Validation: Ensures that components like services delegate to other services and that repository methods avoid committing transactions.

Quick Start

Use the mvcs-compliance skill to verify code that handles repository queries and service logic, ensuring adherence to architecture rules and proper layering.

Frequently Asked Questions about mvcs-compliance

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

FAQPage Schema
How do I enforce MVCS architecture and separation of concerns during code review?▼

To enforce MVCS architecture during code review, validate layer responsibilities by ensuring services do not expose entities, controllers manage transactions, and repositories avoid committing transactions.

What is the proper way to manage transactions in an MVCS service-oriented application?▼

In MVCS service-oriented applications, transaction management should be handled by controllers, while repository methods must avoid committing transactions to maintain strict layer responsibilities.

How do I validate data flow from controllers to repositories in an MVCS codebase?▼

Validate data flow from controllers to repositories by ensuring services delegate to other services appropriately and that database queries include required tenant and business unit identifiers.

Can I use this approach to verify that database queries include tenant and business unit identifiers?▼

Yes, you can verify that database queries include tenant and business unit identifiers by applying MVCS architecture enforcement guidelines to validate layer responsibilities and data flow.

Why should services not expose entities in an MVCS architecture?▼

Services should not expose entities in MVCS architecture to maintain strict separation of concerns, ensuring that components delegate properly and supporting maintainability and security standards across the codebase.

Related Skills

Explore More Software Engineering Skills→
changgengluchanggenglu

laravel-architecture

Enforce multi-layer Laravel architecture across controllers, services, repositories, and requests.

Community
Intermediate
VilnaCRM-OrgVilnaCRM-Org
5

deptrac-fixer

Refactor code to fix Deptrac architectural violations without editing deptrac.yaml.

Official
Advanced
inbharataiinbharatai
22

code-reviewer

Analyzes code for bugs, security vulnerabilities, performance bottlenecks, and style violations.

Community
Advanced
gizixgizix
2

mvc-pattern

Scaffold MVC components with observer Model, ttk View, and mediator Controller for Tkinter applications.

Community
Intermediate