16 lines
649 B
Markdown
16 lines
649 B
Markdown
|
# Facade Pattern
|
||
|
|
|
||
|
|
## Description
|
||
|
|
Provide a unified interface to a set of interfaces in a subsystem, hiding the implementation details of the subsystem.
|
||
|
|
|
||
|
|
## Use Cases
|
||
|
|
Load this skill when you need to solve design problems described by this pattern in your code.
|
||
|
|
|
||
|
|
## Guidelines
|
||
|
|
1. Analyze whether current code structure matches the pattern's intent.
|
||
|
|
2. Refactor or implement following the pattern's typical structure.
|
||
|
|
3. Ensure the pattern introduction reduces coupling or improves flexibility.
|
||
|
|
|
||
|
|
## Detailed Reference
|
||
|
|
For more details, diagrams, and code examples: [Facade Pattern - RefactoringGuru](https://refactoringguru.cn/design-patterns/facade)
|