100xprism 2.3.1

package/modules/signup-flow-cro/SKILL.md

@@ -0,0 +1,359 @@
+---
+name: signup-flow-cro
+description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
+category: marketing
+tier: on-demand
+---
+
+# Signup Flow CRO
+
+You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+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?
+
+---
+
+## 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
+
+**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
+
+---
+
+## Task-Specific Questions
+
+1. What's your current signup completion rate?
+2. Do you have field-level analytics on drop-off?
+3. What data is absolutely required before they can use the product?
+4. Are there compliance or verification requirements?
+5. What happens immediately after signup?
+
+---
+
+## Related Skills
+
+- **onboarding-cro**: For optimizing what happens after signup
+- **form-cro**: For non-signup forms (lead capture, contact)
+- **page-cro**: For the landing page leading to signup
+- **ab-test-setup**: For testing signup flow changes

package/modules/signup-flow-cro/evals/evals.json

@@ -0,0 +1,88 @@
+{
+  "skill_name": "signup-flow-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Audit our signup flow. We have a 3-step process: Step 1 asks for email, password, and full name. Step 2 asks for company name, company size, role, and industry. Step 3 asks for use case and how they heard about us. Current completion rate is 45%.",
+      "expected_output": "Should check for product-marketing-context.md first. Should identify the flow type (likely B2B SaaS trial). Should apply the core principles: minimize required fields (which of these are genuinely needed before they can use the product?). Should evaluate each step: Step 1 is reasonable, Step 2 fields are mostly deferrable to progressive profiling, Step 3 is entirely deferrable. Should recommend cutting to Step 1 only or at most 2 steps. Should provide audit findings in structured format (Issue, Impact, Fix, Priority). Should include Quick Wins, High-Impact Changes, and Test Hypotheses.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Identifies flow type",
+        "Applies minimize required fields principle",
+        "Evaluates each field for necessity",
+        "Recommends deferring most Step 2 and all Step 3 fields",
+        "Provides findings in structured format",
+        "Includes Quick Wins, High-Impact Changes, Test Hypotheses"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Should we add Google and Microsoft SSO to our signup page? We're a B2B project management tool and currently only have email/password signup.",
+      "expected_output": "Should apply the social auth options guidance. For B2B, should recommend Google and Microsoft as the primary SSO options (matching the B2B recommendation). Should explain benefits: higher conversion (less friction), pre-verified email, faster onboarding. Should recommend placing SSO prominently (often higher conversion than email). Should address implementation considerations: clear visual separation from email signup, button copy ('Sign up with Google' not just Google icon), consider which option to emphasize based on audience.",
+      "assertions": [
+        "Applies social auth options guidance",
+        "Recommends Google and Microsoft for B2B",
+        "Explains conversion benefits of SSO",
+        "Recommends prominent placement",
+        "Addresses visual separation from email signup",
+        "Provides implementation recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our signup form is just email and password but we still only get 35% of visitors to complete it. what else could be wrong?",
+      "expected_output": "Should trigger on casual phrasing. Should investigate beyond just form fields since the form is already minimal. Should apply trust and friction reduction guidance: is there a 'No credit card required' message? Privacy assurance? Testimonial near the form? Should check form-level issues: error handling, password requirements clarity, submit button copy. Should also look at pre-form factors: is the value proposition clear? Is the page optimized? (cross-reference page-cro). Should provide diagnostic checklist and recommendations.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Investigates beyond form fields",
+        "Applies trust and friction reduction",
+        "Checks for 'No credit card required' messaging",
+        "Checks error handling and password UX",
+        "Considers pre-form factors (value prop, page CRO)",
+        "Provides diagnostic checklist"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We require email verification before users can access the product. Is that hurting our conversion? Should we change it?",
+      "expected_output": "Should apply the verification flows guidance. Should explain that requiring verification before product access does create friction and likely reduces activation. Should recommend alternatives: delay verification until needed (let users explore first), magic link as alternative to password, let users start while verification is pending. Should discuss when email verification IS required (compliance, preventing abuse). Should provide specific recommendations for improving the verification experience if kept.",
+      "assertions": [
+        "Applies verification flows guidance",
+        "Explains verification friction impact",
+        "Recommends delaying verification",
+        "Suggests letting users explore while pending",
+        "Discusses when verification is required",
+        "Provides improvements if verification is kept"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "What experiments should we run on our signup page? We want to improve our trial signup rate.",
+      "expected_output": "Should apply the experiment ideas section. Should provide experiments across categories: form design experiments (layout, field count, SSO), copy and messaging experiments (headline, CTA text, trust elements), trial and commitment experiments (credit card required vs not, trial length), and post-submit experiments. Should prioritize experiments by likely impact. Should cross-reference ab-test-setup for proper experiment design.",
+      "assertions": [
+        "Applies experiment ideas section",
+        "Covers form design experiments",
+        "Covers copy and messaging experiments",
+        "Covers trial and commitment experiments",
+        "Prioritizes by likely impact",
+        "Cross-references ab-test-setup skill"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Users sign up fine but then never activate. Only 20% complete onboarding. What do we do?",
+      "expected_output": "Should recognize this is a post-signup onboarding problem, not a signup flow problem. Should defer to or cross-reference the onboarding-cro skill, which handles post-signup activation and onboarding optimization. Signup-flow-cro covers getting users through the signup form, not what happens after.",
+      "assertions": [
+        "Recognizes this as post-signup onboarding, not signup flow",
+        "References or defers to onboarding-cro skill",
+        "Explains signup-flow-cro covers the signup form, not post-signup"
+      ],
+      "files": []
+    }
+  ]
+}