tuning-panel
Create visual parameter tuning panels for iterative adjustment of animations, layouts, colors, typography, physics, or any numeric/visual values. Use when the user asks to "create a tuning panel", "add parameter controls", "build a debug panel", "tweak parameters visually", "fine-tune values", "dial in the settings", or "adjust parameters interactively". Also triggers on mentions of "leva", "dat.GUI", or "tweakpane".
What this skill does
# Tuning Panel Skill Create bespoke parameter tuning panels that give users visual control over values they're iterating on. These panels surface all relevant parameters for the current task, enable real-time adjustment, and export tuned values in an LLM-friendly format. ## Core Philosophy **Err on the side of exhaustive.** When a user is tuning something, surface every parameter that could reasonably affect the outcome. Missing a parameter forces context-switching; having "too many" parameters costs only scroll distance. **Debug-mode only.** Tuning panels should never appear in production. Use environment checks, build flags, or URL parameters. **Export changed values only.** LLM exports should show only what was tuned, not all 100+ parameters. ## Platform Selection | Platform | Library | Reference | |----------|---------|-----------| | **React** | Leva (recommended) | [references/react-leva.md](references/react-leva.md) | | **SwiftUI** | Native controls | [references/swiftui.md](references/swiftui.md) | | **Vanilla JS** | Tweakpane or dat.GUI | [references/vanilla-js.md](references/vanilla-js.md) | ## Implementation Workflow ### Step 1: Identify All Tunable Parameters Analyze the code being tuned and extract every parameter that affects the output. See [references/parameter-categories.md](references/parameter-categories.md) for exhaustive lists by domain. **Common categories:** - **Animation**: duration, delay, easing, spring physics (stiffness, damping, mass) - **Layout**: padding, margin, gap, width, height, position - **Visual**: colors, opacity, shadows, borders, transforms - **Typography**: font size, line height, letter spacing, weight **Discovery strategies:** 1. Search for magic numbers (any hardcoded numeric value) 2. Look for style objects (CSS-in-JS, inline styles, theme values) 3. Find animation definitions (Framer Motion, CSS transitions, SwiftUI animations) 4. Identify color values (hex, RGB, HSL anywhere in the file) 5. Check component props with numeric or color defaults 6. Examine CSS custom properties (`--var-name` declarations) ### Step 2: Create Debug-Mode Panel Wrap the tuning panel so it only appears in development: - **React**: `process.env.NODE_ENV === 'development'` - **SwiftUI**: `#if DEBUG` - **Vanilla JS**: URL parameter `?debug` or environment check See platform-specific references for code patterns. ### Step 3: Implement Controls Follow these principles: 1. **Group related parameters** using folders/sections 2. **Use appropriate control types**: sliders for numbers, color pickers for colors, dropdowns for enums 3. **Set sensible min/max/step values** based on the parameter domain 4. **Include presets** for common configurations 5. **Add reset buttons** to return to defaults ### Step 4: Add LLM Export **Critical requirements:** 1. **Store defaults** at initialization for comparison 2. **Use tolerance for floats** (e.g., `Math.abs(a - b) > 0.001`) 3. **Filter to changed values only** - don't show unchanged parameters 4. **Format for readability** - group by category, use human-readable names **Export format:** ```markdown ## Tuned Parameters for [ComponentName] ### Changed Values - Duration: 300 → 450 - Spring Damping: 0.80 → 0.65 - Corner Radius: 12 → 16 ### Apply These Values Update the component at `src/components/Card.tsx:42` with the values above. ``` **Why this matters:** - A panel might expose 100+ parameters - Exporting all values wastes tokens and obscures what changed - The `default → current` format makes diffs scannable ## Additional Resources ### Reference Files - **[references/react-leva.md](references/react-leva.md)** - Complete React/Leva implementation guide - **[references/swiftui.md](references/swiftui.md)** - SwiftUI native controls and export patterns - **[references/vanilla-js.md](references/vanilla-js.md)** - Tweakpane and dat.GUI for plain JS - **[references/parameter-categories.md](references/parameter-categories.md)** - Exhaustive parameter lists by domain ### Example Files - **[examples/react-leva-animation.tsx](examples/react-leva-animation.tsx)** - Complete animation tuning panel - **[examples/export-format.md](examples/export-format.md)** - Full LLM export template
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.