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

feat: mark clean-code & clean-architecture as MANDATORY

Browse Source 
- Add MANDATORY prefix to clean-code and clean-architecture descriptions
- Change 'core skills' to 'mandatory' in detect-project.sh output
- Both skills now always active, not just context-triggered
This commit is contained in:
asepharyana
2026-07-25 13:07:10 +07:00
parent a0f8796ebd
commit 0aebde93ea
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/clean-code/SKILL.md
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: clean-code
description: Apply Robert C. Martin's (Uncle Bob's) Clean Code, Clean Architecture, and Clean Craftsmanship principles when writing, reviewing, or refactoring code. Use this skill whenever the user asks to write new code of non-trivial size, refactor existing code, review code for quality, design a module or system boundary, write tests, or the user mentions clean-code concepts in any language. Also engage proactively from code quality signals — poor naming, long functions, deep nesting, unclear abstractions — regardless of spoken language. Detects from code context and project files — not dependent on specific language keywords.
description: MANDATORY — always active. Clean Code principles: naming, functions, comments, formatting, error handling, classes. Apply to every session regardless of context. Use whenever the user writes code, reviews code, refactors, or mentions clean-code concepts in any language. Also engage proactively from code quality signals — poor naming, long functions, deep nesting, unclear abstractions. Works regardless of spoken language.
---
# Clean Code