backend-architect

Consult on backend architecture design, review, refactoring, and problem-solving.

88|6|Updated Feb 2, 2026

Search Tags:#architecture #refactoring #design patterns #clean code #backend #ddd #solid

Ready to run

npx skills add https://github.com/FlorianBruniaux/ccboard --skill backend-architect-florianbruniaux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-architect
Source: https://github.com/FlorianBruniaux/ccboard/tree/main/.claude/skills/backend-architect
Command: npx skills add https://github.com/FlorianBruniaux/ccboard --skill backend-architect-florianbruniaux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides expert senior backend architecture guidance to assist throughout the development lifecycle, from initial design to refactoring and problem-solving.

Core Features & Use Cases

Architecture Design: Propose architectural structures, choose patterns, and define boundaries.
Code Review & Refactoring: Analyze code for quality, identify smells, and suggest improvements.
Problem Solving: Diagnose and resolve architectural issues.
Use Case: When designing a new microservice, use this Skill to ensure adherence to hexagonal architecture principles and SOLID.

Quick Start

Use the backend-architect skill to review the proposed changes in the 'feature-x' branch for architectural soundness.

Frequently Asked Questions about backend-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a new microservice using hexagonal architecture and DDD?▼

To design a microservice with hexagonal architecture and Domain-Driven Design, define bounded contexts, isolate domain logic from infrastructure using ports and adapters, and enforce SOLID principles. This approach ensures your core business rules remain decoupled from external frameworks.

What is the best way to refactor code to fix architectural smells and improve clean code?▼

Refactoring code to improve clean code involves analyzing existing structures for architectural smells, extracting domain logic into isolated layers, and applying appropriate design patterns. This process resolves structural degradation and aligns the implementation with SOLID principles.

Can I get a review of my backend design before implementing a new feature?▼

Yes, you can review your backend design before implementation by evaluating proposed changes against architectural boundaries and hexagonal principles. This validates structural soundness, verifies dependency direction, and ensures the design adheres to clean code standards.

When do I need to apply SOLID principles and design patterns in backend architecture?▼

You need to apply SOLID principles and design patterns when structuring new backend systems or resolving complex architectural challenges. These patterns guide dependency inversion and boundary definition, preventing tightly coupled code and ensuring long-term maintainability.

Why does my monolithic backend architecture struggle with testing and feature scaling?▼

Your monolithic backend architecture struggles with testing and scaling because tightly coupled components prevent isolated test execution and boundary enforcement. Applying hexagonal architecture and DDD separates domain logic from infrastructure, resolving these structural bottlenecks.