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 applications for better maintainability.

56

Quality

51%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

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

Architecture Patterns

Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.

Use this skill when

  • Designing new backend systems from scratch
  • Refactoring monolithic applications for better maintainability
  • Establishing architecture standards for your team
  • Migrating from tightly coupled to loosely coupled architectures
  • Implementing domain-driven design principles
  • Creating testable and mockable codebases
  • Planning microservices decomposition

Do not use this skill when

  • You only need small, localized refactors
  • The system is primarily frontend with no backend architecture changes
  • You need implementation details without architectural design

Instructions

  1. Clarify domain boundaries, constraints, and scalability targets.
  2. Select an architecture pattern that fits the domain complexity.
  3. Define module boundaries, interfaces, and dependency rules.
  4. Provide migration steps and validation checks.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

🧠 Knowledge Modules (Fractal Skills)

1. implementation-playbook

Repository
Dokhacgiakhoa/antigravity-ide
Last updated
Created

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.