What is the primary goal of Screaming Architecture?

The primary goal is to ensure that the folder structure of a project clearly communicates the business purpose and features of the application, rather than just the technical frameworks or libraries being used.

What are the rules for dependencies between features?

Features should only import from another feature's public API (the barrel file). They should never import internal implementation details or create circular dependencies.

Why does it discourage the use of index.tsx for components?

Using descriptive filenames (e.g., add-todo-form.tsx) instead of index.tsx makes searching for files easier in IDEs and prevents confusion when multiple 'index' files are open in tabs.

How does this skill handle shared code?

It implements a 'common' directory for truly generic utilities used by three or more features, while keeping feature-specific logic strictly isolated within its respective feature folder.

Screaming Architecture

Name: Screaming Architecture
Author: acbcdev

byacbcdev

0•

开发者工具

Organizes codebases by business feature intent rather than technical framework layers to improve discoverability and scalability.

The Screaming Architecture skill provides a standardized framework for structuring projects so their purpose is immediately obvious from the folder hierarchy. By moving away from technical grouping (like /components or /services) and toward domain-driven grouping (like /features/auth or /features/payments), this skill helps developers build highly maintainable, scalable, and navigable applications. It includes strict guidelines for co-location, naming conventions, barrel file management, and dependency rules to ensure a clean separation of concerns.

主要功能

01Feature-based organization that groups components, hooks, and logic by domain

020 GitHub stars

03Strict co-location rules for tests, styles, and sub-components

04Standardized naming conventions using kebab-case and descriptive filenames

05Controlled public API exports via optimized barrel files (index.ts)

06Clear dependency mapping to prevent circular imports and architectural leaking

使用场景

01Scaling a growing React or TypeScript application into an enterprise-grade codebase

02Refactoring legacy projects organized by technical type into domain-driven structures

03Onboarding new developers quickly by making the business logic visible at the file level

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add acbcdev/claude-code skills

For use in Claude.ai and ChatGPT

Download Skill