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-reuse-release-equivalence.mdreferences/

title:
Release Components as Cohesive Units
impact:
HIGH
impactDescription:
enables version tracking, supports parallel team development
tags:
comp, release, versioning, cohesion

Release Components as Cohesive Units

Classes grouped into a component should be releasable together. A component should have a version number, release notes, and clear documentation. This is the Reuse/Release Equivalence Principle (REP).

Incorrect (arbitrary grouping):

shared-lib/
├── src/
│   ├── auth/
│   │   ├── JwtValidator.ts
│   │   └── PermissionChecker.ts
│   ├── logging/
│   │   └── Logger.ts
│   ├── email/
│   │   └── EmailSender.ts
│   └── payment/
│       └── StripeClient.ts
└── package.json  // version 1.2.3

# Version 1.2.4 fixes JWT bug
# But users of EmailSender must also upgrade
# Changelog unclear which features affect which users

Correct (cohesive releasable components):

packages/
├── auth/
│   ├── src/
│   │   ├── JwtValidator.ts
│   │   ├── PermissionChecker.ts
│   │   └── index.ts
│   ├── CHANGELOG.md        # Auth-specific changes
│   └── package.json        # @company/auth v2.1.0
├── logging/
│   ├── src/
│   │   └── Logger.ts
│   ├── CHANGELOG.md
│   └── package.json        # @company/logging v1.0.3
├── email/
│   ├── src/
│   │   └── EmailSender.ts
│   ├── CHANGELOG.md
│   └── package.json        # @company/email v1.5.0
└── payments/
    ├── src/
    │   └── StripeClient.ts
    ├── CHANGELOG.md
    └── package.json        # @company/payments v3.0.0

# Clear ownership: auth team owns @company/auth
# Independent versioning: JWT fix only bumps auth
# Semantic versioning: breaking change in payments doesn't affect others

Benefits:

  • Teams release independently on their own schedule
  • Version numbers communicate compatibility
  • Changelogs specific to what users of each component care about

Reference: Clean Architecture - Reuse/Release Equivalence Principle

Install with Tessl CLI

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

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