feat(hub-guide): add 'ask when ambiguous' principle across skills

- Add principle #25 to engineering-principles: 'Ask When Ambiguous' - Add 'Ask When Ambiguous' section to design-patterns and clean-architecture - Update detect-project.sh hook to reinforce ask-don't-assume behavior
2026-07-25 12:05:00 +07:00
parent 80feaf2f16
commit 3a559a58f6
4 changed files with 27 additions and 0 deletions
@@ -81,6 +81,13 @@ When the task calls for it, load:

 - **[references/catalog.md](references/catalog.md)** — Full GoF pattern catalog with code examples, real-world usage, modern alternatives, and "when to NOT use" guidance for each pattern.

+## Ask When Ambiguous
+
+When multiple patterns could apply, present a brief comparison and ask which direction fits:
+- "This could use Strategy (if algorithms vary) or polymorphism on a factory (if types vary). Which axis of change do you expect to grow?"
+- If you're unsure what pattern fits, say so. Don't force a pattern where a simple function suffices.
+- If the problem is too vague to pattern-match, ask clarifying questions first. A pattern chosen on partial input is technical debt.
+
 ## Anti-patterns

 - ❌ **Pattern for pattern's sake** — a simple function is better than a Strategy class with one implementation