The Balanced Coupling model for software design. Use when: designing modular architectures, evaluating coupling between components, reviewing code modularity, deciding whether to split or merge modules/services, assessing integration patterns, classifying coupling as balanced or unbalanced, applying DDD strategic and tactical patterns, reasoning about cohesion vs coupling trade-offs, identifying distributed monolith risks, or explaining why a system is hard to change. Provides the three-dimensional framework (integration strength, distance, volatility) and the balance rule for making coupling decisions.
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
规范化 Excalidraw 图,确保后续可维护编辑、绑定关系安全、编辑器辅助重排和夜间模式安全导出。处理 `.excalidraw` 架构图、拓扑图、流程图或系统图,并且需要修复 container/binding、重排几何布局、清理连接线或导出透明 PNG 到文档时使用。
Use after implementing features, before claiming a phase is complete, when reviewing AI-generated code, or when code feels overly complex. Also use when you notice repeated patterns across files, a function exceeds 40 lines, nesting exceeds 3 levels, or an abstraction has only one implementation. Covers duplication, dead code, over-engineering, and AI-specific bloat patterns like verbose error handling and redundant type checks.
>-
- 📁 .history/
- 📁 references/
- 📄 SKILL.md
Use when preparing for automated authorization testing with Hadrian from an API specification (OpenAPI/Swagger, GraphQL SDL schema, or gRPC proto file) without Burp traffic or source code. Generates Hadrian-compatible auth.yaml and roles.yaml files.
Post-task learning capture and knowledge promotion. Auto-invoke when a task or sprint is completed, when the user says "done", "finished", "wrap up", or when all acceptance criteria are checked off. Do NOT invoke when user says "ship it" — that triggers /ship-test-ensure instead.