Development Skill
Angular Migration
Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and…
$15
Architecture Patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal…
An implementation guide for proven backend architecture patterns: Clean Architecture, Hexagonal (Ports & Adapters), and Domain-Driven Design. It shows how to keep business logic independent of frameworks and databases, with full worked code for entities, use cases, repositories, ports, adapters, value objects, and aggregates, plus enterprise resilience patterns like circuit breakers and graceful degradation.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category Development
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
Clean Architecture is earned, not defaulted. The first check is whether the domain justifies the layers at all; only then do ports, adapters and DDD tactics go in:
- Starts with the over-engineering check: simple CRUD does not get clean architecture; every added layer must answer what would be lost without it.
- Lays the layers so dependencies only point inward: entities and abstract interfaces live in the domain, use cases orchestrate business rules, adapters implement, frameworks and drivers stay at the outermost ring.
- The domain defines ports (IUserRepository, PaymentGatewayPort, NotificationPort) and infrastructure provides the adapters (Postgres, Stripe, Mock), so the core is testable with zero database or external service.
- Runs the DDD tactical pass: value objects immutable and self-validating, aggregates as consistency boundaries with the root as the only entry point, repositories defined only on aggregate roots, cross-context communication via domain events.
- External systems pass through an anti-corruption layer: a Stripe charge.succeeded webhook becomes a domain PaymentCompleted event; foreign data shapes, retries and timeouts never leak into the core.
- Wraps every external call in resilience patterns: circuit breaker opening after five consecutive failures with a 30-second half-open probe, graceful degradation so the site keeps working, exponential backoff retry that never retries on 4xx.
One power source. 6 lines out.
architecture-patterns · core
core active · 6 lines
- ✓ designing a new backend
Designing a new backend system with clear separation of concerns
- ✓ refactoring a tightly co…
Refactoring a tightly coupled monolith for testability and maintainability
- ✓ implementing the depende…
Implementing the dependency rule so the domain doesn't depend on frameworks
- ✓ modeling a domain with b…
Modeling a domain with bounded contexts, aggregates, and value objects
- ✓ swapping infrastructure…
Swapping infrastructure (DB, payment provider) without touching the core
- ✓ adding circuit breakers
Adding circuit breakers and graceful degradation to external integrations
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
A core you can unit-test without a database, UI, or external services
license: perpetual -
Freedom to swap technologies by writing a new adapter, not rewriting logic
license: perpetual -
Lower cognitive load and cleaner boundaries via bounded contexts
license: perpetual -
A resilient system that keeps running when an external service goes down
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Clean Architecture directory structure with full entity/use-case/adapter code
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Backend engineers and architects building or refactoring complex systems that need to stay testable and maintainable at scale.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
Does this assume a particular language or framework?
The patterns are language-agnostic by design, since the whole point is keeping the domain independent of any framework, and they come with full worked code for entities, use cases, repositories, ports, and adapters. The patterns don't dictate a stack; you adapt the examples to yours.
-
Won't Clean and Hexagonal just add layers of indirection I don't need?
For a complex system that indirection is what makes the domain testable without a database or framework attached. The cost is real, which is why the guidance aims at systems that need to stay maintainable, not throwaway scripts.
-
I'm building a basic CRUD app, is this the right fit?
Probably not; these patterns earn their keep when business logic is complex and long-lived, and on simple CRUD they're overhead. Reach for them when coupling is actively hurting testability, not preemptively.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.