Merge main and resolve conflicts for description improvements

Take PR's improved skill descriptions (with "Use when..." trigger phrases) and combine with main's argument-hint format. Drop old args blocks and deleted transformer files. Rebuild all providers so descriptions propagate everywhere. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-09-19 17:46:36 +03:00 · 2026-03-24 15:52:32 -07:00
parent 05f061d247 8303cbbbe2
commit bea7315076
266 changed files with 9806 additions and 7841 deletions
@@ -1,13 +1,7 @@
 ---
 name: adapt
 description: "Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility."
-args:
-  - name: target
-    description: The feature or component to adapt (optional)
-    required: false
-  - name: context
-    description: What to adapt for (mobile, tablet, desktop, print, email, etc.)
-    required: false
+argument-hint: "[target] [context (mobile, tablet, print...)]"
 user-invocable: true
 ---

@@ -15,7 +9,7 @@ Adapt existing designs to work effectively across different contexts - different

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: target platforms/devices and usage contexts.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: target platforms/devices and usage contexts.

 ---

@@ -1,10 +1,7 @@
 ---
 name: animate
 description: "Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive."
-args:
-  - name: target
-    description: The feature or component to animate (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Analyze a feature and strategically add animations and micro-interactions that e

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: performance constraints.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: performance constraints.

 ---

@@ -1,10 +1,7 @@
 ---
 name: arrange
 description: "Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition."
-args:
-  - name: target
-    description: The feature or component to improve layout for (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Assess and improve layout and spacing that feels monotonous, crowded, or structu

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---

@@ -1,16 +1,13 @@
 ---
 name: audit
 description: "Perform a comprehensive audit of interface quality across accessibility, performance, theming, and responsive design. Generates a prioritized report with severity ratings. Use when the user wants a design review, accessibility check, quality audit, or a full list of UI issues to fix."
-args:
-  - name: area
-    description: The feature or area to audit (optional)
-    required: false
+argument-hint: "[area (feature, page, component...)]"
 user-invocable: true
 ---

 Run systematic quality checks and generate a comprehensive audit report with prioritized issues and actionable recommendations. Don't fix issues - document them for other commands to address.

-**First**: Use the frontend-design skill for design principles and anti-patterns.
+**First**: Invoke {{command_prefix}}frontend-design for design principles and anti-patterns.

 ## Diagnostic Scan

@@ -1,10 +1,7 @@
 ---
 name: bolder
 description: "Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character."
-args:
-  - name: target
-    description: The feature or component to make bolder (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Increase visual impact and personality in designs that are too safe, generic, or

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---

@@ -1,10 +1,7 @@
 ---
 name: clarify
 description: "Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing."
-args:
-  - name: target
-    description: The feature or component with unclear copy (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Identify and improve unclear, confusing, or poorly written interface text to mak

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: audience technical level and users' mental state in context.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: audience technical level and users' mental state in context.

 ---

@@ -1,10 +1,7 @@
 ---
 name: colorize
 description: "Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette."
-args:
-  - name: target
-    description: The feature or component to colorize (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Strategically introduce color to designs that are too monochromatic, gray, or la

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: existing brand colors.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: existing brand colors.

 ---

@@ -1,16 +1,13 @@
 ---
 name: critique
 description: "Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback. Use when the user asks to review, critique, evaluate, audit, or give feedback on a design, UI, or component."
-args:
-  - name: area
-    description: The feature or area to critique (optional)
-    required: false
+argument-hint: "[area (feature, page, component...)]"
 user-invocable: true
 ---

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: what the interface is trying to accomplish.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: what the interface is trying to accomplish.

 ---

@@ -1,10 +1,7 @@
 ---
 name: delight
 description: "Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use. Elevates functional to delightful. Use when the user asks to add polish, personality, animations, micro-interactions, delight, or make an interface feel fun or memorable."
-args:
-  - name: target
-    description: The feature or area to add delight to (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Identify opportunities to add moments of joy, personality, and unexpected polish

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant).
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: what's appropriate for the domain (playful vs professional vs quirky vs elegant).

 ---

@@ -1,10 +1,7 @@
 ---
 name: distill
 description: "Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused."
-args:
-  - name: target
-    description: The feature or component to distill (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Remove unnecessary complexity from designs, revealing the essential elements and

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---

@@ -1,10 +1,7 @@
 ---
 name: extract
 description: "Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens."
-args:
-  - name: target
-    description: The feature, component, or area to extract from (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -22,7 +22,7 @@ Individual skills may require additional context — check the skill's preparati
 **Gathering order:**
 1. **Check current instructions (instant)**: If your loaded instructions already contain a **Design Context** section, proceed immediately.
 2. **Check .impeccable.md (fast)**: If not in instructions, read `.impeccable.md` from the project root. If it exists and contains the required context, proceed.
-3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run the teach-impeccable skill NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.
+3. **Run teach-impeccable (REQUIRED)**: If neither source has context, you MUST run {{command_prefix}}teach-impeccable NOW before doing anything else. Do NOT skip this step. Do NOT attempt to infer context from the codebase instead.

 ---

@@ -1,10 +1,7 @@
 ---
 name: harden
 description: "Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues."
-args:
-  - name: target
-    description: The feature or area to harden (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -1,10 +1,7 @@
 ---
 name: normalize
 description: "Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system."
-args:
-  - name: feature
-    description: The page, route, or feature to normalize (optional)
-    required: false
+argument-hint: "[feature (page, route, component...)]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Analyze and redesign the feature to perfectly match our design system standards,

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---

@@ -1,16 +1,13 @@
 ---
 name: onboard
 description: "Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows."
-args:
-  - name: target
-    description: The feature or area needing onboarding (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: the "aha moment" you want users to reach, and users' experience level.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: the "aha moment" you want users to reach, and users' experience level.

 ---

@@ -1,10 +1,7 @@
 ---
 name: optimize
 description: "Diagnoses and fixes UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience."
-args:
-  - name: target
-    description: The feature or area to optimize (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -1,10 +1,7 @@
 ---
 name: overdrive
 description: "Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary."
-args:
-  - name: target
-    description: The feature or area to push into overdrive (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -19,7 +16,7 @@ Push an interface past conventional limits. This isn't just about visual effects

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 **EXTRA IMPORTANT FOR THIS SKILL**: Context determines what "extraordinary" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate.

@@ -1,16 +1,13 @@
 ---
 name: polish
 description: "Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great."
-args:
-  - name: target
-    description: The feature or area to polish (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first. Additionally gather: quality bar (MVP vs flagship).
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first. Additionally gather: quality bar (MVP vs flagship).

 ---

@@ -1,10 +1,7 @@
 ---
 name: quieter
 description: "Tones down visually aggressive or overstimulating designs, reducing intensity while preserving quality. Use when the user mentions too bold, too loud, overwhelming, aggressive, garish, or wants a calmer, more refined aesthetic."
-args:
-  - name: target
-    description: The feature or component to make quieter (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Reduce visual intensity in designs that are too bold, aggressive, or overstimula

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---

@@ -1,10 +1,7 @@
 ---
 name: typeset
 description: "Improves typography by fixing font choices, hierarchy, sizing, weight, and readability so text feels intentional. Use when the user mentions fonts, type, readability, text hierarchy, sizing looks off, or wants more polished, intentional typography."
-args:
-  - name: target
-    description: The feature or component to improve typography for (optional)
-    required: false
+argument-hint: "[target]"
 user-invocable: true
 ---

@@ -12,7 +9,7 @@ Assess and improve typography that feels generic, inconsistent, or poorly struct

 ## MANDATORY PREPARATION

-Use the frontend-design skill — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run teach-impeccable first.
+Invoke {{command_prefix}}frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run {{command_prefix}}teach-impeccable first.

 ---