@kood/claude-code 0.3.12 → 0.3.15

package/templates/.claude/skills/vercel-react-best-practices/SKILL.md

@@ -1,125 +0,0 @@
----
-name: vercel-react-best-practices
-description: React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
-license: MIT
-metadata:
-  author: vercel
-  version: "1.0.0"
----
-
-# Vercel React Best Practices
-
-Comprehensive performance optimization guide for React and Next.js applications, maintained by Vercel. Contains 45 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
-
-## When to Apply
-
-Reference these guidelines when:
-- Writing new React components or Next.js pages
-- Implementing data fetching (client or server-side)
-- Reviewing code for performance issues
-- Refactoring existing React/Next.js code
-- Optimizing bundle size or load times
-
-## Rule Categories by Priority
-
-| Priority | Category | Impact | Prefix |
-|----------|----------|--------|--------|
-| 1 | Eliminating Waterfalls | CRITICAL | `async-` |
-| 2 | Bundle Size Optimization | CRITICAL | `bundle-` |
-| 3 | Server-Side Performance | HIGH | `server-` |
-| 4 | Client-Side Data Fetching | MEDIUM-HIGH | `client-` |
-| 5 | Re-render Optimization | MEDIUM | `rerender-` |
-| 6 | Rendering Performance | MEDIUM | `rendering-` |
-| 7 | JavaScript Performance | LOW-MEDIUM | `js-` |
-| 8 | Advanced Patterns | LOW | `advanced-` |
-
-## Quick Reference
-
-### 1. Eliminating Waterfalls (CRITICAL)
-
-- `async-defer-await` - Move await into branches where actually used
-- `async-parallel` - Use Promise.all() for independent operations
-- `async-dependencies` - Use better-all for partial dependencies
-- `async-api-routes` - Start promises early, await late in API routes
-- `async-suspense-boundaries` - Use Suspense to stream content
-
-### 2. Bundle Size Optimization (CRITICAL)
-
-- `bundle-barrel-imports` - Import directly, avoid barrel files
-- `bundle-dynamic-imports` - Use next/dynamic for heavy components
-- `bundle-defer-third-party` - Load analytics/logging after hydration
-- `bundle-conditional` - Load modules only when feature is activated
-- `bundle-preload` - Preload on hover/focus for perceived speed
-
-### 3. Server-Side Performance (HIGH)
-
-- `server-cache-react` - Use React.cache() for per-request deduplication
-- `server-cache-lru` - Use LRU cache for cross-request caching
-- `server-serialization` - Minimize data passed to client components
-- `server-parallel-fetching` - Restructure components to parallelize fetches
-- `server-after-nonblocking` - Use after() for non-blocking operations
-
-### 4. Client-Side Data Fetching (MEDIUM-HIGH)
-
-- `client-swr-dedup` - Use SWR for automatic request deduplication
-- `client-event-listeners` - Deduplicate global event listeners
-
-### 5. Re-render Optimization (MEDIUM)
-
-- `rerender-defer-reads` - Don't subscribe to state only used in callbacks
-- `rerender-memo` - Extract expensive work into memoized components
-- `rerender-dependencies` - Use primitive dependencies in effects
-- `rerender-derived-state` - Subscribe to derived booleans, not raw values
-- `rerender-functional-setstate` - Use functional setState for stable callbacks
-- `rerender-lazy-state-init` - Pass function to useState for expensive values
-- `rerender-transitions` - Use startTransition for non-urgent updates
-
-### 6. Rendering Performance (MEDIUM)
-
-- `rendering-animate-svg-wrapper` - Animate div wrapper, not SVG element
-- `rendering-content-visibility` - Use content-visibility for long lists
-- `rendering-hoist-jsx` - Extract static JSX outside components
-- `rendering-svg-precision` - Reduce SVG coordinate precision
-- `rendering-hydration-no-flicker` - Use inline script for client-only data
-- `rendering-activity` - Use Activity component for show/hide
-- `rendering-conditional-render` - Use ternary, not && for conditionals
-
-### 7. JavaScript Performance (LOW-MEDIUM)
-
-- `js-batch-dom-css` - Group CSS changes via classes or cssText
-- `js-index-maps` - Build Map for repeated lookups
-- `js-cache-property-access` - Cache object properties in loops
-- `js-cache-function-results` - Cache function results in module-level Map
-- `js-cache-storage` - Cache localStorage/sessionStorage reads
-- `js-combine-iterations` - Combine multiple filter/map into one loop
-- `js-length-check-first` - Check array length before expensive comparison
-- `js-early-exit` - Return early from functions
-- `js-hoist-regexp` - Hoist RegExp creation outside loops
-- `js-min-max-loop` - Use loop for min/max instead of sort
-- `js-set-map-lookups` - Use Set/Map for O(1) lookups
-- `js-tosorted-immutable` - Use toSorted() for immutability
-
-### 8. Advanced Patterns (LOW)
-
-- `advanced-event-handler-refs` - Store event handlers in refs
-- `advanced-use-latest` - useLatest for stable callback refs
-
-## How to Use
-
-Read individual rule files for detailed explanations and code examples:
-
-```
-rules/async-parallel.md
-rules/bundle-barrel-imports.md
-rules/_sections.md
-```
-
-Each rule file contains:
-- Brief explanation of why it matters
-- Incorrect code example with explanation
-- Correct code example with explanation
-- Additional context and references
-
-## Full Compiled Document
-
-For the complete guide with all rules expanded: `AGENTS.md`

package/templates/.claude/skills/vs-design-diverge/SKILL.md

@@ -1,307 +0,0 @@
----
-name: vs-design-diverge
-description: Create high-entropy frontend interfaces using Verbalized Sampling (VS). Break mode collapse, avoid AI-slop aesthetics. Use for distinctive design work.
----
-
-<context>
-
-**Purpose:** Mitigate Mode Collapse (tendency to produce generic AI output) and create production-grade frontend interfaces
-
-**Principle:** Verbalized Sampling (VS) - Verbalize typical design (P ≈ 0.95), then deliberately select Low-T (low typicality) alternatives
-
-</context>
-
----
-
-<workflow>
-
-## Execution Flow
-
-```
-Phase 0: Context Discovery
-  ↓ (AskUserQuestion - probe 4 dimensions)
-Phase 1: Identify the Mode
-  ↓ (verbalize P ≈ 0.95 baseline, avoid it)
-Phase 2: Sample the Long-Tail
-  ↓ (3 directions + T-Score justification)
-Phase 3: Commit to Low-Typicality
-  ↓ (lowest T-Score + pass Guardrails)
-Phase 4: Implementation
-  ↓ (production-grade code)
-Phase 5: Surprise Validation
-  ↓ (AI-typical? → refactor)
-```
-
-### Phase 0: Context Discovery
-
-**Probe these dimensions using AskUserQuestion tool:**
-
-| Dimension | Question Examples |
-|-----------|-------------------|
-| **Emotional Tone** | "Trustworthy", "edgy", "playful", "luxurious" - which atmosphere? |
-| **Target Audience** | Who will see this? Technical sophistication? Expectations? |
-| **Reference Points / Anti-References** | Benchmark examples? Styles to explicitly avoid? |
-| **Business Context** | Problem this UI solves? Usage scenario? |
-
-**Additional signals:**
-- Existing code: Extract style patterns, color schemes, component conventions
-- User prompt: Parse keywords (landing page, dashboard, portfolio, SaaS, etc.)
-- Follow-up questions: Surface full vision even for simple prompts
-
-Gather sufficient context before proceeding to Phase 1.
-
-### Phase 1: Identify the Mode
-
-**Verbalize the highest-probability (P ≈ 0.95) design:**
-
-AI-slop markers:
-- Inter/Roboto/System fonts
-- Rounded blue/purple buttons
-- Standard F-pattern layouts
-- White backgrounds with gradient accents
-- Generic hero sections with stock imagery
-
-**Avoid this baseline.**
-
-### Phase 2: Sample the Long-Tail
-
-**Generate 3 directions with T-Score (Typicality Score, 0~1.0):**
-
-| Direction | T-Score | Characteristics |
-|-----------|---------|-----------------|
-| **A** | ≈ 0.7 | Modern/Clean, safe |
-| **B** | ≈ 0.4 | Distinctive/Characterful (specific niche style) |
-| **C** | < 0.2 | Experimental/Bold (high-entropy, unexpected) |
-
-**T-Score justification required:** Explain WHY each direction has that score. Reference specific design choices.
-
-### Phase 3: Commit to Low-Typicality
-
-**Select lowest T-Score that meets:**
-1. Functional requirements from Phase 0
-2. All Quality Guardrails
-
-Deliberate and intentional choice, not accidental.
-
-</workflow>
-
----
-
-<guardrails>
-
-## Quality Principles
-
-Experimental designs must satisfy these principles. If violated, increase T-Score until compliance.
-
-| Principle | Description |
-|-----------|-------------|
-| **Visual Hierarchy** | Clear priority ordering (1st → 2nd → 3rd) |
-| **Contrast & Legibility** | Text readable against background (WCAG AA minimum) |
-| **Internal Consistency** | Design follows its own logic (not random) |
-| **Functional Clarity** | Interactive elements recognizable, affordances clear |
-
-</guardrails>
-
----
-
-<anti_patterns>
-
-## Failure Patterns
-
-| Pattern | Symptoms | Validation |
-|---------|----------|------------|
-| **Accidental Design** | Differentiation without intent, randomness | "Why this color/font/layout?" → must have coherent answer |
-| **Frankenstein Style** | Incompatible aesthetics mixed, no unity | "Describe this design's personality in one sentence?" → must be possible |
-
-</anti_patterns>
-
----
-
-<aesthetics>
-
-## Frontend Aesthetics Guidelines (VS-Enhanced)
-
-**Inversion Principle:** If a choice feels "obvious," it has too much probability mass → consider lower-probability, higher-impact alternatives (when context-appropriate).
-
-### Typography
-
-| Category | Content |
-|----------|---------|
-| ❌ **AI-slop** | Inter, Roboto, Arial, System fonts, Space Grotesk (default usage) |
-| ✅ **Low-T** | High-character display faces + refined, unexpected body typefaces. Variable fonts, unusual weights. |
-| **Context-dependent** | Brutalist portfolio → industrial sans-serifs / Luxury brand → refined serifs |
-
-### Color & Theme
-
-| Principle | Description |
-|-----------|-------------|
-| ✅ **Uneven distribution** | Cohesive but "dissonant-yet-beautiful" palette |
-| ✅ **CSS Variables** | Systematic theming |
-| ✅ **Texture-first** | Sophisticated noise/lighting over flat fills (when context-appropriate) |
-
-### Spatial Composition
-
-| Condition | Approach |
-|-----------|----------|
-| **Standard grid (P=0.9)** | Consider asymmetry, overlapping elements, diagonal flows, editorial whitespace (P=0.1) |
-| **Data-heavy UIs** | Dashboards, tables → conventional grids may be needed (usability priority) |
-
-### Motion
-
-| Principle | Description |
-|-----------|-------------|
-| ✅ **Micro-delights** | Staggered reveals, scroll-bound transformations, custom easing |
-| ❌ **Purposeless motion** | Every animation must have purpose |
-
-</aesthetics>
-
----
-
-<frameworks>
-
-## AIDA Framework (Conditional)
-
-**Apply only for persuasion/conversion goals (landing pages, marketing sites, product showcases):**
-
-| Stage | Goal | Design Application |
-|-------|------|-------------------|
-| **A**ttention | Stop scroll, create immediate visual impact | Bold typography, unexpected imagery, striking color contrast |
-| **I**nterest | Build curiosity, encourage exploration | Progressive information reveal, visual storytelling, highlight unique value |
-| **D**esire | Create emotional connection, make them want it | Social proof, benefits visualization, aspirational imagery, micro-interactions |
-| **A**ction | Drive conversion with clear next steps | High-contrast CTAs, reduced friction, urgency cues (when appropriate) |
-
-### Application Conditions
-
-| Apply ✅ | Don't Apply ❌ |
-|---------|----------------|
-| Landing/marketing pages | Dashboards, data-heavy UIs (usability priority) |
-| Product launch pages | Documentation/content-focused sites (readability priority) |
-| Client-attracting portfolios | Internal tools (efficiency priority) |
-
-**VS + AIDA Integration:** Apply Low-T aesthetics to EACH AIDA stage. Generic hero → Attention failure / Predictable CTA → Action failure. AIDA = "what", VS = "how".
-
-</frameworks>
-
----
-
-<implementation>
-
-## Implementation Standards
-
-| Standard | Description |
-|----------|-------------|
-| **Production-Grade** | Functional, accessible (A11y), performant |
-| **Complexity-Typicality Balance** | Low-T design → implementation complexity increases proportionally (maintain quality) |
-| **No Complexity Refusal** | Pursue extraordinary work, don't simplify vision |
-
-</implementation>
-
----
-
-<validation>
-
-## Final Validation
-
-Pre-delivery checklist:
-
-1. **Intentionality**: Can you justify every major design decision?
-2. **Consistency**: Does the design follow its own internal logic?
-3. **Guardrails**: Are hierarchy, legibility, consistency, and clarity preserved?
-4. **Surprise**: Would this stand out in a lineup of AI-generated designs?
-
-**Goal:** Maximize "Surprise Score" while maintaining "Production Quality." Deliberate disruption.
-
-</validation>
-
----
-
-<examples>
-
-## Practical Examples
-
-### Phase 2: T-Score Justification
-
-```markdown
-**Direction A (T ≈ 0.7): Modern Minimal**
-- Inter font, white background, blue buttons
-- High typicality: 2020s SaaS standard pattern
-
-**Direction B (T ≈ 0.4): Brutalist Style**
-- Space Mono font, grid background, angular black buttons
-- Lower typicality: Specific niche, non-mainstream choice
-
-**Direction C (T < 0.2): Neo-Baroque**
-- Fraunces Display font, irregular layout, animated gradients
-- Very low probability: Rarely seen on web
-```
-
-### Typography Code
-
-```css
-/* ❌ AI-slop */
-font-family: 'Inter', system-ui, sans-serif;
-
-/* ✅ Low-T (Brutalist portfolio) */
-@import url('https://fonts.googleapis.com/css2?family=Space+Mono:wght@400;700&display=swap');
-font-family: 'Space Mono', monospace;
-font-variation-settings: 'wght' 650;
-
-/* ✅ Low-T (Luxury brand) */
-@import url('https://fonts.googleapis.com/css2?family=Cormorant+Garamond:wght@300;500&display=swap');
-font-family: 'Cormorant Garamond', serif;
-letter-spacing: 0.05em;
-```
-
-### Color System
-
-```css
-/* ❌ AI-slop (even distribution) */
-:root {
-  --primary: #3b82f6; /* blue */
-  --secondary: #a855f7; /* purple */
-  --accent: #10b981; /* green */
-}
-
-/* ✅ Low-T (uneven, cohesive) */
-:root {
-  --dominant: #0a0908; /* near-black (60%) */
-  --support: #8d99ae; /* neutral blue (30%) */
-  --punch: #ef233c; /* intense red (10%) */
-  --texture: url('data:image/svg+xml,...'); /* noise overlay */
-}
-```
-
-### AIDA + Low-T Integration
-
-```tsx
-// Hero Section (Attention stage + Low-T)
-<section className="hero">
-  <h1 style={{
-    fontFamily: 'Fraunces',
-    fontSize: 'clamp(3rem, 10vw, 8rem)',
-    fontVariationSettings: '"SOFT" 100, "WONK" 1',
-    background: 'linear-gradient(135deg, #0a0908, #ef233c)',
-    backgroundClip: 'text',
-    WebkitTextFillColor: 'transparent',
-  }}>
-    Disruptive Product Name
-  </h1>
-  {/* Unexpected imagery treatment */}
-</section>
-
-// CTA (Action stage + Low-T)
-<button style={{
-  background: '#ef233c',
-  color: '#0a0908',
-  border: '2px solid #0a0908',
-  padding: '1.5rem 3rem',
-  fontSize: '1.25rem',
-  fontWeight: 700,
-  clipPath: 'polygon(5% 0, 100% 0, 95% 100%, 0 100%)', // asymmetric
-  transition: 'clip-path 0.3s cubic-bezier(0.4, 0, 0.2, 1)',
-}}>
-  Get Started →
-</button>
-```
-
-</examples>