CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/software-design-principles

Apply software design principles across architecture and implementation using deterministic decision workflows, SOLID checks, structural patterns, and anti-pattern detection; use when reviewing designs, refactoring modules, or resolving maintainability and coupling risks.

Review — 93%

Does it follow best practices?

Evaluation — 99%

↑ 1.01x

Agent success when using this tile

Validation — 11 / 11 Passed

Validation for skill structure

Overview
Skills
Evals
Files

comp-common-reuse.mdreferences/

title:
Avoid Forcing Clients to Depend on Unused Code
impact:
HIGH
impactDescription:
reduces unnecessary recompilation and deployment
tags:
comp, common-reuse, dependencies, coupling

Avoid Forcing Clients to Depend on Unused Code

Classes used together should be in the same component. Classes not used together should be in separate components. Forcing a client to depend on things it doesn't use creates unnecessary coupling.

Incorrect (monolithic utility package):

// utils/src/main/java/com/app/utils/
├── StringUtils.java
├── DateUtils.java
├── FileUtils.java
├── HttpUtils.java
├── CryptoUtils.java
├── ImageUtils.java      // Depends on ImageMagick
└── PdfUtils.java        // Depends on iText

// pom.xml for utils module
<dependencies>
    <dependency>imagemagick</dependency>  <!-- 50MB -->
    <dependency>itext-pdf</dependency>     <!-- 20MB -->
    <dependency>bouncycastle</dependency>  <!-- 10MB -->
</dependencies>

// A service that only needs StringUtils
// must now depend on all 80MB of transitive dependencies

Correct (split by usage pattern):

// string-utils/
├── StringUtils.java
└── pom.xml  // No heavy dependencies

// date-utils/
├── DateUtils.java
└── pom.xml

// image-processing/
├── ImageUtils.java
├── ImageResizer.java
└── pom.xml  // ImageMagick dependency only here

// pdf-generation/
├── PdfUtils.java
├── PdfBuilder.java
└── pom.xml  // iText dependency only here

// crypto/
├── CryptoUtils.java
├── HashingService.java
└── pom.xml  // BouncyCastle dependency only here

// Services import only what they need
// order-service depends on string-utils, date-utils (2MB)
// report-service depends on string-utils, pdf-generation (22MB)

Benefits:

  • Clients only pull dependencies they actually use
  • Smaller deployment artifacts
  • Changes to image processing don't redeploy order service

Reference: Clean Architecture - Common Reuse Principle

Install with Tessl CLI

npx tessl i pantheon-ai/software-design-principles

references

adapt-anti-corruption-layer.md

adapt-controller-thin.md

adapt-gateway-abstraction.md

adapt-mapper-translation.md

adapt-presenter-formats.md

anti-patterns-and-frameworks.md

bound-boundary-cost-awareness.md

bound-defer-decisions.md

bound-humble-object.md

bound-main-component.md

bound-partial-boundaries.md

bound-service-internal-architecture.md

comp-common-closure.md

comp-common-reuse.md

comp-reuse-release-equivalence.md

comp-screaming-architecture.md

comp-stable-dependencies.md

dep-acyclic-dependencies.md

dep-data-crossing-boundaries.md

dep-interface-ownership.md

dep-inward-only.md

dep-no-framework-imports.md

dep-stable-abstractions.md

detailed-examples.md

entity-encapsulate-invariants.md

entity-no-persistence-awareness.md

entity-pure-business-rules.md

entity-rich-not-anemic.md

entity-value-objects.md

frame-di-container-edge.md

frame-domain-purity.md

frame-logging-abstraction.md

frame-orm-in-infrastructure.md

frame-web-in-infrastructure.md

test-boundary-verification.md

test-layer-isolation.md

test-testable-design.md

test-tests-are-architecture.md

usecase-explicit-dependencies.md

usecase-input-output-ports.md

usecase-no-presentation-logic.md

usecase-orchestrates-not-implements.md

usecase-single-responsibility.md

usecase-transaction-boundary.md

SKILL-FULL.md

SKILL.md

tile.json