lsd-pi 1.2.0 → 1.2.2

package/src/resources/skills/userinterface-wiki/rules/visual-border-alpha-colors.md

@@ -1,25 +0,0 @@
----
-title: Use Semi-Transparent Borders for Subtle Separation
-impact: MEDIUM
-tags: visual, border, alpha, separation
----
-
-## Use Semi-Transparent Borders for Subtle Separation
-
-Semi-transparent borders adapt to any background color and create subtle, non-jarring separation.
-
-**Incorrect (hardcoded border color):**
-
-```css
-.card {
-  border: 1px solid #e5e5e5;
-}
-```
-
-**Correct (alpha border):**
-
-```css
-.card {
-  border: 1px solid var(--gray-a4);
-}
-```

package/src/resources/skills/userinterface-wiki/rules/visual-button-shadow-anatomy.md

@@ -1,49 +0,0 @@
----
-title: Use Full Shadow Anatomy on Buttons
-impact: HIGH
-tags: visual, shadow, button, depth, gradient
----
-
-## Use Full Shadow Anatomy on Buttons
-
-A polished button uses six layered techniques, not just a single box-shadow.
-
-1. **Outer cut shadow** — 0.5px dark box-shadow to "cut" the button into the surface
-2. **Inner ambient highlight** — 1px inset box-shadow on all sides for environmental light reflections
-3. **Inner top highlight** — 1px inset top highlight for the primary light source from above
-4. **Layered depth shadows** — At least 3 external shadows for natural lighting
-5. **Text drop-shadow** — Drop-shadow on text/icons for better contrast against the button background
-6. **Subtle gradient background** — If you can tell there's a gradient, it's too much
-
-**Incorrect (flat button):**
-
-```css
-.button {
-  background: var(--gray-12);
-  color: var(--gray-1);
-  box-shadow: 0 2px 4px rgba(0, 0, 0, 0.1);
-}
-```
-
-**Correct (full shadow anatomy):**
-
-```css
-.button {
-  background: linear-gradient(
-    to bottom,
-    color-mix(in srgb, var(--gray-12) 100%, white 4%),
-    var(--gray-12)
-  );
-  color: var(--gray-1);
-  box-shadow:
-    0 0 0 0.5px rgba(0, 0, 0, 0.3),
-    inset 0 0 0 1px rgba(255, 255, 255, 0.04),
-    inset 0 1px 0 rgba(255, 255, 255, 0.07),
-    0 1px 2px rgba(0, 0, 0, 0.1),
-    0 2px 4px rgba(0, 0, 0, 0.06),
-    0 4px 8px rgba(0, 0, 0, 0.03);
-  text-shadow: 0 1px 1px rgba(0, 0, 0, 0.15);
-}
-```
-
-Reference: [@PixelJanitor](https://threadreaderapp.com/thread/1623358514440859649)

package/src/resources/skills/userinterface-wiki/rules/visual-concentric-radius.md

@@ -1,40 +0,0 @@
----
-title: Concentric Border Radius for Nested Elements
-impact: HIGH
-tags: visual, border-radius, concentric, nesting
----
-
-## Concentric Border Radius for Nested Elements
-
-When nesting rounded elements, inner radius must equal outer radius minus the gap. Same radius on both creates uneven curves.
-
-**Incorrect (same radius on both):**
-
-```css
-.outer {
-  border-radius: 16px;
-  padding: 8px;
-}
-
-.inner {
-  border-radius: 16px;
-}
-```
-
-**Correct (concentric radius):**
-
-```css
-.outer {
-  --padding: 8px;
-  --inner-radius: 8px;
-
-  border-radius: calc(var(--inner-radius) + var(--padding));
-  padding: var(--padding);
-}
-
-.inner {
-  border-radius: var(--inner-radius);
-}
-```
-
-Reference: [Concentric Border Radius](https://jakub.kr/work/concentric-border-radius)

package/src/resources/skills/userinterface-wiki/rules/visual-consistent-spacing-scale.md

@@ -1,35 +0,0 @@
----
-title: Use a Consistent Spacing Scale
-impact: HIGH
-tags: visual, spacing, scale, consistency
----
-
-## Use a Consistent Spacing Scale
-
-Don't use arbitrary pixel values for spacing. Define a scale and stick to it throughout the UI.
-
-**Incorrect (arbitrary values):**
-
-```css
-.header { padding: 17px; }
-.card { margin-bottom: 13px; }
-.section { gap: 22px; }
-```
-
-**Correct (consistent scale):**
-
-```css
-:root {
-  --space-1: 4px;
-  --space-2: 8px;
-  --space-3: 12px;
-  --space-4: 16px;
-  --space-5: 24px;
-  --space-6: 32px;
-  --space-7: 48px;
-}
-
-.header { padding: var(--space-4); }
-.card { margin-bottom: var(--space-3); }
-.section { gap: var(--space-5); }
-```

package/src/resources/skills/userinterface-wiki/rules/visual-layered-shadows.md

@@ -1,30 +0,0 @@
----
-title: Layer Multiple Shadows for Realistic Depth
-impact: HIGH
-tags: visual, shadow, layered, depth
----
-
-## Layer Multiple Shadows for Realistic Depth
-
-A single box-shadow looks flat. Layer multiple shadows with increasing blur and decreasing opacity to mimic real light.
-
-**Incorrect (single flat shadow):**
-
-```css
-.card {
-  box-shadow: 0 4px 16px rgba(0, 0, 0, 0.2);
-}
-```
-
-**Correct (layered shadows):**
-
-```css
-.card {
-  box-shadow:
-    0 1px 2px rgba(0, 0, 0, 0.06),
-    0 4px 8px rgba(0, 0, 0, 0.04),
-    0 12px 24px rgba(0, 0, 0, 0.03);
-}
-```
-
-Reference: [Designing Beautiful Shadows in CSS](https://www.joshwcomeau.com/css/designing-shadows/)

package/src/resources/skills/userinterface-wiki/rules/visual-no-pure-black-shadow.md

@@ -1,25 +0,0 @@
----
-title: Use Neutral Colors for Shadows, Not Pure Black
-impact: MEDIUM
-tags: visual, shadow, color, neutral
----
-
-## Use Neutral Colors for Shadows, Not Pure Black
-
-Pure black shadows look harsh and artificial. Use deep neutrals or semi-transparent dark colors.
-
-**Incorrect (pure black):**
-
-```css
-.card {
-  box-shadow: 0 4px 12px rgba(0, 0, 0, 0.25);
-}
-```
-
-**Correct (neutral shadow):**
-
-```css
-.card {
-  box-shadow: 0 4px 12px rgba(17, 24, 39, 0.08);
-}
-```

package/src/resources/skills/userinterface-wiki/rules/visual-shadow-direction.md

@@ -1,25 +0,0 @@
----
-title: Consistent Shadow Direction Across UI
-impact: HIGH
-tags: visual, shadow, direction, light-source
----
-
-## Consistent Shadow Direction Across UI
-
-All shadows must share the same offset direction to imply a single light source. Mixed directions feel broken.
-
-**Incorrect (conflicting light sources):**
-
-```css
-.card { box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1); }
-.modal { box-shadow: 4px 0 8px rgba(0, 0, 0, 0.1); }
-.tooltip { box-shadow: 0 -4px 8px rgba(0, 0, 0, 0.1); }
-```
-
-**Correct (consistent top-down light):**
-
-```css
-.card { box-shadow: 0 2px 8px rgba(0, 0, 0, 0.08); }
-.modal { box-shadow: 0 8px 24px rgba(0, 0, 0, 0.12); }
-.tooltip { box-shadow: 0 4px 12px rgba(0, 0, 0, 0.1); }
-```

package/src/resources/skills/userinterface-wiki/rules/visual-shadow-matches-elevation.md

@@ -1,23 +0,0 @@
----
-title: Shadow Size Indicates Elevation
-impact: MEDIUM
-tags: visual, shadow, elevation, hierarchy
----
-
-## Shadow Size Indicates Elevation
-
-Larger blur and offset means higher elevation. Use a consistent shadow scale across your UI.
-
-**Correct (elevation scale):**
-
-```css
-:root {
-  --shadow-1: 0 1px 2px rgba(0, 0, 0, 0.05);
-  --shadow-2: 0 2px 8px rgba(0, 0, 0, 0.08);
-  --shadow-3: 0 8px 24px rgba(0, 0, 0, 0.12);
-}
-
-.card { box-shadow: var(--shadow-1); }
-.dropdown { box-shadow: var(--shadow-2); }
-.modal { box-shadow: var(--shadow-3); }
-```

package/src/resources/skills/userinterface-wiki/rules/weight-duration-matches-action.md

@@ -1,29 +0,0 @@
----
-title: Sound Duration Matches Action Duration
-impact: MEDIUM
-tags: weight, duration, action
----
-
-## Sound Duration Matches Action Duration
-
-Sound duration should match action duration.
-
-**Incorrect (long sound for instant action):**
-
-```tsx
-function handleClick() {
-  playSound("long-whoosh"); // 2000ms
-}
-```
-
-**Correct (matched duration):**
-
-```tsx
-function handleClick() {
-  playSound("click"); // 50ms
-}
-
-function handleUpload() {
-  playSound("upload-progress"); // Matches upload duration
-}
-```

package/src/resources/skills/userinterface-wiki/rules/weight-match-action.md

@@ -1,32 +0,0 @@
----
-title: Match Sound Weight to Action
-impact: MEDIUM
-tags: weight, action, importance
----
-
-## Match Sound Weight to Action
-
-Sound weight should match action importance.
-
-**Incorrect (fanfare for toggle):**
-
-```tsx
-function handleToggle() {
-  playSound("triumphant-fanfare");
-  setEnabled(!enabled);
-}
-```
-
-**Correct (weight matches action):**
-
-```tsx
-function handleToggle() {
-  playSound("soft-click");
-  setEnabled(!enabled);
-}
-
-function handlePurchase() {
-  playSound("success-chime");
-  completePurchase();
-}
-```

package/src/resources/skills/web-design-guidelines/SKILL.md

@@ -1,39 +0,0 @@
----
-name: web-design-guidelines
-description: Review UI code for Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
-metadata:
-  author: vercel
-  version: "1.0.0"
-  argument-hint: <file-or-pattern>
----
-
-# Interface Guidelines
-
-Review files for compliance with Interface Guidelines.
-
-## How It Works
-
-1. Fetch the latest guidelines from the source URL below
-2. Read the specified files (or prompt user for files/pattern)
-3. Check against all rules in the fetched guidelines
-4. Output findings in the terse `file:line` format
-
-## Guidelines Source
-
-Fetch fresh guidelines before each review:
-
-```
-https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/main/command.md
-```
-
-Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.
-
-## Usage
-
-When a user provides a file or pattern argument:
-1. Fetch guidelines from the source URL above
-2. Read the specified files
-3. Apply all rules from the fetched guidelines
-4. Output findings using the format specified in the guidelines
-
-If no files specified, ask the user which files to review.

package/src/resources/skills/web-quality-audit/SKILL.md

@@ -1,168 +0,0 @@
----
-name: web-quality-audit
-description: Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
-license: MIT
-metadata:
-  author: web-quality-skills
-  version: "1.0"
----
-
-# Web quality audit
-
-Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.
-
-## How it works
-
-1. Analyze the provided code/project for quality issues
-2. Categorize findings by severity (Critical, High, Medium, Low)
-3. Provide specific, actionable recommendations
-4. Include code examples for fixes
-
-## Audit categories
-
-### Performance (40% of typical issues)
-
-**Core Web Vitals** — Must pass for good page experience:
-* **LCP (Largest Contentful Paint) < 2.5s.** The largest visible element must render quickly. Optimize images, fonts, and server response time.
-* **INP (Interaction to Next Paint) < 200ms.** User interactions must feel instant. Reduce JavaScript execution time and break up long tasks.
-* **CLS (Cumulative Layout Shift) < 0.1.** Content must not jump around. Set explicit dimensions on images, embeds, and ads.
-
-**Resource Optimization:**
-* **Compress images.** Use WebP/AVIF with fallbacks. Serve correctly sized images via `srcset`.
-* **Minimize JavaScript.** Remove unused code. Use code splitting. Defer non-critical scripts.
-* **Optimize CSS.** Extract critical CSS. Remove unused styles. Avoid `@import`.
-* **Efficient fonts.** Use `font-display: swap`. Preload critical fonts. Subset to needed characters.
-
-**Loading Strategy:**
-* **Preconnect to origins.** Add `<link rel="preconnect">` for third-party domains.
-* **Preload critical assets.** LCP images, fonts, and above-fold CSS.
-* **Lazy load below-fold content.** Images, iframes, and heavy components.
-* **Cache effectively.** Long cache TTLs for static assets. Immutable caching for hashed files.
-
-### Accessibility (30% of typical issues)
-
-**Perceivable:**
-* **Text alternatives.** Every `<img>` has meaningful `alt` text. Decorative images use `alt=""`.
-* **Color contrast.** Minimum 4.5:1 for normal text, 3:1 for large text (WCAG AA).
-* **Don't rely on color alone.** Use icons, patterns, or text alongside color indicators.
-* **Captions and transcripts.** Video has captions. Audio has transcripts.
-
-**Operable:**
-* **Keyboard accessible.** All functionality available via keyboard. No keyboard traps.
-* **Focus visible.** Clear focus indicators on all interactive elements.
-* **Skip links.** Provide "Skip to main content" for keyboard users.
-* **Sufficient time.** Users can extend time limits. No auto-advancing content without controls.
-
-**Understandable:**
-* **Page language.** Set `lang` attribute on `<html>`.
-* **Consistent navigation.** Same navigation structure across pages.
-* **Error identification.** Form errors clearly described and associated with fields.
-* **Labels and instructions.** All form inputs have associated labels.
-
-**Robust:**
-* **Valid HTML.** No duplicate IDs. Properly nested elements.
-* **ARIA used correctly.** Prefer native elements. ARIA roles match behavior.
-* **Name, role, value.** Interactive elements have accessible names and correct roles.
-
-### SEO (15% of typical issues)
-
-**Crawlability:**
-* **Valid robots.txt.** Doesn't block important resources.
-* **XML sitemap.** Lists all important pages. Submitted to Search Console.
-* **Canonical URLs.** Prevent duplicate content issues.
-* **No noindex on important pages.** Check meta robots and headers.
-
-**On-Page SEO:**
-* **Unique title tags.** 50-60 characters. Primary keyword included.
-* **Meta descriptions.** 150-160 characters. Compelling and unique.
-* **Heading hierarchy.** Single `<h1>`. Logical heading structure.
-* **Descriptive link text.** Not "click here" or "read more".
-
-**Technical SEO:**
-* **Mobile-friendly.** Responsive design. Tap targets ≥ 48px.
-* **HTTPS.** Secure connection required.
-* **Fast loading.** Performance directly impacts ranking.
-* **Structured data.** JSON-LD for rich snippets (Article, Product, FAQ, etc.).
-
-### Best practices (15% of typical issues)
-
-**Security:**
-* **HTTPS everywhere.** No mixed content. HSTS enabled.
-* **No vulnerable libraries.** Keep dependencies updated.
-* **CSP headers.** Content Security Policy to prevent XSS.
-* **No exposed source maps.** In production builds.
-
-**Modern Standards:**
-* **No deprecated APIs.** Replace `document.write`, synchronous XHR, etc.
-* **Valid doctype.** Use `<!DOCTYPE html>`.
-* **Charset declared.** `<meta charset="UTF-8">` as first element in `<head>`.
-* **No browser errors.** Clean console. No CORS issues.
-
-**UX Patterns:**
-* **No intrusive interstitials.** Especially on mobile.
-* **Clear permission requests.** Only ask when needed, with context.
-* **No misleading buttons.** Buttons do what they say.
-
-## Severity levels
-
-| Level | Description | Action |
-|-------|-------------|--------|
-| **Critical** | Security vulnerabilities, complete failures | Fix immediately |
-| **High** | Core Web Vitals failures, major a11y barriers | Fix before launch |
-| **Medium** | Performance opportunities, SEO improvements | Fix within sprint |
-| **Low** | Minor optimizations, code quality | Fix when convenient |
-
-## Audit output format
-
-When performing an audit, structure findings as:
-
-```markdown
-## Audit results
-
-### Critical issues (X found)
-- **[Category]** Issue description. File: `path/to/file.js:123`
-  - **Impact:** Why this matters
-  - **Fix:** Specific code change or recommendation
-
-### High priority (X found)
-...
-
-### Summary
-- Performance: X issues (Y critical)
-- Accessibility: X issues (Y critical)
-- SEO: X issues
-- Best Practices: X issues
-
-### Recommended priority
-1. First fix this because...
-2. Then address...
-3. Finally optimize...
-```
-
-## Quick checklist
-
-### Before every deploy
-- [ ] Core Web Vitals passing
-- [ ] No accessibility errors (axe/Lighthouse)
-- [ ] No console errors
-- [ ] HTTPS working
-- [ ] Meta tags present
-
-### Weekly review
-- [ ] Check Search Console for issues
-- [ ] Review Core Web Vitals trends
-- [ ] Update dependencies
-- [ ] Test with screen reader
-
-### Monthly deep dive
-- [ ] Full Lighthouse audit
-- [ ] Performance profiling
-- [ ] Accessibility audit with real users
-- [ ] SEO keyword review
-
-## References
-
-For detailed guidelines on specific areas:
-- [Core Web Vitals](../core-web-vitals/SKILL.md)
-- [Accessibility](../accessibility/SKILL.md)
-- [Best Practices](../best-practices/SKILL.md)

package/src/resources/skills/web-quality-audit/scripts/analyze.sh

@@ -1,91 +0,0 @@
-#!/bin/bash
-set -e
-
-# Web Quality Audit Script
-# Analyzes HTML files for common quality issues
-
-usage() {
-  echo "Usage: $0 <file_or_directory>" >&2
-  echo "Analyzes HTML files for web quality issues." >&2
-  exit 1
-}
-
-if [ -z "$1" ]; then
-  usage
-fi
-
-TARGET="$1"
-ISSUES=()
-WARNINGS=()
-
-analyze_html() {
-  local file="$1"
-  echo "Analyzing: $file" >&2
-
-  # Check for doctype
-  if ! grep -qi "<!doctype html>" "$file"; then
-    ISSUES+=("$file: Missing HTML5 doctype")
-  fi
-
-  # Check for charset
-  if ! grep -qi 'charset.*utf-8' "$file"; then
-    WARNINGS+=("$file: Missing or non-UTF-8 charset declaration")
-  fi
-
-  # Check for viewport
-  if ! grep -qi 'name="viewport"' "$file"; then
-    ISSUES+=("$file: Missing viewport meta tag")
-  fi
-
-  # Check for lang attribute
-  if ! grep -qi '<html.*lang=' "$file"; then
-    ISSUES+=("$file: Missing lang attribute on <html>")
-  fi
-
-  # Check for images without alt
-  if grep -qE '<img[^>]*>' "$file" && grep -qE '<img(?![^>]*alt=)[^>]*>' "$file" 2>/dev/null; then
-    WARNINGS+=("$file: Possible images without alt text")
-  fi
-
-  # Check for title tag
-  if ! grep -qi '<title>' "$file"; then
-    ISSUES+=("$file: Missing <title> tag")
-  fi
-
-  # Check for HTTPS in links
-  if grep -qE 'http://' "$file"; then
-    WARNINGS+=("$file: Contains non-HTTPS URLs")
-  fi
-}
-
-# Process files
-if [ -d "$TARGET" ]; then
-  find "$TARGET" -name "*.html" -o -name "*.htm" | while read -r file; do
-    analyze_html "$file"
-  done
-elif [ -f "$TARGET" ]; then
-  analyze_html "$TARGET"
-else
-  echo "Error: $TARGET is not a valid file or directory" >&2
-  exit 1
-fi
-
-# Output results as JSON
-echo '{'
-echo '  "issues": ['
-for i in "${!ISSUES[@]}"; do
-  if [ $i -gt 0 ]; then echo ','; fi
-  echo -n "    \"${ISSUES[$i]}\""
-done
-echo ''
-echo '  ],'
-echo '  "warnings": ['
-for i in "${!WARNINGS[@]}"; do
-  if [ $i -gt 0 ]; then echo ','; fi
-  echo -n "    \"${WARNINGS[$i]}\""
-done
-echo ''
-echo '  ],'
-echo "  \"issueCount\": ${#ISSUES[@]},"
-echo "  \"warningCount\": ${#WARNINGS[@]}"
-echo '}'