backend-architect
Design and Review Backend Architecture
Backend design reviews often miss dependency problems, code smells, and testing gaps. This skill applies structured architecture guidance and prioritized checklists to propose clear improvements.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "backend-architect" from https://skillstore.io/skills/bikach-backend-architect.md and its manifest at https://skillstore.io/api/skills/bikach-backend-architect/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.
Test it
Using "backend-architect". Review the user registration service for dependency inversion.
Expected outcome:
- P1 - The use case constructs a concrete repository, which couples domain logic to infrastructure.
- Inject a repository port through the constructor and keep its interface in the domain layer.
- Add a unit test with a repository double before changing the dependency.
Using "backend-architect". Design an order cancellation feature using DDD and hexagonal architecture.
Expected outcome:
- Bounded context: Orders owns cancellation rules and order state transitions.
- Use case: Cancel Order validates policy, updates the aggregate, persists through a repository port, and publishes through an event gateway.
- Adapters: HTTP handles transport, persistence maps records, and messaging publishes the cancellation event.
Using "backend-architect". Review a product listing endpoint with slow database access.
Expected outcome:
- P1 - The repository loads related records inside a loop, creating an N+1 query pattern.
- Measure query count, add eager loading for required relations, and verify pagination.
- Add an integration test for query behavior and compare latency before and after the change.
Security Audit
SafeAll 115 static findings are false positives after contextual review. Weak-cryptography alerts matched the French word "des", while other alerts matched harmless identifiers and Markdown formatting. No malicious intent, prompt injection, cryptographic implementation, or automatic command execution was found.
Risk Factors
⚙️ External commands (7)
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.
Copy report link
https://skillstore.io/skills/bikach-backend-architect/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bikach-backend-architect?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bikach-backend-architect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bikach-backend-architect/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bikach-backend-architect.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
Bikach. (2026). backend-architect security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bikach-backend-architect/audits/10BibTeX citation
@techreport{bikach-bikach-backend-architect-2026,
author = {Bikach},
title = {backend-architect security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/bikach-backend-architect/audits/10},
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: "backend-architect security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "Bikach"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bikach-backend-architect/audits/10"
identifiers:
- type: other
value: "skillstore:bikach-backend-architect:audit:10"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
bikach-backend-architect
2026-08-21
sickn33-backend-architect
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Feature architecture for backend developers
Define bounded contexts, ports, adapters, domain models, and dependency direction before implementation.
Code review for technical leads
Review changes for architectural violations, code smells, testing gaps, and performance risks with prioritized feedback.
Legacy refactoring for maintainers
Identify concentrated responsibilities and coupled dependencies, then plan incremental refactoring supported by tests.
Try These Prompts
Review [file or module] for clean code issues. Identify the three most important problems and suggest focused improvements.
Design [feature] for [system] using hexagonal architecture. Define the domain model, use cases, ports, adapters, and dependency direction.
Analyze [module] for documented code smells and SOLID violations. Propose an incremental refactoring plan with tests after each step.
Review [change set] across all affected bounded contexts. Trace dependencies, data flow, testing coverage, and performance risks. Prioritize findings from P0 to P2.
Best Practices
- Provide business requirements, affected files, and architectural constraints.
- Request small, prioritized recommendations with explicit impact and validation steps.
- Run tests and profiling after each refactoring or performance change.
Avoid
- Do not request a full redesign without sharing the current boundaries and constraints.
- Do not apply every pattern when a simpler design meets current requirements.
- Do not refactor behavior without tests that protect the existing contract.