3 Commits

Include renames

Author	SHA1	Message	Date
4 people	d29cf651c7	fix(skills): declare activation triggers in descriptions and normalize version metadata (#2618) ... * fix(skills): move version into metadata and normalize to semver 29 skills declared `version` at the top level of their frontmatter. The schema reads it from `metadata`, so tooling that follows the schema either misses it or has to special-case the top level. Three motion skills also declared `version: 1.0`, which is not a valid semantic version; normalized to `1.0.0`. No behavioral change — frontmatter metadata only. * fix(skills): state activation triggers in skill descriptions 148 skills described what they cover but never named the situation that should trigger them. Since the description is what Claude matches against to decide whether to load a skill, a description without a trigger makes activation guesswork — the skill is either missed or loaded at the wrong time. Added a "Use when ..." clause to each, derived from the skill's own body (most already stated the trigger under "## When to Use" or in the opening line; that intent is now reflected in the frontmatter where it is actually read from). Descriptions were only appended to; no existing wording was removed. * fix(skills): sync activation triggers into the Codex skill mirror 10 of the skills whose descriptions changed are also mirrored under `.agents/skills/`, where the description was previously a verbatim copy. Left alone, the two surfaces would disagree about when the skill applies. Only the description line is synced; the Codex copies keep their reduced frontmatter, since that validator accepts only name, description, metadata, license, and allowed-tools. * fix(skills): correct three activation clauses from review - autonomous-loops: the clause pulled new loop work into a skill that its own body marks as a compatibility shim retained for one release. It now points at the canonical continuous-agent-loop instead. - continuous-learning: the description carried the v1 routing directive twice; collapsed to one. - homelab-pihole-dns: the clause fired on any broken home DNS. Narrowed to tasks that actually involve Pi-hole. * chore: retain current main lockfile --------- Co-authored-by: Çağrı Solakoğlu <cagri.solakoglu@vtcenerji.com> Co-authored-by: haelyra <49814733+haelyra@users.noreply.github.com>	2026-08-11 23:58:14 -04:00
Bujidao	86e2a2061a	feat: add Vue ecosystem review support	2026-06-12 19:14:31 +08:00
Bujidao	fe2d6656a3	feat(skills): add vue-patterns skill for Vue.js 3 best practices ... Add skills/vue-patterns/SKILL.md covering: - Project structure (feature-first layout, file naming) - Component architecture (SFC order, presentational vs container, props/emits) - Composables (use prefix, MaybeRef/toValue, cleanup, vs mixins) - State management decision tree (local → props → provide/inject → Pinia → server state) - Vue Router patterns (lazy loading, navigation guards, reactive params) - Template patterns (v-if/v-else, v-show, v-for, v-model with defineModel) - Performance techniques (shallowRef, v-memo, v-once, KeepAlive, Suspense) - Testing stack and patterns (Vitest, Vue Test Utils, Pinia testing) - Nuxt-specific patterns (auto-imports, useAsyncData, server routes, runtime config) - Vue 3.5+ new APIs section: reactive props destructure, useTemplateRef, onWatcherCleanup, useId, defer Teleport, lazy hydration - Anti-patterns table with Vue 3.5+ version-specific notes	2026-06-12 17:54:28 +08:00