Skills architecture-patterns
📦

architecture-patterns

Content revision r2 Safe 🔑 Env variables⚙️ External commands

Design Maintainable Backend Architectures

Complex backend systems become difficult to test and change when dependencies cross domain boundaries. This skill applies Clean Architecture, Hexagonal Architecture, and DDD patterns.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "architecture-patterns" from https://skillstore.io/skills/sickn33-architecture-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-architecture-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-architecture-patterns.md Signed manifest GET /api/skills/sickn33-architecture-patterns/manifest Signed lockfile GET /api/skills/sickn33-architecture-patterns/lockfile

Test it

Using "architecture-patterns". Choose an architecture for a small CRUD service with one database and limited domain logic.

Expected outcome:

  • Recommendation: Use a simple layered architecture; full DDD would add unnecessary complexity.
  • Boundaries: Keep business rules in a small application layer and isolate database access behind a repository.
  • Validation: Test business rules without the database and add integration tests for the repository.

Using "architecture-patterns". Plan an incremental migration for controllers that contain HTTP handling, business rules, and database queries.

Expected outcome:

  • Current risk: Controllers combine transport, business decisions, and persistence.
  • First step: Extract one use case and define a repository interface around existing database behavior.
  • Validation: Preserve API contracts, compare results, and retain a rollback path for each extraction.

Security Audit

Safe
v5 • 7/23/2026 Open versioned report

All 13 static findings are false positives in documentation and illustrative Python examples. API-key references use dependency injection, SQL uses placeholders, and backticks format Markdown; no malicious intent or prompt injection was found.

2
Files scanned
531
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

🔑 Env variables (2)
resources/implementation-playbook.md:332 resources/implementation-playbook.md:334
⚙️ External commands (3)
SKILL.md:37 SKILL.md:41 SKILL.md:45
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-architecture-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-architecture-patterns/security.svg)](https://skillstore.io/skills/sickn33-architecture-patterns?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-architecture-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-architecture-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-architecture-patterns.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). architecture-patterns security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-architecture-patterns/audits/5

BibTeX citation

@techreport{sickn33-sickn33-architecture-patterns-2026, author = {sickn33}, title = {architecture-patterns security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-architecture-patterns/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "architecture-patterns security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-architecture-patterns/audits/5" identifiers: - type: other value: "skillstore:sickn33-architecture-patterns:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

4 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
wshobson Recommended

wshobson-architecture-patterns

Skillstore Score 78
Evidence Confidence High
Skillstore usage 21
Updated

2026-08-21

AdamManuel-dev

adammanuel-dev-architecture-patterns

Skillstore Score 78
Evidence Confidence High
Skillstore usage 13
Updated

2026-08-21

Barnhardt-Enterprises-Inc

barnhardt-enterprises-inc-architecture-patterns

Skillstore Score 78
Evidence Confidence High
Skillstore usage 9
Updated

2026-08-21

sickn33 Current

sickn33-architecture-patterns

Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Design a new backend

Select a pattern and define boundaries for a new service with clear domain rules and infrastructure adapters.

Plan monolith decomposition

Map coupling, identify bounded contexts, and create incremental migration steps for an established application.

Set team standards

Create shared dependency rules, interface conventions, and review checks for consistent backend architecture.

Try These Prompts

Choose a pattern 
I am building [system] with [requirements]. Compare Clean Architecture, Hexagonal Architecture, and DDD, then recommend the simplest suitable approach.
Define system boundaries 
Analyze this backend: [context]. Define layers, modules, interfaces, dependency directions, and infrastructure adapters. Explain each boundary.
Plan a migration 
Create an incremental migration plan for [current architecture]. Identify coupling risks, extraction order, compatibility measures, tests, and rollback checks.
Review an architecture 
Review [architecture description] against Clean Architecture, Hexagonal Architecture, and DDD. Find boundary violations, justify tradeoffs, and propose prioritized corrections with validation criteria.

Best Practices

  • Start with domain constraints and quality targets before selecting a pattern.
  • Keep dependencies pointing toward domain logic and isolate frameworks behind interfaces.
  • Migrate incrementally and verify behavior with unit, integration, contract, and rollback checks.

Avoid

  • Applying full DDD to simple CRUD systems without domain complexity.
  • Moving business rules into controllers, ORM models, or external service adapters.
  • Creating abstractions without a concrete boundary, substitution need, or testability benefit.

Frequently Asked Questions

Which architecture patterns does this skill cover?
It covers Clean Architecture, Hexagonal Architecture, and strategic and tactical Domain-Driven Design patterns.
Does this skill generate production-ready code?
No. It provides illustrative structures and examples that require completion, testing, security review, and adaptation.
Is this skill suitable for microservices?
Yes, when domain boundaries and independent deployment needs justify decomposition. It also warns against unnecessary complexity.
Must every project use Domain-Driven Design?
No. The guidance recommends matching architecture depth to domain complexity and using simpler structures for basic CRUD systems.
How does the skill address failure-prone workflows?
It recommends durable execution at the infrastructure layer for payments, fulfillment, and other multi-step workflows.
What information should I provide?
Provide domain boundaries, current coupling, constraints, scalability targets, technology choices, migration limits, and success criteria.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/architecture-patterns

Ref

86d877f219e2131f05dd5b37c5e329c71c7b8ec4

Maintenance freshness

7/26/2026

Usage

7 downloads · 120 views

File structure

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md

More from sickn33

View all

Related Skills

View all