From auto-claude-skills
Produce 3 thin comparable variants of a proposed design with a comparison artifact and mandatory Human Validation Plan
npx claudepluginhub damianpapadopoulos/auto-claude-skillsThis skill uses the workspace's default tool permissions.
Build exactly 3 thin, comparable variants of a proposed design so the user can evaluate concrete alternatives before committing to a direction.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Build exactly 3 thin, comparable variants of a proposed design so the user can evaluate concrete alternatives before committing to a direction.
During DESIGN phase when competing approaches are identified. Fires on trigger match alongside brainstorming (which remains the process driver). The user or DESIGN phase guidance may suggest prototyping; this skill does not depend on brainstorming internally escalating to it.
Relationship to design-debate:
Determine what "a variant" means for this project:
| Project type | Variant contents |
|---|---|
| New skill | SKILL.md draft + routing entry + one behavioral test |
| New hook | Script draft + config entry + one syntax test |
| New feature | Implementation sketch + one test |
| Architecture decision | Thin proof-of-concept code + one integration test |
Default: 3 variants. User can override ("just compare these 2").
For each variant (A, B, C):
Save to docs/plans/YYYY-MM-DD-<topic>-prototype-lab.md:
# Prototype Comparison: <Topic>
**Date:** YYYY-MM-DD
**Variants:** 3
## Variant A: <Name>
**Approach:** <1-2 sentences>
**Trade-offs:** <pros and cons>
**Artifact:** <path or inline>
## Variant B: <Name>
**Approach:** <1-2 sentences>
**Trade-offs:** <pros and cons>
**Artifact:** <path or inline>
## Variant C: <Name>
**Approach:** <1-2 sentences>
**Trade-offs:** <pros and cons>
**Artifact:** <path or inline>
## Recommendation
**Chosen:** Variant <X>
**Reasoning:** <why this over the others>
## Human Validation Plan
<REQUIRED — how the user will test the chosen option with real usage>
<AI-simulated testing may inform the draft but never replaces this section>
<Describe: who tests, what they test, what success looks like>
## Success Signals
<What to measure after shipping to confirm the choice was right>
Show the comparison artifact. Ask the user to choose a variant. Only the chosen variant proceeds to writing-plans. The others are archived in the comparison artifact.