MythEclipse/asepharyana-hub-guide
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source 
- 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
This commit is contained in:
asepharyana
2026-07-25 12:05:00 +07:00
parent 80feaf2f16
commit 3a559a58f6
4 changed files with 27 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/clean-architecture/SKILL.md
+7
View File
@@ -85,6 +85,13 @@ When the task calls for it, load:
- **[references/solid.md](references/solid.md)** — Full SOLID treatment (SRP, OCP, LSP, ISP, DIP). Component principles (REP, CCP, CRP, ADP, SDP, SAP). Examples for each principle, historical evolution, and practical tests for violations.
## Ask When Ambiguous
When the module boundary is unclear, ask rather than guessing:
- "Should this live in domain or application layer? Is it a pure business rule or an orchestration concern?"
- "Is this a port (interface declared by application) or an adapter (implementation in infrastructure)?"
- If you're not sure which layer a piece of logic belongs to, flag it with a brief question. A wrong boundary assumption is expensive to refactor later.
## Anti-patterns
- ❌ Business logic in route handlers or controllers