skills.rest
agnaldo4j
agnaldo4jCOMMUNITY
Explore all skills by this author →
Website𝕏@agnaldo4jGitHub

screaming-architecture

Evaluate software project structures against Screaming Architecture principles.

1|Updated Mar 14, 2026
Search Tags:#architecture#refactoring#code-quality#domain-driven-design#clean-architecture#software-design
One-click install
npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill screaming-architecture-agnaldo4j
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: screaming-architecture
Source: https://github.com/agnaldo4j/kanban-vision-api-kt/tree/main/.claude/skills/screaming-architecture
Command: npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill screaming-architecture-agnaldo4j

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of architectural drift where technical frameworks (like Ktor or Spring) obscure the actual business purpose of a system, making the codebase difficult to navigate and maintain.

Core Features & Use Cases

  • Architectural Evaluation: Analyze existing modules, packages, and classes to ensure they communicate business intent rather than technical implementation.
  • Domain-Driven Design: Validate that core business logic (domain and use cases) remains isolated from delivery mechanisms like HTTP or databases.
  • Use Case: Use this skill when refactoring a legacy module or designing a new feature to ensure that the package structure reflects Kanban domain concepts like boards, cards, and columns instead of technical layers like controllers or services.

Quick Start

Use the screaming-architecture skill to evaluate the current structure of the usecases package and verify if it clearly communicates the business intent.

Frequently Asked Questions about screaming-architecture

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

FAQPage Schema
How do I check if my package structure reflects business intent instead of technical layers?▼

Evaluating package structure for business intent involves analyzing modules and classes to ensure they communicate domain concepts rather than technical implementation. This skill reviews project structures against Screaming Architecture principles to verify that business domain logic remains decoupled from technical frameworks.

What is Screaming Architecture and how does it help with refactoring legacy code?▼

Screaming Architecture is a design principle ensuring code structure reveals business purpose without technical frameworks obscuring it. When refactoring legacy code, it validates that core business logic and use cases remain isolated from delivery mechanisms like HTTP or databases, improving maintainability.

Can I use this approach to isolate domain logic from frameworks like Spring or Ktor?▼

Yes, this approach specifically addresses architectural drift where technical frameworks like Ktor or Spring obscure business purpose. It validates that core domain logic and use cases remain isolated from delivery mechanisms, ensuring clean architecture and testability.

When do I need to apply Domain-Driven Design principles to my module design?▼

You need Domain-Driven Design principles when designing new features or refactoring modules to ensure package structures reflect domain concepts like boards and cards instead of technical layers like controllers. This prioritizes domain clarity over infrastructure concerns.

What's the best way to ensure code quality during architectural refactoring?▼

Ensuring code quality during architectural refactoring requires evaluating software project structures against Screaming Architecture principles. This guarantees business domain logic stays decoupled from technical frameworks, satisfying requirements for clean architecture, testability, and isolation of delivery mechanisms from core business rules.

Why does my codebase become difficult to navigate and maintain over time?▼

Codebases become difficult to navigate due to architectural drift where technical frameworks obscure the actual business purpose of the system. This skill addresses that issue by aligning code structure with business intent and ensuring domain logic remains decoupled from technical implementation.

Related Skills

Explore More Software Engineering Skills→
guyowenguyowen
12

dependency-audit

Audit TypeScript module dependencies to detect circular imports and analyze package coupling.

Community
Intermediate
KentoShimizuKentoShimizu
7

architecture-clean-architecture

Enforce clean architectural boundaries between domain, application, and infrastructure layers.

Community
Intermediate
rajitsaharajitsaha
10

test

Detect and execute unit, integration, and system tests across platforms and languages.

Community
Advanced
EmilLindforsEmilLindfors
2

hexagonal-advisor

Analyze Rust code for hexagonal architecture violations and ports-and-adapters separation.

Community
Advanced