wizz-method 1.4.0 → 1.5.0

package/src/skills-lib/premium-landing-ui-researcher/references/stack-and-visual-direction.md

@@ -0,0 +1,118 @@
+## Default Stack
+
+Se o usuário não especificar stack, assumir:
+
+- Next.js;
+- React;
+- TypeScript;
+- Tailwind CSS;
+- shadcn/ui;
+- Framer Motion ou Motion;
+- React Bits;
+- React Three Fiber para projetos 3D;
+- Three.js para WebGL avançado;
+- lucide-react para ícones;
+- Recharts para dashboards SaaS.
+
+Se o projeto for simples, reduzir stack e evitar complexidade desnecessária.
+
+## Default Visual Direction
+
+Se o usuário não informar direção de marca, sugerir 2 ou 3 caminhos e pedir confirmação.
+
+### 1. Premium Tech Minimalist
+
+Usar para: SaaS, AI tools, produtos digitais, consultorias modernas, serviços B2B.
+
+Características: limpo, moderno, estratégico, tipografia forte, motion sutil, CTAs claros, alta conversão, visual profissional.
+
+### 2. Cinematic Futuristic
+
+Usar para: tecnologia, IA, inovação, Web3, produtos high-ticket, marcas digitais avançadas.
+
+Características: fundo escuro, glow controlado, partículas, WebGL, 3D, scroll storytelling, gradientes dinâmicos, sensação premium/futurista.
+
+### 3. Sophisticated Editorial
+
+Usar para: consultorias, agências, criadores premium, luxo, arquitetura, branding, serviços autorais.
+
+Características: tipografia refinada, muito espaço negativo, layout assimétrico, movimento discreto, sensação editorial, visual sofisticado.
+
+Não forçar uma direção sem confirmar se a marca for ambígua.
+
+### Paletas sugeridas
+
+Quando o usuário não fornecer paleta, escolher baseado no negócio:
+
+- Tech / IA / SaaS: preto, azul profundo, ciano, branco, cinza frio.
+- Luxo / consultoria premium: off-white, preto, grafite, dourado suave, bege.
+- Saúde / bem-estar: verde profundo, areia, branco, azul suave.
+- Educação / infoproduto premium: marinho, branco, amarelo elegante, cinza.
+- Produto low ticket com percepção premium: fundo escuro ou claro editorial, cor de destaque forte e contida.
+
+### Tipografia
+
+Preferir:
+
+- títulos: Space Grotesk, Sora, Manrope, Plus Jakarta Sans, Neue Montreal, Inter Tight;
+- corpo: Inter, SF Pro, Geist, Manrope;
+- detalhes técnicos: JetBrains Mono, Geist Mono, IBM Plex Mono.
+
+## Animation Selection Rules
+
+Escolher animações com base em: tom da marca, ticket da oferta, maturidade do público, objetivo da página, nível de consciência do público, performance mobile, clareza da mensagem, valor percebido, confiança, conversão.
+
+Não usar animação apenas porque é bonita.
+
+A animação deve: guiar atenção, reforçar hierarquia, aumentar desejo, comunicar qualidade, melhorar compreensão, tornar a experiência memorável.
+
+Evitar:
+
+- excesso de movimento;
+- animações lentas demais;
+- animações sem propósito;
+- scroll hijacking agressivo;
+- efeitos que atrapalham leitura;
+- WebGL pesado sem fallback;
+- neon exagerado em marca que pede sofisticação.
+
+Antes de qualquer animação, respeitar:
+
+- `prefers-reduced-motion`: desativar ou simplificar todos os efeitos quando a preferência do sistema indicar isso.
+- **Fallback mobile**: reduzir partículas, Three.js e efeitos pesados em dispositivos de baixo desempenho.
+- Lazy load de componentes 3D.
+- Usar fallback estático quando necessário.
+- Priorizar LCP, CLS e legibilidade.
+
+### Animation Types to Research
+
+Quando o projeto pedir motion ou visual premium, pesquisar e recomendar:
+
+scroll effects, parallax, 3D hero animation, WebGL background, particle effects, shader effects, hover 3D, animated cards, text reveal, typewriter, magnetic buttons, gradient animations, floating objects, cinematic transitions, masked typography, image reveal, product mockup animation, CTA animation, dashboard microinteractions, loading states, onboarding animations, pricing section motion, testimonial carousel motion, background noise/texture, glassmorphism interactions.
+
+### 3D / WebGL Sources
+
+Usar Spline, Unicorn Studio, Three.js e React Three Fiber quando o projeto exigir experiência visual avançada.
+
+Usar para: hero 3D, WebGL backgrounds, motion assets, interactive objects, product visualization, particle systems, cinematic scenes, mouse-reactive visuals, shader effects, scroll-driven 3D.
+
+Se for 3D High-End ou modo Signature 3D, sempre sugerir: efeito principal desktop, fallback mobile, estratégia de performance, redução de partículas, lazy loading, `prefers-reduced-motion`, canvas otimizado, alternativa estática para mobile fraco.
+
+Não usar 3D pesado em projetos Basic.
+
+### Checklist de seleção de componentes
+
+Antes de escolher um componente ou animação, responder internamente:
+
+- Ele melhora clareza, desejo, credibilidade ou conversão?
+- Ele combina com o público?
+- Ele combina com a oferta?
+- Ele é viável no stack atual?
+- Ele prejudica performance mobile?
+- Ele depende de biblioteca paga?
+- Ele é acessível?
+- Ele pode ser mantido pelo projeto?
+- Existe alternativa mais simples?
+
+Se a resposta for fraca, não usar.
+

package/src/skills-lib/signup-flow-cro/SKILL.md

@@ -16,330 +16,24 @@ If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-
 
 Before providing recommendations, understand:
 
-1. **Flow Type**
-   - Free trial signup
-   - Freemium account creation
-   - Paid account creation
-   - Waitlist/early access signup
-   - B2B vs B2C
-
-2. **Current State**
-   - How many steps/screens?
-   - What fields are required?
-   - What's the current completion rate?
-   - Where do users drop off?
-
-3. **Business Constraints**
-   - What data is genuinely needed at signup?
-   - Are there compliance requirements?
-   - What happens immediately after signup?
-
----
+1. **Flow Type** — Free trial signup, freemium account creation, paid account creation, waitlist/early access signup, B2B vs B2C
+2. **Current State** — How many steps/screens? What fields are required? What's the current completion rate? Where do users drop off?
+3. **Business Constraints** — What data is genuinely needed at signup? Are there compliance requirements? What happens immediately after signup?
 
 ## Core Principles
 
-### 1. Minimize Required Fields
-Every field reduces conversion. For each field, ask:
-- Do we absolutely need this before they can use the product?
-- Can we collect this later through progressive profiling?
-- Can we infer this from other data?
-
-**Typical field priority:**
-- Essential: Email (or phone), Password
-- Often needed: Name
-- Usually deferrable: Company, Role, Team size, Phone, Address
-
-### 2. Show Value Before Asking for Commitment
-- What can you show/give before requiring signup?
-- Can they experience the product before creating an account?
-- Reverse the order: value first, signup second
-
-### 3. Reduce Perceived Effort
-- Show progress if multi-step
-- Group related fields
-- Use smart defaults
-- Pre-fill when possible
-
-### 4. Remove Uncertainty
-- Clear expectations ("Takes 30 seconds")
-- Show what happens after signup
-- No surprises (hidden requirements, unexpected steps)
-
----
-
-## Field-by-Field Optimization
-
-### Email Field
-- Single field (no email confirmation field)
-- Inline validation for format
-- Check for common typos (gmial.com → gmail.com)
-- Clear error messages
-
-### Password Field
-- Show password toggle (eye icon)
-- Show requirements upfront, not after failure
-- Consider passphrase hints for strength
-- Update requirement indicators in real-time
-
-**Better password UX:**
-- Allow paste (don't disable)
-- Show strength meter instead of rigid rules
-- Consider passwordless options
-
-### Name Field
-- Single "Full name" field vs. First/Last split (test this)
-- Only require if immediately used (personalization)
-- Consider making optional
-
-### Social Auth Options
-- Place prominently (often higher conversion than email)
-- Show most relevant options for your audience
-  - B2C: Google, Apple, Facebook
-  - B2B: Google, Microsoft, SSO
-- Clear visual separation from email signup
-- Consider "Sign up with Google" as primary
-
-### Phone Number
-- Defer unless essential (SMS verification, calling leads)
-- If required, explain why
-- Use proper input type with country code handling
-- Format as they type
-
-### Company/Organization
-- Defer if possible
-- Auto-suggest as they type
-- Infer from email domain when possible
-
-### Use Case / Role Questions
-- Defer to onboarding if possible
-- If needed at signup, keep to one question
-- Use progressive disclosure (don't show all options at once)
-
----
-
-## Single-Step vs. Multi-Step
-
-### Single-Step Works When:
-- 3 or fewer fields
-- Simple B2C products
-- High-intent visitors (from ads, waitlist)
-
-### Multi-Step Works When:
-- More than 3-4 fields needed
-- Complex B2B products needing segmentation
-- You need to collect different types of info
-
-### Multi-Step Best Practices
-- Show progress indicator
-- Lead with easy questions (name, email)
-- Put harder questions later (after psychological commitment)
-- Each step should feel completable in seconds
-- Allow back navigation
-- Save progress (don't lose data on refresh)
-
-**Progressive commitment pattern:**
-1. Email only (lowest barrier)
-2. Password + name
-3. Customization questions (optional)
-
----
-
-## Trust and Friction Reduction
-
-### At the Form Level
-- "No credit card required" (if true)
-- "Free forever" or "14-day free trial"
-- Privacy note: "We'll never share your email"
-- Security badges if relevant
-- Testimonial near signup form
-
-### Error Handling
-- Inline validation (not just on submit)
-- Specific error messages ("Email already registered" + recovery path)
-- Don't clear the form on error
-- Focus on the problem field
-
-### Microcopy
-- Placeholder text: Use for examples, not labels
-- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
-- Help text: Only when needed, placed close to field
-
----
-
-## Mobile Signup Optimization
-
-- Larger touch targets (44px+ height)
-- Appropriate keyboard types (email, tel, etc.)
-- Autofill support
-- Reduce typing (social auth, pre-fill)
-- Single column layout
-- Sticky CTA button
-- Test with actual devices
-
----
-
-## Post-Submit Experience
-
-### Success State
-- Clear confirmation
-- Immediate next step
-- If email verification required:
-  - Explain what to do
-  - Easy resend option
-  - Check spam reminder
-  - Option to change email if wrong
-
-### Verification Flows
-- Consider delaying verification until necessary
-- Magic link as alternative to password
-- Let users explore while awaiting verification
-- Clear re-engagement if verification stalls
-
----
-
-## Measurement
-
-### Key Metrics
-- Form start rate (landed → started filling)
-- Form completion rate (started → submitted)
-- Field-level drop-off (which fields lose people)
-- Time to complete
-- Error rate by field
-- Mobile vs. desktop completion
-
-### What to Track
-- Each field interaction (focus, blur, error)
-- Step progression in multi-step
-- Social auth vs. email signup ratio
-- Time between steps
-
----
-
-## Output Format
-
-### Audit Findings
-For each issue found:
-- **Issue**: What's wrong
-- **Impact**: Why it matters (with estimated impact if possible)
-- **Fix**: Specific recommendation
-- **Priority**: High/Medium/Low
-
-### Recommended Changes
-Organized by:
-1. Quick wins (same-day fixes)
-2. High-impact changes (week-level effort)
-3. Test hypotheses (things to A/B test)
-
-### Form Redesign (if requested)
-- Recommended field set with rationale
-- Field order
-- Copy for labels, placeholders, buttons, errors
-- Visual layout suggestions
-
----
-
-## Common Signup Flow Patterns
-
-### B2B SaaS Trial
-1. Email + Password (or Google auth)
-2. Name + Company (optional: role)
-3. → Onboarding flow
-
-### B2C App
-1. Google/Apple auth OR Email
-2. → Product experience
-3. Profile completion later
-
-### Waitlist/Early Access
-1. Email only
-2. Optional: Role/use case question
-3. → Waitlist confirmation
-
-### E-commerce Account
-1. Guest checkout as default
-2. Account creation optional post-purchase
-3. OR Social auth with single click
-
----
-
-## Experiment Ideas
-
-### Form Design Experiments
+1. **Minimize Required Fields** — every field reduces conversion. Essential: email (or phone), password. Often needed: name. Usually deferrable: company, role, team size, phone, address.
+2. **Show Value Before Asking for Commitment** — show/give value before requiring signup where possible; reverse the order (value first, signup second).
+3. **Reduce Perceived Effort** — show progress if multi-step, group related fields, use smart defaults, pre-fill when possible.
+4. **Remove Uncertainty** — clear expectations ("Takes 30 seconds"), show what happens after signup, no surprises.
 
-**Layout & Structure**
-- Single-step vs. multi-step signup flow
-- Multi-step with progress bar vs. without
-- 1-column vs. 2-column field layout
-- Form embedded on page vs. separate signup page
-- Horizontal vs. vertical field alignment
+## References (load on demand)
 
-**Field Optimization**
-- Reduce to minimum fields (email + password only)
-- Add or remove phone number field
-- Single "Name" field vs. "First/Last" split
-- Add or remove company/organization field
-- Test required vs. optional field balance
-
-**Authentication Options**
-- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
-- SSO prominent vs. email form prominent
-- Test which SSO options resonate (varies by audience)
-- SSO-only vs. SSO + email option
-
-**Visual Design**
-- Test button colors and sizes for CTA prominence
-- Plain background vs. product-related visuals
-- Test form container styling (card vs. minimal)
-- Mobile-optimized layout testing
-
----
-
-### Copy & Messaging Experiments
-
-**Headlines & CTAs**
-- Test headline variations above signup form
-- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
-- Add clarity around trial length in CTA
-- Test value proposition emphasis in form header
-
-**Microcopy**
-- Field labels: minimal vs. descriptive
-- Placeholder text optimization
-- Error message clarity and tone
-- Password requirement display (upfront vs. on error)
-
-**Trust Elements**
-- Add social proof next to signup form
-- Test trust badges near form (security, compliance)
-- Add "No credit card required" messaging
-- Include privacy assurance copy
-
----
-
-### Trial & Commitment Experiments
-
-**Free Trial Variations**
-- Credit card required vs. not required for trial
-- Test trial length impact (7 vs. 14 vs. 30 days)
-- Freemium vs. free trial model
-- Trial with limited features vs. full access
-
-**Friction Points**
-- Email verification required vs. delayed vs. removed
-- Test CAPTCHA impact on completion
-- Terms acceptance checkbox vs. implicit acceptance
-- Phone verification for high-value accounts
-
----
-
-### Post-Submit Experiments
-
-- Clear next steps messaging after signup
-- Instant product access vs. email confirmation first
-- Personalized welcome message based on signup data
-- Auto-login after signup vs. require login
-
----
+- `references/field-optimization.md` — field-by-field guidance (email, password, name, social auth, phone, company, use case/role). Load when deciding which fields to keep, defer, or cut.
+- `references/flow-structure.md` — single-step vs. multi-step decision criteria, the progressive commitment pattern, and mobile signup optimization. Load when deciding how many steps the flow needs.
+- `references/trust-and-post-submit.md` — trust copy near the form, error handling, microcopy, and the post-submit experience (success state, verification flows). Load when writing form-adjacent copy or designing what happens right after submit.
+- `references/measurement-output-patterns.md` — key metrics to track, the output format for an audit/redesign deliverable, and proven signup patterns by product type (B2B SaaS, B2C, waitlist, e-commerce). Load when instrumenting the flow, formatting a deliverable, or looking for a reference pattern.
+- `references/experiments.md` — a full experiment backlog (form design, copy/messaging, trial/commitment, post-submit) for A/B testing. Load when the deliverable needs a test plan.
 
 ## Task-Specific Questions
 
@@ -349,8 +43,6 @@ Organized by:
 4. Are there compliance or verification requirements?
 5. What happens immediately after signup?
 
----
-
 ## Related Skills
 
 - **onboarding-cro**: For optimizing what happens after signup

package/src/skills-lib/signup-flow-cro/references/experiments.md

@@ -0,0 +1,72 @@
+# Experiment Ideas
+
+Load this file when the deliverable includes a test plan / A/B test backlog for a signup flow.
+
+## Form Design Experiments
+
+**Layout & Structure**
+- Single-step vs. multi-step signup flow
+- Multi-step with progress bar vs. without
+- 1-column vs. 2-column field layout
+- Form embedded on page vs. separate signup page
+- Horizontal vs. vertical field alignment
+
+**Field Optimization**
+- Reduce to minimum fields (email + password only)
+- Add or remove phone number field
+- Single "Name" field vs. "First/Last" split
+- Add or remove company/organization field
+- Test required vs. optional field balance
+
+**Authentication Options**
+- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
+- SSO prominent vs. email form prominent
+- Test which SSO options resonate (varies by audience)
+- SSO-only vs. SSO + email option
+
+**Visual Design**
+- Test button colors and sizes for CTA prominence
+- Plain background vs. product-related visuals
+- Test form container styling (card vs. minimal)
+- Mobile-optimized layout testing
+
+## Copy & Messaging Experiments
+
+**Headlines & CTAs**
+- Test headline variations above signup form
+- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
+- Add clarity around trial length in CTA
+- Test value proposition emphasis in form header
+
+**Microcopy**
+- Field labels: minimal vs. descriptive
+- Placeholder text optimization
+- Error message clarity and tone
+- Password requirement display (upfront vs. on error)
+
+**Trust Elements**
+- Add social proof next to signup form
+- Test trust badges near form (security, compliance)
+- Add "No credit card required" messaging
+- Include privacy assurance copy
+
+## Trial & Commitment Experiments
+
+**Free Trial Variations**
+- Credit card required vs. not required for trial
+- Test trial length impact (7 vs. 14 vs. 30 days)
+- Freemium vs. free trial model
+- Trial with limited features vs. full access
+
+**Friction Points**
+- Email verification required vs. delayed vs. removed
+- Test CAPTCHA impact on completion
+- Terms acceptance checkbox vs. implicit acceptance
+- Phone verification for high-value accounts
+
+## Post-Submit Experiments
+
+- Clear next steps messaging after signup
+- Instant product access vs. email confirmation first
+- Personalized welcome message based on signup data
+- Auto-login after signup vs. require login

package/src/skills-lib/signup-flow-cro/references/field-optimization.md

@@ -0,0 +1,49 @@
+# Field-by-Field Optimization
+
+Load this file when deciding which signup fields to keep, defer, or cut, and how to design each one.
+
+### Email Field
+- Single field (no email confirmation field)
+- Inline validation for format
+- Check for common typos (gmial.com → gmail.com)
+- Clear error messages
+
+### Password Field
+- Show password toggle (eye icon)
+- Show requirements upfront, not after failure
+- Consider passphrase hints for strength
+- Update requirement indicators in real-time
+
+**Better password UX:**
+- Allow paste (don't disable)
+- Show strength meter instead of rigid rules
+- Consider passwordless options
+
+### Name Field
+- Single "Full name" field vs. First/Last split (test this)
+- Only require if immediately used (personalization)
+- Consider making optional
+
+### Social Auth Options
+- Place prominently (often higher conversion than email)
+- Show most relevant options for your audience
+  - B2C: Google, Apple, Facebook
+  - B2B: Google, Microsoft, SSO
+- Clear visual separation from email signup
+- Consider "Sign up with Google" as primary
+
+### Phone Number
+- Defer unless essential (SMS verification, calling leads)
+- If required, explain why
+- Use proper input type with country code handling
+- Format as they type
+
+### Company/Organization
+- Defer if possible
+- Auto-suggest as they type
+- Infer from email domain when possible
+
+### Use Case / Role Questions
+- Defer to onboarding if possible
+- If needed at signup, keep to one question
+- Use progressive disclosure (don't show all options at once)

package/src/skills-lib/signup-flow-cro/references/flow-structure.md

@@ -0,0 +1,38 @@
+# Single-Step vs. Multi-Step and Mobile Optimization
+
+Load this file when deciding how many steps the signup flow needs and how to adapt it for mobile.
+
+## Single-Step vs. Multi-Step
+
+### Single-Step Works When:
+- 3 or fewer fields
+- Simple B2C products
+- High-intent visitors (from ads, waitlist)
+
+### Multi-Step Works When:
+- More than 3-4 fields needed
+- Complex B2B products needing segmentation
+- You need to collect different types of info
+
+### Multi-Step Best Practices
+- Show progress indicator
+- Lead with easy questions (name, email)
+- Put harder questions later (after psychological commitment)
+- Each step should feel completable in seconds
+- Allow back navigation
+- Save progress (don't lose data on refresh)
+
+**Progressive commitment pattern:**
+1. Email only (lowest barrier)
+2. Password + name
+3. Customization questions (optional)
+
+## Mobile Signup Optimization
+
+- Larger touch targets (44px+ height)
+- Appropriate keyboard types (email, tel, etc.)
+- Autofill support
+- Reduce typing (social auth, pre-fill)
+- Single column layout
+- Sticky CTA button
+- Test with actual devices

package/src/skills-lib/signup-flow-cro/references/measurement-output-patterns.md

@@ -0,0 +1,62 @@
+# Measurement, Output Format, and Common Patterns
+
+Load this file when defining what to measure, formatting the audit/recommendation deliverable, or looking for a proven signup pattern by product type.
+
+## Measurement
+
+### Key Metrics
+- Form start rate (landed → started filling)
+- Form completion rate (started → submitted)
+- Field-level drop-off (which fields lose people)
+- Time to complete
+- Error rate by field
+- Mobile vs. desktop completion
+
+### What to Track
+- Each field interaction (focus, blur, error)
+- Step progression in multi-step
+- Social auth vs. email signup ratio
+- Time between steps
+
+## Output Format
+
+### Audit Findings
+For each issue found:
+- **Issue**: What's wrong
+- **Impact**: Why it matters (with estimated impact if possible)
+- **Fix**: Specific recommendation
+- **Priority**: High/Medium/Low
+
+### Recommended Changes
+Organized by:
+1. Quick wins (same-day fixes)
+2. High-impact changes (week-level effort)
+3. Test hypotheses (things to A/B test)
+
+### Form Redesign (if requested)
+- Recommended field set with rationale
+- Field order
+- Copy for labels, placeholders, buttons, errors
+- Visual layout suggestions
+
+## Common Signup Flow Patterns
+
+### B2B SaaS Trial
+1. Email + Password (or Google auth)
+2. Name + Company (optional: role)
+3. → Onboarding flow
+
+### B2C App
+1. Google/Apple auth OR Email
+2. → Product experience
+3. Profile completion later
+
+### Waitlist/Early Access
+1. Email only
+2. Optional: Role/use case question
+3. → Waitlist confirmation
+
+### E-commerce Account
+1. Guest checkout as default
+2. Account creation optional post-purchase
+3. OR Social auth with single click