Does this skill work for both frontend and backend?

Yes, it is platform-agnostic and provides guidance for Mobile, Web, Backend, Desktop, and CLI applications.

Does it enforce specific coding styles or linting?

No, it focuses on high-level architectural patterns, dependency flow, and structural integrity rather than cosmetic formatting.

How does it decide where business logic belongs?

The skill uses defined heuristics and composition rules to determine if logic should reside in a Use Case, Service, or Repository based on its specific responsibility.

Can it help with refactoring monoliths?

Absolutely. It provides strategies for breaking down monolithic structures into decoupled, feature-based modules that are easier to maintain.

How does it validate dependency rules?

It analyzes the relationships between folders and layers to identify 'inward' violations, ensuring that core business logic never depends on volatile infrastructure like databases or external APIs.

Software Architecture Guide

Name: Software Architecture Guide
Author: bitsydarel

bybitsydarel

0•

Developer Tools

Enforces clean code principles and modular folder structures to ensure loose coupling and high testability across all platforms.

This skill acts as an architectural consultant for Claude Code, providing a standardized framework for designing and refactoring software systems. It guides developers through identifying core components, organizing feature-based folder structures, and making critical decisions regarding logic placement between layers, such as choosing between Services and Repositories. By strictly enforcing inward-flowing dependency rules and isolating business logic from infrastructure details like databases or UIs, it helps maintain long-term codebase health and minimizes the human resources required for system maintenance.

Key Features

01Logic placement heuristics for Services vs. Repositories

02Automated PR review for circular references

03Cross-platform architectural validation

04Inward-flowing dependency enforcement

050 GitHub stars

06Feature-based folder structuring guidelines

Use Cases

01Designing the folder structure for a new feature in a complex monolith or microservice.

02Validating architectural compliance during code reviews to prevent dependency violations.

03Refactoring legacy code to separate domain logic from infrastructure and UI concerns.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add bitsydarel/bdskills bd-software-architecture

For use in Claude.ai and ChatGPT

Download Skill