CtrlK
BlogDocsLog inGet started
Tessl Logo

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing ...

74

1.17x

Quality

62%

Does it follow best practices?

Impact

94%

1.17x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-architecture-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

86%

15%

Inventory Management Backend — Architecture Design

Clean Architecture structure and dependency rules

Criteria
Without context
With context

Standard directory structure

60%

70%

Domain interfaces directory

0%

100%

No framework imports in domain

100%

100%

Dependencies point inward

70%

100%

Rich domain model

100%

100%

Thin controller

90%

100%

Use case orchestrates via interface

100%

100%

Repository entity mapping

25%

37%

Test independence

100%

100%

README describes dependency direction

66%

100%

Value objects in domain

16%

0%

Without context: $0.8451 · 2m 47s · 42 turns · 87 in / 11,856 out tokens

With context: $1.1659 · 3m 30s · 51 turns · 48 in / 14,584 out tokens

100%

3%

Multi-Channel Notification Service — Architecture Design

Hexagonal Architecture ports and adapters

Criteria
Without context
With context

Distinct ports directory

100%

100%

Ports are abstract interfaces

100%

100%

Focused single-channel interfaces

62%

100%

Core depends only on ports

100%

100%

No framework imports in core

100%

100%

Concrete adapter implements port

100%

100%

Mock adapter for testing

100%

100%

Test uses mock adapter

100%

100%

Thin entry-point

100%

100%

README explains ports vs adapters

100%

100%

Adapters in separate directory

100%

100%

Without context: $1.1673 · 3m 59s · 48 turns · 48 in / 18,343 out tokens

With context: $1.4128 · 4m 38s · 50 turns · 297 in / 19,698 out tokens

96%

24%

E-Commerce Order Fulfillment — Domain Model and Resilient Workflow

DDD tactical patterns and durable execution for failure-prone workflows

Criteria
Without context
With context

Value object is immutable

100%

100%

Value object validates itself

100%

100%

Aggregate enforces invariants

100%

100%

Aggregate stores related IDs

100%

100%

Domain events on state change

100%

100%

Repository publishes and clears events

0%

50%

Rich entity behavior

100%

100%

DBOS workflow decorator

0%

100%

DBOS step decorators

0%

100%

Abstract repository interface

100%

100%

README explains aggregate design

100%

100%

No framework imports in domain

100%

100%

Domain events are dataclasses

100%

100%

Without context: $1.4236 · 5m 3s · 44 turns · 50 in / 22,802 out tokens

With context: $1.8256 · 5m 54s · 55 turns · 60 in / 23,922 out tokens

Repository
boisenoise/skills-collections
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.