@su-record/vibe 2.7.20 → 2.7.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@su-record/vibe",
-  "version": "2.7.20",
+  "version": "2.7.21",
   "description": "AI Coding Framework for Claude Code — 49 agents, 41+ tools, multi-LLM orchestration",
   "type": "module",
   "main": "dist/cli/index.js",

package/skills/arch-guard/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: arch-guard
-description: "Generate architecture boundary tests that mechanically enforce layer constraints."
+description: "Generate architecture boundary tests that mechanically enforce layer constraints. Use when adding new modules, refactoring layers, or after detecting circular dependencies. Creates import-rule tests (e.g., 'UI must not import DB') that fail CI on violation. Must use this skill when user mentions layer enforcement, dependency rules, or architectural boundaries — even casually like 'make sure services don't import controllers'."
 triggers: [arch guard, architecture test, layer test, boundary test, structural test, arch validation]
 priority: 60
 ---

package/skills/brand-assets/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: brand-assets
-description: "Auto-generate app icons and favicons from SPEC brand information using Gemini Image API"
+description: "Auto-generate app icons (iOS/Android/PWA), favicons, and OG images from SPEC brand information using Gemini Image API. Use when the project needs visual brand assets, when user mentions 'icon', 'favicon', 'logo', or 'brand assets', or when a SPEC defines brand colors/identity but no assets exist yet. Outputs multiple sizes and formats ready for deployment. Not for complex illustration or marketing graphics — focused on app identity assets."
 triggers: [icon, favicon, brand, logo, app icon, branding, assets]
 priority: 65
 ---

package/skills/capability-loop/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: capability-loop
-description: "When an agent fails, diagnose which capability is missing and build it into the repo."
+description: "When an agent fails, diagnose which capability is missing and build it into the repo. Activates after repeated agent failures, tool errors, or when a task keeps failing in the same way. Analyzes failure transcripts, identifies the missing guardrail/tool/abstraction/doc, and creates it permanently. Use this skill whenever you see 3+ similar failures, an agent hitting the same wall repeatedly, or the user asking 'why does this keep failing'."
 triggers: [capability loop, failure loop, build capability, missing capability, agent failed, why did it fail]
 priority: 75
 ---

package/skills/characterization-test/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: characterization-test
-description: "Lock existing behavior with characterization tests before modifying code."
+description: "Lock existing behavior with characterization tests before modifying code. Use BEFORE any refactor, rewrite, or large-scale modification of existing code — especially legacy code without tests. Captures current input/output behavior as test cases so regressions are caught immediately. Must use this skill when touching files >200 lines with no existing tests, when user says 'refactor', 'rewrite', 'modernize', or 'clean up' existing code."
 triggers: [legacy, characterization test, lock behavior, regression prevention, before refactor, large file]
 priority: 65
 ---

package/skills/commerce-patterns/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: commerce-patterns
-description: "E-commerce domain patterns - cart, payment, inventory with transaction safety"
+description: "E-commerce domain patterns — cart management, payment processing (Toss/Stripe/PG), inventory tracking, and order state machines with transaction safety. Use when implementing any shopping cart, checkout flow, payment integration, stock management, or order lifecycle. Covers idempotency keys, double-charge prevention, stock reservation, and refund flows. Must use this skill when the codebase involves e-commerce — even for seemingly simple 'add to cart' features."
 triggers: [commerce, ecommerce, cart, payment, checkout, inventory, stock, order, pg, toss, stripe]
 priority: 70
 ---

package/skills/e2e-commerce/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-commerce
-description: "E2E test scenarios for commerce checkout and payment flows"
+description: "E2E test scenarios for commerce checkout and payment flows. Provides ready-made Playwright test templates for cart→checkout→payment→confirmation flows, including PG sandbox testing (Toss/Stripe), error scenarios (payment failure, timeout, stock exhaustion), and idempotency verification. Use when writing E2E tests for any e-commerce feature — checkout, payment, order status, or refund flows."
 triggers: [e2e commerce, checkout test, payment test, order flow test]
 priority: 65
 ---

package/skills/exec-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exec-plan
-description: "Convert SPEC into a self-contained execution plan that agents can run autonomously for hours."
+description: "Convert SPEC into a self-contained execution plan that agents can run autonomously for hours. Use when a SPEC has 3+ phases, multiple files to change, or complex dependencies between tasks. Produces a plan with explicit file paths, interface extracts, and acceptance criteria so agents never need to 'figure out' context. Must use this skill when launching long-running autonomous work, parallelizing implementation across agents, or when user says 'execute this spec' or 'run this plan'."
 triggers: [exec plan, execution plan, autonomous plan, self-contained plan, long-running]
 priority: 70
 ---

package/skills/parallel-research/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: parallel-research
-description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
+description: "Parallel research with 4 specialized agents (best-practices, framework-docs, codebase-patterns, security-advisory) running simultaneously. Use when facing unfamiliar technology, choosing between libraries/frameworks, designing architecture for a new feature, or investigating security implications. Must use this skill when user asks 'how should we build X', 'which library for Y', or when starting work on a complex feature with unknown requirements. Not for simple lookups — use web search directly for those."
 triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
 priority: 60
 ---

package/skills/seo-checklist/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: seo-checklist
-description: "SEO gotchas for web development - easy-to-miss items that hurt search ranking"
+description: "SEO gotchas for web development — easy-to-miss items that hurt search ranking. Covers meta tags, Open Graph, structured data (JSON-LD), sitemap, robots.txt, canonical URLs, and Naver/Google-specific requirements. Use when building or reviewing any public-facing web page, landing page, or marketing site. Must use this skill when user mentions SEO, search ranking, meta tags, or when deploying a web app that needs to be discoverable."
 triggers: [seo, search, meta, sitemap, schema, structured data, og, opengraph, google, naver]
 priority: 65
 ---

package/skills/ui-ux-pro-max/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ui-ux-pro-max
-description: "UI/UX design intelligence with bold aesthetic direction. 50+ styles, 97 palettes, 57 font pairings, 99 UX guidelines, 25 chart types across 9 stacks."
+description: "UI/UX design intelligence with bold aesthetic direction. Searchable database: 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, 25 chart types across 9 stacks (React, Vue, Svelte, Angular, Astro, Next.js, Flutter, Swift, Kotlin). Use when building any UI component, choosing color schemes, selecting typography, applying design patterns, or reviewing UX compliance. Must use this skill when user builds frontend — pages, components, dashboards, or landing pages — to ensure design quality beyond generic AI output."
 ---
 
 # UI/UX Pro Max - Design Intelligence

package/skills/video-production/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: video-production
-description: "Video processing gotchas — FFmpeg, transcoding, streaming, subtitles."
+description: "Video processing gotchas — FFmpeg commands, transcoding pipelines, HLS/DASH streaming setup, subtitle embedding (SRT/VTT), and thumbnail extraction. Use when the project involves any video manipulation, media processing, or streaming infrastructure. Covers codec selection, bitrate optimization, and common FFmpeg pitfalls. Must use this skill when user works with video files, mentions FFmpeg, or needs media processing — even for simple tasks like 'generate a thumbnail'."
 triggers: [video, ffmpeg, transcode, encode, stream, media, subtitle, thumbnail, hls, dash]
 priority: 60
 ---