How does this skill handle shared code?

It defines a 'common/' directory for truly generic utilities used by three or more features, ensuring that business logic remains inside feature folders while shared UI or helpers are centralized.

What is the core principle of Screaming Architecture?

The core principle is to group code by its business feature or domain (e.g., 'billing', 'users') rather than its technical type (e.g., 'controllers', 'models'), making the application's purpose obvious from its folder structure.

Why does this skill discourage using index.tsx for components?

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

Does this work with React and TypeScript?

Yes, while the principles are language-agnostic, this skill provides specific patterns for React components, hooks, and TypeScript type organization.

Screaming Architecture Guidelines

Name: Screaming Architecture Guidelines
Author: acbcdev

byacbcdev

0•

Developer Tools

Organizes project files by business feature and domain intent rather than technical framework layers to improve code discoverability.

This skill implements the 'Screaming Architecture' philosophy, ensuring that your project's folder structure clearly communicates its business purpose at first glance. By grouping code by feature (e.g., /features/auth) instead of type (e.g., /components), it reduces cognitive load, minimizes circular dependencies, and simplifies onboarding for new developers. It provides strict patterns for naming conventions, barrel files, and shared utilities, making it ideal for building scalable React, TypeScript, or Node.js applications that remain maintainable as they grow.

Key Features

01Standardized kebab-case naming conventions for files and folders

02Prevention of circular dependencies between domains

03Automated barrel file (index.ts) management for clean public APIs

040 GitHub stars

05Clear separation of global common utilities vs. feature-scoped logic

06Feature-based folder organization and co-location

Use Cases

01Improving developer productivity by making code locations intuitive and predictable

02Bootstraping new projects with scalable architectural best practices

03Refactoring monolithic folder structures into modular, domain-driven features

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add acbcdev/claude-code screaming-architecture

For use in Claude.ai and ChatGPT

Download Skill