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.
Does it follow best practices?
Evaluation — 99%
↑ 1.01xAgent success when using this tile
Validation for skill structure
When integrating with external systems that have different models, build an anti-corruption layer (ACL) that translates between their model and yours. Never let external concepts pollute your domain.
Incorrect (external model leaks into domain):
// Domain polluted with Stripe's model
public class Order {
private String id;
private List<OrderItem> items;
// Stripe-specific fields in domain
private String stripeCustomerId;
private String stripePaymentIntentId;
private String stripePaymentMethodId;
public void processPayment(Stripe stripe) {
// Domain directly calls Stripe
PaymentIntent intent = PaymentIntent.create(
PaymentIntentCreateParams.builder()
.setCustomer(this.stripeCustomerId)
.setPaymentMethod(this.stripePaymentMethodId)
.setAmount(this.calculateTotal().cents())
.setCurrency("usd")
.build()
);
this.stripePaymentIntentId = intent.getId();
}
}
// If we switch to PayPal, Order must changeCorrect (anti-corruption layer isolates external model):
// domain/Order.java - Pure domain, no external concepts
public class Order {
private OrderId id;
private CustomerId customerId;
private List<OrderItem> items;
private PaymentStatus paymentStatus;
public Money calculateTotal() {
return items.stream()
.map(OrderItem::lineTotal)
.reduce(Money.zero(), Money::add);
}
public void markPaid(PaymentReference reference) {
this.paymentStatus = PaymentStatus.paid(reference);
}
}
// domain/ports/PaymentProcessor.java - Domain-defined port
public interface PaymentProcessor {
PaymentResult charge(CustomerId customer, Money amount);
}
// Domain-defined value objects
public record PaymentResult(PaymentReference reference, PaymentStatus status) {}
public record PaymentReference(String value) {}
// infrastructure/stripe/StripePaymentProcessor.java - ACL
public class StripePaymentProcessor implements PaymentProcessor {
private final CustomerMappingRepository customerMapping;
public PaymentResult charge(CustomerId customerId, Money amount) {
// Translate domain CustomerId to Stripe customer
String stripeCustomerId = customerMapping.getStripeId(customerId);
// Call Stripe with their model
PaymentIntent intent = PaymentIntent.create(
PaymentIntentCreateParams.builder()
.setCustomer(stripeCustomerId)
.setAmount(amount.cents())
.setCurrency("usd")
.setConfirm(true)
.build()
);
// Translate Stripe response back to domain model
return new PaymentResult(
new PaymentReference(intent.getId()),
translateStatus(intent.getStatus())
);
}
private PaymentStatus translateStatus(String stripeStatus) {
return switch (stripeStatus) {
case "succeeded" -> PaymentStatus.COMPLETED;
case "processing" -> PaymentStatus.PENDING;
case "requires_action" -> PaymentStatus.REQUIRES_ACTION;
default -> PaymentStatus.FAILED;
};
}
}Benefits:
Reference: Anti-Corruption Layer Pattern
Install with Tessl CLI
npx tessl i pantheon-ai/software-design-principlesevals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
references