Claude Skill

suede-signup

Suede-owned signup conversion discipline. Use when auditing or redesigning account creation, registration, or trial-start flows, including field friction, progressive profiling, identity options, mobile behavior, abandonment, and measurement. NOT FOR: post-signup activation (use

LLM Mart · 0 points · 15 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download JasonColapietro-suede-creator-skills-skills_suede-signup-f192517.zip · 10 KB

jasoncolapietro/suede-creator-skills 125 12 forks MIT Updated 1d ago

Part of jasoncolapietro/suede-creator-skills — 70 skills

Install

skills CLI npx skills add https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-signup

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jasoncolapietro-suede-creator-skills@llmmart

Git git clone https://github.com/JasonColapietro/suede-creator-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jasoncolapietro/suede-creator-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Suede Signup Conversion

Suede Signup identifies measurable friction between intent and completed account creation, then turns it into accessible, security-preserving experiments. It optimizes only the registration boundary and hands post-account activation to the Suede onboarding lane.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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:

Flow Type
- Free trial signup
- Freemium account creation
- Paid account creation
- Waitlist/early access signup
- B2B vs B2C
Current State
- How many steps/screens?
- What fields are required?
- What's the current completion rate?
- Where do users drop off?
- Is there field-level analytics on drop-off, or only funnel totals?
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 suede-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:

Email only (lowest barrier)
Password + name
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

Do not open with what the flow does well. If no finding clears the bar, say so in one sentence and name the single measurement that is missing and would change the verdict.

Rank every finding by its effect on completion rate and return the top 8. If more survive, list the remainder by name in one line so nothing is dropped silently. Cap test hypotheses at 3.

Audit Findings

For each issue found:

Issue: What's wrong
Impact: The mechanism and the funnel step it affects (form start, field completion, submit, verification). Give a number only when it is labeled modeled and carries the assumption and the measured baseline it was applied to; otherwise omit the number.
Fix: Specific recommendation
Priority: High/Medium/Low

Recommended Changes

Organized by:

Quick wins (same-day fixes)
High-impact changes (week-level effort)
Test hypotheses (things to A/B test, at most 3)

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

Email + Password (or Google auth)
Name + Company (optional: role)
→ Onboarding flow

B2C App

Google/Apple auth OR Email
→ Product experience
Profile completion later

Waitlist/Early Access

Email only
Optional: Role/use case question
→ Waitlist confirmation

E-commerce Account

Guest checkout as default
Account creation optional post-purchase
OR Social auth with single click

Experiment Ideas

When producing test hypotheses, draw them from four families:

Form design (step count, field set, layout, auth options)
Copy and messaging (headline, CTA text, microcopy, trust elements)
Trial and commitment (card requirement, trial length, verification friction)
Post-submit (next-step messaging, instant access, auto-login)

For the full candidate menu inside each family, read references/experiments.md before writing the test hypotheses in Output Format.

Boundaries

Do not deploy signup or authentication changes, remove security, consent, age, identity, or legal controls, or alter stored user data without owner review.
Do not use deceptive defaults, forced consent, hidden costs, or inaccessible friction reduction.
Do not claim conversion lift without a current baseline and completed experiment; keep personal data out of examples and diagnostic output.

Routing

Use suede-onboarding for activation after account creation.
Use suede-site-alchemy for lead-capture and non-account forms.
Use suede-ab-testing to design and evaluate signup experiments.
Use suede-analytics to instrument funnel stages and read outcomes.

Files (suede-creator-skills)

agents

openai.yaml 553 B

interface:
  display_name: "Suede Signup"
  short_description: "Suede accessible signup and registration experiments"
  default_prompt: "Use $suede-signup on [target]. The user has a signup, registration, or trial-start flow that loses people partway through. Work through field-by-field audit, social versus email tradeoffs, progressive profiling, and recovering abandoned signups, ground every recommendation in evidence the user can check, and return the decisions, the reasoning, and what to measure next."
policy:
  allow_implicit_invocation: true

evals

evals.json 6 KB

{
  "skill_name": "suede-signup",
  "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.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.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, or verified testimonial near the form? Should check form-level issues such as error handling, password requirements clarity, and submit-button copy. Should also inspect pre-form value clarity and cross-reference `suede-site-alchemy`. Should provide a 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 form design, copy and messaging, trial commitment, and post-submit experience. Should prioritize experiments by evidence, reach, and implementation cost, then cross-reference `suede-ab-testing` for 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 suede-ab-testing"
      ],
      "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 `suede-onboarding`, which handles post-signup activation and onboarding optimization. `suede-signup` 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 suede-onboarding",
        "Explains signup covers the signup form, not post-signup"
      ],
      "files": []
    }
  ]
}

references

experiments.md 2.5 KB

# Signup Experiment Menu

Candidate tests for signup flows, grouped by family. Read this when the audit has
produced test hypotheses and you need the specific variants worth running for a
given family. Design, sizing, and stopping rules belong to `suede-ab-testing`;
this file only supplies the candidate list.

## 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

CARD.md 4.2 KB

# Skill Card — Suede Signup Conversion

<!-- Generated by scripts/build-skill-cards.mjs — do not hand-edit. -->
<!-- Regenerate with: npm run build:cards -->

Release record for the `suede-signup` skill, following the NVIDIA skill-card template (<https://docs.nvidia.com/skills/skill-cards>). It tells a reviewer what the skill does, who owns it, what it needs, what could go wrong, and what evidence backs the release — without requiring them to open the source first.

## Description

Suede-owned signup conversion discipline.

Status: production. Ships in the `suede-skills` plugin (the full pack) at release 0.19.0; loads as a Claude Code / Codex agent skill from this directory's [SKILL.md](./SKILL.md).

## Owner

Jason Colapietro, Suede Labs AI (<https://github.com/JasonColapietro>). Security contact: `info@suedeai.ai` per [SECURITY.md](../../SECURITY.md).

## License / Terms of Use

MIT ([LICENSE](../../LICENSE)). The pack's combined license expression is `MIT AND BSD-3-Clause`; this skill bundles no third-party licensed material of its own.

## Use Case

Target users: developers and creators running the skill inside a Claude Code or Codex CLI session.

Use when auditing or redesigning account creation, registration, or trial-start flows, including field friction, progressive profiling, identity options, mobile behavior, abandonment, and measurement.

Out of scope — post-signup activation (use suede-onboarding), lead-capture forms (use suede-site-alchemy), or deploying auth and compliance changes without review.

## Deployment Geography

Global. The skill is a prompt-and-script package that runs locally inside the invoking agent session; it pins no region-specific service of its own.

## Requirements / Dependencies

- A Claude Code or Codex CLI session with the `suede-skills` plugin installed (install options: <https://skills.suedeai.ai/>).
- Bundled files loaded relative to this directory: `agents/` (1 file), `references/` (1 file).
- Credentials: none are bundled or required by the skill files. Any tool or API credentials come from the host session; never paste credentials into skill files, prompts, or outputs.

## Known Risks and Mitigations

- Risk: an agent treats a quality gate as autonomous authority. Mitigation: every gate in the pack is advisory — it changes what is reported, never what the user decided; only extreme-risk findings (data loss, credential exposure, legal/rights violations, payment mistakes, irreversible public damage) pause for the user's explicit choice.
- Risk: a skill instruction is used to act outside its mandate. Mitigation: the hard limits in the skill body's "Boundaries" section, quoted below.

From "Boundaries":

- Do not deploy signup or authentication changes, remove security, consent, age, identity, or legal controls, or alter stored user data without owner review.
- Do not use deceptive defaults, forced consent, hidden costs, or inaccessible friction reduction.
- Do not claim conversion lift without a current baseline and completed experiment; keep personal data out of examples and diagnostic output.

## References

- Skill source: [`skills/suede-signup/SKILL.md`](./SKILL.md)
- Rendered reference page: <https://skills.suedeai.ai/skills/suede-signup.html>
- Security policy and reviewed scanner exceptions: [SECURITY.md](../../SECURITY.md) and [`.plugin-scanner.toml`](../../.plugin-scanner.toml) at the repo root

## Skill Output

Structured Markdown returned in the agent's response, shaped by the output contract defined in the skill body: "Output Format". The skill publishes, posts, and sends nothing without the user's explicit authorization; delivery decisions stay with the user.

## Skill Version

0.19.0 — the pack is single-versioned, so every skill releases together; see [VERSION](../../VERSION) and [CITATION.cff](../../CITATION.cff) for the release identifier this card describes.

## Ethical Considerations

- The skill produces recommendations for a human decision-maker. Publishing, sending, payment, and rights decisions stay with the user.
- Its gates require verifiable claims and honest reporting; do not use the skill to fabricate claims, evidence, metrics, or attribution.
- Report suspected misuse or a security concern privately per [SECURITY.md](../../SECURITY.md); do not open a public issue for it.

SKILL.md 9.1 KB

---
name: suede-signup
description: "Suede-owned signup conversion discipline. Use when auditing or redesigning account creation, registration, or trial-start flows, including field friction, progressive profiling, identity options, mobile behavior, abandonment, and measurement. NOT FOR: post-signup activation (use suede-onboarding), lead-capture forms (use suede-site-alchemy), or deploying auth and compliance changes without review."
metadata:
  version: 2.0.0
---

# Suede Signup Conversion

Suede Signup identifies measurable friction between intent and completed account
creation, then turns it into accessible, security-preserving experiments. It
optimizes only the registration boundary and hands post-account activation to
the Suede onboarding lane.

## Initial Assessment

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, 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?
   - Is there field-level analytics on drop-off, or only funnel totals?

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 `suede-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

Do not open with what the flow does well. If no finding clears the bar, say so in
one sentence and name the single measurement that is missing and would change the
verdict.

Rank every finding by its effect on completion rate and return the top 8. If more
survive, list the remainder by name in one line so nothing is dropped silently.
Cap test hypotheses at 3.

### Audit Findings
For each issue found:
- **Issue**: What's wrong
- **Impact**: The mechanism and the funnel step it affects (form start, field
  completion, submit, verification). Give a number only when it is labeled
  modeled and carries the assumption and the measured baseline it was applied to;
  otherwise omit the number.
- **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, at most 3)

### 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

When producing test hypotheses, draw them from four families:
- Form design (step count, field set, layout, auth options)
- Copy and messaging (headline, CTA text, microcopy, trust elements)
- Trial and commitment (card requirement, trial length, verification friction)
- Post-submit (next-step messaging, instant access, auto-login)

**For the full candidate menu inside each family**, read
[references/experiments.md](references/experiments.md) before writing the test
hypotheses in Output Format.

---

## Boundaries

- Do not deploy signup or authentication changes, remove security, consent, age,
  identity, or legal controls, or alter stored user data without owner review.
- Do not use deceptive defaults, forced consent, hidden costs, or inaccessible
  friction reduction.
- Do not claim conversion lift without a current baseline and completed
  experiment; keep personal data out of examples and diagnostic output.

## Routing

- Use `suede-onboarding` for activation after account creation.
- Use `suede-site-alchemy` for lead-capture and non-account forms.
- Use `suede-ab-testing` to design and evaluate signup experiments.
- Use `suede-analytics` to instrument funnel stages and read outcomes.

Comments (0)

No comments yet.

Reviews (0)

No reviews yet.

Claude Prompt

Tighten-my-prose editing prompt

Claude Skill

Adversarial code-review skill for Claude

Claude Workflow

Deep-research workflow (fan-out + verify)

Claude Skill

Conventional-commit writer for Claude

suede-signup

Install

Skill manifest

Suede Signup Conversion

Initial Assessment

Core Principles

1. Minimize Required Fields

2. Show Value Before Asking for Commitment

3. Reduce Perceived Effort

4. Remove Uncertainty

Field-by-Field Optimization

Email Field

Password Field

Name Field

Social Auth Options

Phone Number

Company/Organization

Use Case / Role Questions

Single-Step vs. Multi-Step

Single-Step Works When:

Multi-Step Works When:

Multi-Step Best Practices

Trust and Friction Reduction

At the Form Level

Error Handling

Microcopy

Mobile Signup Optimization

Post-Submit Experience

Success State

Verification Flows

Measurement

Key Metrics

What to Track

Output Format

Audit Findings

Recommended Changes

Form Redesign (if requested)

Common Signup Flow Patterns

B2B SaaS Trial

B2C App

Waitlist/Early Access

E-commerce Account

Experiment Ideas

Boundaries

Routing

Comments (0)

Reviews (0)

Related