dominik/hermes-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add home-assistant-dashboard-conventions skill + update multiple skills

Browse Source 
- New: smart-home/home-assistant-dashboard-conventions (Mushroom cards, view tabs, no Bubble Cards)
- Updated: rke2, ceph, galera, proxmox, brainstorming, compound-learning, 1password-cli, smart-home-automation skills
- New references: ceph-cluster-administration, docker-volume-forensics, ceph-crush-weight, ceph-ec-mixed-size
This commit is contained in:
Debian
2026-07-14 18:35:16 +00:00
parent e9cc106625
commit 01bd921ced
37 changed files with 6133 additions and 126 deletions
Download Patch File Download Diff File Expand all files Collapse all files
software-development/brainstorming/SKILL.md
+2
View File
@@ -120,6 +120,8 @@ During exploration, if the conversation converges on "should we adopt/switch to/
- **Load the skill BEFORE generating brainstorming content.** When a user says "brainstorming first", "let's brainstorm", or similar, load this skill IMMEDIATELY and follow its structured process (one question at a time, multiple choice, incremental validation). Do NOT dump a full ad-hoc analysis first and then load the skill afterward — the structured process IS the value, not the ideas themselves. The user asking for the skill after you've already brainstormed is a correction signal.
- **Load the skill BEFORE writing any code or manifests.** Even if the user doesn't explicitly say "brainstorming", any task that involves building, migrating, or creating something new should trigger this skill FIRST. A user redirecting you from `execute_code` / manifest writing to "use the ce_* skills, starting with brainstorming" is a STRONG correction signal — they expected the structured design process, not premature implementation. This applies to infrastructure migrations, feature development, and configuration changes alike. Even if manifests seem straightforward, the structured exploration reveals design decisions (backup strategy, token handling, archive structure, cutover approach) that would otherwise be discovered too late. When corrected, STOP implementation immediately, delete any prematurely-created files, load the brainstorming skill, and start from Step 1. The full Compound Engineering chain is: brainstorming → writing-plans → (subagent-driven-development | manual execution). Do NOT skip to execution even after the design is approved — produce the implementation plan first via the `writing-plans` skill.
- **One question at a time** — don't overwhelm
- **Multiple choice preferred** — easier to answer than open-ended
- **Incremental validation** — present design, get approval before moving on