스킬 backend-architect
🏗️
backend-architect
안전 ⚙️
외부 명령어🌐
네트워크 접근
設計與審查後端架構
複雜的後端系統需要扎實的架構基礎。此技能提供六角架構、領域驅動設計、SOLID 原則與程式碼品質方面的專家指引，協助你打造可維護且可擴展的應用。
지원: Claude Codex Code(CC)
1
스킬 ZIP 다운로드
2
Claude에서 업로드
설정 → 기능 → 스킬 → 스킬 업로드로 이동
3
토글을 켜고 사용 시작
테스트해 보기
"backend-architect" 사용 중입니다. Review this UserService class for architecture issues
예상 결과:
- P0 - God Class detected: UserService has 15+ methods handling CRUD, email sending, and reporting
- Violation: Single Responsibility Principle - split into separate use cases
- Recommendation: Extract CreateUserUseCase, UserReportService, and move email logic to EmailGateway adapter
"backend-architect" 사용 중입니다. How should I structure a new payment module using DDD?
예상 결과:
- Create bounded context for payments with: Domain layer (Payment entity, PaymentValueObject), Application layer (PaymentUseCase), Infrastructure layer (PaymentRepository adapter)
- Define ports: IPaymentRepository, INotificationGateway in domain/port/
- Implement adapters in infrastructure/ implementing defined interfaces
"backend-architect" 사용 중입니다. What code smells exist in this file?
예상 결과:
- Feature Envy: getUserData() accesses more data from UserRepository than its own class
- Data Clumps: startDate and endDate always appear together - extract DateRange Value Object
- Primitive Obsession: Replace email strings with Email Value Object with validation
보안 감사
안전v5 • 1/16/2026
This is a documentation-only skill containing markdown files with architectural guidance. All 410 static findings are FALSE POSITIVES. The static analyzer incorrectly identifies markdown code block delimiters (triple backticks) as Ruby shell execution, and documentation text patterns as security issues. No executable code, network calls, or filesystem operations exist in this skill.
21
스캔된 파일
3,777
분석된 줄 수
2
발견 사항
5
총 감사 수
위험 요인
⚙️ 외부 명령어 (182)
architecture/ddd-patterns.md:7-12 architecture/dependency-injection.md:13-21 architecture/dependency-injection.md:21-41 architecture/dependency-injection.md:41-49 architecture/hexagonal.md:5-20 architecture/hexagonal.md:20-24 architecture/hexagonal.md:24-41 architecture/hexagonal.md:41-45 architecture/hexagonal.md:45-67 architecture/hexagonal.md:67-72 architecture/hexagonal.md:72-73 architecture/hexagonal.md:73-74 architecture/hexagonal.md:74-79 architecture/hexagonal.md:79-80 architecture/hexagonal.md:80-81 architecture/hexagonal.md:81-82 architecture/hexagonal.md:82-83 checklists/testing-checklist.md:5-13 checklists/testing-checklist.md:13-215 checklists/testing-checklist.md:215-219 checklists/testing-checklist.md:219-222 checklists/testing-checklist.md:222-226 code-smells/data-clumps.md:28-32 code-smells/data-clumps.md:32-35 code-smells/data-clumps.md:35-41 code-smells/data-clumps.md:41-44 code-smells/data-clumps.md:44-48 code-smells/data-clumps.md:48-51 code-smells/data-clumps.md:51-56 code-smells/data-clumps.md:56-59 code-smells/data-clumps.md:59-65 code-smells/feature-envy.md:27-36 code-smells/feature-envy.md:36-64 code-smells/feature-envy.md:64-68 code-smells/feature-envy.md:68-71 code-smells/feature-envy.md:71-75 examples/bad-vs-good-refactoring.md:7-22 examples/bad-vs-good-refactoring.md:22-26 examples/bad-vs-good-refactoring.md:26-42 examples/bad-vs-good-refactoring.md:42-48 examples/bad-vs-good-refactoring.md:48-65 examples/bad-vs-good-refactoring.md:65-69 examples/bad-vs-good-refactoring.md:69-87 examples/bad-vs-good-refactoring.md:87-93 examples/bad-vs-good-refactoring.md:93-105 examples/bad-vs-good-refactoring.md:105-109 examples/bad-vs-good-refactoring.md:109-128 examples/bad-vs-good-refactoring.md:128-134 examples/bad-vs-good-refactoring.md:134-150 examples/bad-vs-good-refactoring.md:150-154 examples/bad-vs-good-refactoring.md:154-178 examples/bad-vs-good-refactoring.md:178-184 examples/bad-vs-good-refactoring.md:184-195 examples/bad-vs-good-refactoring.md:195-199 examples/bad-vs-good-refactoring.md:199-219 examples/bad-vs-good-refactoring.md:219-225 examples/bad-vs-good-refactoring.md:225-253 examples/bad-vs-good-refactoring.md:253-257 examples/bad-vs-good-refactoring.md:257-277 examples/bad-vs-good-refactoring.md:277-283 examples/bad-vs-good-refactoring.md:283-299 examples/bad-vs-good-refactoring.md:299-303 examples/bad-vs-good-refactoring.md:303-330 examples/bad-vs-good-refactoring.md:330-336 examples/bad-vs-good-refactoring.md:336-348 examples/bad-vs-good-refactoring.md:348-352 examples/bad-vs-good-refactoring.md:352-373 examples/bad-vs-good-refactoring.md:373-379 examples/bad-vs-good-refactoring.md:379-397 examples/bad-vs-good-refactoring.md:397-401 examples/bad-vs-good-refactoring.md:401-419 examples/bad-vs-good-refactoring.md:419-425 examples/bad-vs-good-refactoring.md:425-433 examples/bad-vs-good-refactoring.md:433-437 examples/bad-vs-good-refactoring.md:437-450 examples/good-hexagonal-structure.md:5-51 examples/good-hexagonal-structure.md:51-57 examples/good-hexagonal-structure.md:57-64 examples/good-hexagonal-structure.md:64-68 examples/good-hexagonal-structure.md:68-78 examples/good-hexagonal-structure.md:78-82 examples/good-hexagonal-structure.md:82-98 examples/good-hexagonal-structure.md:98-102 examples/good-hexagonal-structure.md:102-114 examples/good-hexagonal-structure.md:114-119 examples/good-hexagonal-structure.md:119-124 examples/good-hexagonal-structure.md:124-127 examples/good-hexagonal-structure.md:127-132 examples/good-hexagonal-structure.md:132-135 examples/good-hexagonal-structure.md:135-142 examples/good-hexagonal-structure.md:142-145 examples/good-hexagonal-structure.md:145-150 examples/good-hexagonal-structure.md:150-153 examples/good-hexagonal-structure.md:153-159 examples/good-hexagonal-structure.md:159-165 examples/good-hexagonal-structure.md:165-177 examples/good-hexagonal-structure.md:177-189 examples/good-hexagonal-structure.md:189-202 examples/good-hexagonal-structure.md:202-206 examples/good-hexagonal-structure.md:206-215 examples/good-hexagonal-structure.md:215-221 examples/good-hexagonal-structure.md:221-234 examples/good-hexagonal-structure.md:234-240 examples/good-hexagonal-structure.md:240-248 examples/good-hexagonal-structure.md:248-252 examples/good-hexagonal-structure.md:252-259 SKILL.md:62 SKILL.md:68 SKILL.md:77 SKILL.md:85 SKILL.md:91 SKILL.md:110 SKILL.md:111 solid-principles/dependency-inversion.md:10-13 solid-principles/dependency-inversion.md:13-17 solid-principles/dependency-inversion.md:17-23 solid-principles/dependency-inversion.md:23-27 solid-principles/dependency-inversion.md:27-35 solid-principles/dependency-inversion.md:35-58 solid-principles/dependency-inversion.md:58-72 solid-principles/dependency-inversion.md:72-77 solid-principles/dependency-inversion.md:77-81 solid-principles/dependency-inversion.md:81-84 solid-principles/dependency-inversion.md:84-90 solid-principles/dependency-inversion.md:90-93 solid-principles/dependency-inversion.md:93-96 solid-principles/dependency-inversion.md:96-155 solid-principles/dependency-inversion.md:155-158 solid-principles/dependency-inversion.md:158-161 solid-principles/dependency-inversion.md:161-165 solid-principles/dependency-inversion.md:165-168 solid-principles/dependency-inversion.md:168-171 solid-principles/dependency-inversion.md:171-174 solid-principles/dependency-inversion.md:174-177 solid-principles/dependency-inversion.md:177-207 solid-principles/dependency-inversion.md:207-219 solid-principles/dependency-inversion.md:219-224 solid-principles/dependency-inversion.md:224-228 solid-principles/dependency-inversion.md:228-231 solid-principles/dependency-inversion.md:231-235 solid-principles/interface-segregation.md:9-11 solid-principles/interface-segregation.md:11-42 solid-principles/interface-segregation.md:42-53 solid-principles/interface-segregation.md:53-56 solid-principles/interface-segregation.md:56-74 solid-principles/interface-segregation.md:74-93 solid-principles/interface-segregation.md:93-99 solid-principles/interface-segregation.md:99-102 solid-principles/interface-segregation.md:102-109 solid-principles/interface-segregation.md:109-112 solid-principles/interface-segregation.md:112-119 solid-principles/interface-segregation.md:119-224 solid-principles/interface-segregation.md:224-234 solid-principles/liskov-substitution.md:9-11 solid-principles/liskov-substitution.md:11-51 solid-principles/liskov-substitution.md:51-61 solid-principles/liskov-substitution.md:61-64 solid-principles/liskov-substitution.md:64-68 solid-principles/liskov-substitution.md:68-71 solid-principles/liskov-substitution.md:71-75 solid-principles/liskov-substitution.md:75-78 solid-principles/liskov-substitution.md:78-82 solid-principles/liskov-substitution.md:82-147 solid-principles/liskov-substitution.md:147-150 solid-principles/liskov-substitution.md:150-153 solid-principles/liskov-substitution.md:153-156 solid-principles/liskov-substitution.md:156-159 solid-principles/liskov-substitution.md:159-162 solid-principles/open-closed.md:9-11 solid-principles/open-closed.md:11-60 solid-principles/open-closed.md:60-65 solid-principles/open-closed.md:65-68 solid-principles/open-closed.md:68-71 solid-principles/open-closed.md:71-74 solid-principles/open-closed.md:74-77 solid-principles/open-closed.md:77-80 solid-principles/open-closed.md:80-83 solid-principles/open-closed.md:83-97 solid-principles/open-closed.md:97-102 solid-principles/open-closed.md:102-105 solid-principles/open-closed.md:105-110 solid-principles/single-responsibility.md:9-11
🌐 네트워크 접근 (1)
감사자: claude 감사 이력 보기 →
품질 점수
38
아키텍처
100
유지보수성
85
콘텐츠
22
커뮤니티
100
보안
83
사양 준수
만들 수 있는 것
設計新系統
為新的後端專案規劃六角架構與限界上下文
程式碼審查指引
檢視團隊程式碼中的架構違規與程式碼異味
重構支援
識別並修正 SOLID 違反、上帝類別等架構問題
이 프롬프트를 사용해 보세요
分析架構
Analyze this codebase for architecture violations. Check if the code follows hexagonal architecture principles and identify any SOLID principle violations.
重構指引
Help me refactor this God Class. What responsibilities should be extracted and how should I structure the new classes?
設計模式
Design the bounded contexts and ports/adapters for a new user management feature using DDD and hexagonal architecture.
檢核清單審查
Use the clean code and testing checklists to review this code. List all issues found with file locations and severity levels.
모범 사례
- 在實作功能前先定義限界上下文
- 讓領域邏輯獨立於基礎設施關注點
- 使用埠與適配器來解耦商業規則與框架
피하기
- 在控制器或適配器中放入商業邏輯
- 在用例中直接使用具體的資料庫類別
- 建立包含多個不相關職責的大型類別
자주 묻는 질문
哪些程式語言支援六角架構？
六角架構與程式語言無關。它適用於 Java、TypeScript、Python、Go，以及任何支援介面與依賴注入的 OO 或 FP 語言。
限界上下文應該多大？
限界上下文應與單一業務能力對齊。其規模可從少量檔案到多個模組，取決於子領域的複雜度。
此技能可以與我現有的程式碼審查工具整合嗎？
此技能提供可手動應用或透過 CI/CD 管線執行的指引。它不會直接與外部工具整合。
我的程式碼資料會送到外部伺服器嗎？
不會。此技能完全在你的 AI 對話中運作，不會將程式碼或資料傳送到外部。
如果我的程式碼庫沒有使用 DDD 模式怎麼辦？
此技能會因應你的情境調整，可提供較簡單的分層架構指引，或協助你逐步遷移至 DDD。
這和靜態分析工具相比如何？
此技能提供人類可讀的架構指引與情境感知建議。靜態分析工具可找出語法問題，並可與此技能互補以進行全面審查。