symfony-hexagonal-skill

왜 쓰나요

핵심 기능

10 auto-triggered skills for Symfony patterns
2 review agents that catch layering violations
Supports progressive refactor of existing codebases
Templates for Domain, Application, Infrastructure layers
DTO / Command / Query patterns baked in

라이브 데모

실제 사용 모습

symfony-hexagonal-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: symfony-hexagonal-skill

Scaffold a new bounded context with hexagonal layers

👤 Symfony devs building non-trivial domain logic ⏱ ~60 min advanced

언제 쓸까: You're starting a new feature and want the layering right from day one.

흐름

Name the context

Use symfony-hexagonal-skill. Scaffold a 'Billing' bounded context with Invoice aggregate, issue/void commands, and a query for open invoices.✓ 복사됨

→ src/Billing/Domain, Application, Infrastructure folders with proper separation
Wire the infrastructure

Add a Doctrine adapter for InvoiceRepository behind the domain port.✓ 복사됨

→ Interface in Domain, implementation in Infrastructure, services.yaml binding
Expose via controller

Add an HTTP adapter with a POST /invoices endpoint that dispatches the IssueInvoice command.✓ 복사됨

→ Controller calls bus, not repository directly

결과: A clean bounded context that won't turn into spaghetti in 6 months.

함정

Domain depending on Doctrine annotations — Use XML / attribute mapping in Infrastructure, not on domain entities

함께 쓰기: filesystem

Review a PR for hexagonal layering violations

👤 Tech leads on Symfony teams ⏱ ~20 min intermediate

언제 쓸까: Reviewing a PR and you want an automated first-pass on layering.

흐름

Run the review agent

Use symfony-hexagonal-skill review agent on this diff. Flag any Doctrine / Symfony FW imports in Domain/, any controller->repository direct calls, any ORM leakage into responses.✓ 복사됨

→ Concrete findings with file+line
Suggest fixes

For each finding, propose the minimal refactor.✓ 복사됨

→ Diffs introducing a port or DTO

결과: A PR that doesn't silently degrade the architecture.

함께 쓰기: github

Progressively refactor an existing Symfony app toward hexagonal

👤 Teams with a legacy Symfony project ⏱ ~120 min advanced

언제 쓸까: Big-bang rewrite is off the table; you want incremental cleanup.

흐름

Identify a seam

Use symfony-hexagonal-skill. Look at src/Module/Orders — what's the smallest slice I can lift into a clean domain?✓ 복사됨

→ Specific class identified with extraction plan
Extract incrementally

Walk me through the extraction in 3 PR-sized steps.✓ 복사됨

→ Staged plan with tests preserved at each step

결과: A legacy codebase getting better, one PR at a time.

함정

Extracting too much in one step — PR-sized slices only; the plugin's review agent helps gate each step

함께 쓰기: git

조합

다른 MCP와 조합해 10배 효율

symfony-hexagonal-skill + github

Gate PRs on layering review before merge

Run the hex review on the open PR in this repo and post findings as comments.✓ 복사됨

symfony-hexagonal-skill + filesystem

Apply scaffolds into the actual repo

Apply the context scaffold to my project under src/.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
context_scaffold	context name, aggregates	New bounded context
port_adapter_pair	port interface name, adapter type	Adding infrastructure
layering_review	diff or directory	Pre-merge
refactor_plan	legacy module	Starting a cleanup

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Moderate — reviews scan files
금액: Free
팁: Scope reviews to the diff, not whole repos, to save tokens.

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: None from skill

문제 해결

자주 발생하는 오류와 해결

Review agent misses violations

Ensure the full diff is in context; very large diffs may need chunking

Scaffold produces old Symfony 5 style

Mention your Symfony version explicitly — 6 vs 7 conventions differ

대안