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

entity-pure-business-rules.mdreferences/

title:
Entities Contain Only Enterprise Business Rules
impact:
CRITICAL
impactDescription:
enables reuse across applications, prevents coupling
tags:
entity, business-rules, domain, purity

Entities Contain Only Enterprise Business Rules

Entities encapsulate enterprise-wide business rules that would exist regardless of automation. They must not contain application-specific logic, persistence code, or UI concerns.

Incorrect (entity mixed with infrastructure concerns):

class Invoice {
  id: string
  items: LineItem[]
  status: InvoiceStatus
  dueDate: Date

  calculateTotal(): Money {
    return this.items.reduce((sum, item) => sum.add(item.amount), Money.zero())
  }

  isOverdue(): boolean {
    return this.status === InvoiceStatus.Unpaid && new Date() > this.dueDate
  }

  markPaid(): void {
    this.status = InvoiceStatus.Paid
    database.invoices.update(this)  // Entity cannot be tested without database
    emailService.send(this.customerEmail, 'Payment received')  // Coupled to email system
  }
}

Correct (entity contains only business rules):

class Invoice {
  id: string
  items: LineItem[]
  status: InvoiceStatus
  dueDate: Date

  calculateTotal(): Money {
    return this.items.reduce((sum, item) => sum.add(item.amount), Money.zero())
  }

  isOverdue(): boolean {
    return this.status === InvoiceStatus.Unpaid && new Date() > this.dueDate
  }

  markPaid(): void {
    if (this.status !== InvoiceStatus.Unpaid) {
      throw new InvalidOperationError('Invoice already processed')
    }
    this.status = InvoiceStatus.Paid
  }
}

Benefits:

  • Entity can be used in billing system, reporting system, mobile app
  • Business rules tested without database or email setup
  • Rules documented in one place, not scattered across application

Reference: Clean Architecture - Entities

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