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

fix: add MANDATORY prefix to all 8 core skill descriptions

Browse Source 
- Add MANDATORY — always active to engineering-principles, testing,
  error-handling, security, git-workflow, api-design
- Update hook output with explicit EXTREMELY_IMPORTANT instruction
- Skills now explicitly state they apply to every session
This commit is contained in:
asepharyana
2026-07-26 12:00:04 +07:00
parent 6aaa593181
commit d324c1b3c0
7 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/engineering-principles/SKILL.md
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: engineering-principles
description: Foundational software engineering principles that apply across all languages, frameworks, and project types — correctness, simplicity, YAGNI, KISS, DRY, root-cause fixes, least astonishment, explicit over implicit, fail fast, professional craftsmanship, and multi-agent orchestration for complex tasks. This skill is a baseline: apply these principles to every code decision, review, and architecture discussion, regardless of language or framework. Engage proactively whenever writing, reviewing, or designing code — especially when the user's request seems to violate one of these fundamentals. Detects from code context, project files, and task complexity — not dependent on specific language keywords. Triggers regardless of spoken language when the task is complex, multi-step, or large in scope (see §26 — Workflow orchestration).
description: MANDATORY — always active. Foundational software engineering principles that apply to every code decision, review, and architecture discussion, regardless of language or framework. 29 principles covering correctness, simplicity, YAGNI, KISS, DRY, root-cause fixes, professionalism, never suppress lints, never assume (show evidence), and multi-agent orchestration for complex tasks. Engage proactively whenever writing, reviewing, or designing code — especially when the user's request violates one of these fundamentals. Detects from code context, project files, and task complexity — not dependent on specific language keywords. Use Workflow orchestration for complex multi-step tasks (see §26).
---
# Engineering Principles