[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4PDQJ2630BEDQ5B4X6ADC":3,"skill-same:01M7A4PDQJ2630BEDQ5B4X6ADC":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A4PDQJ2630BEDQ5B4X6ADC","developer-signup-flow",null,"Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,...","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdeveloper-signup-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: developer-signup-flow\ndescription: \"Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,...\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdeveloper-signup-flow\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Developer Signup Flow\n## When to Use\n\nUse this skill when you need design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,...\n\n\nCreate signup experiences that respect developers' time and get them to code as fast as possible.\n\n## Overview\n\nDeveloper signup is your first chance to demonstrate that you understand developers. Every unnecessary form field, every extra click, every \"verify your email before continuing\" is a message that you don't value their time. The best developer signups feel like they barely exist—developers go from \"I want to try this\" to \"I'm writing code\" in under 60 seconds.\n\nThis skill covers OAuth integration, API key generation UX, progressive profiling, and measuring what actually matters in signup conversion.\n\n## Before You Start\n\nReview the `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-audience-context` skill to understand your target developer segments. Signup optimization varies significantly based on whether you're targeting hobbyists exploring on weekends versus enterprise developers evaluating tools for their company.\n\n## OAuth Options That Work\n\n### The GitHub-First Approach\n\nFor developer tools, GitHub OAuth should be your primary option. Here's why:\n\n1. **Identity verification built-in** - Active GitHub accounts have commit history, repos, and social proof\n2. **Scope familiarity** - Developers understand GitHub's permission model\n3. **Profile data** - You get username, email, and can infer experience level from public activity\n4. **Trust signal** - GitHub is where developers already live\n\n**Good implementation (Vercel):**\n- Single \"Continue with GitHub\" button dominates the page\n- Email option available but secondary\n- No password creation required\n- Immediate redirect to dashboard after OAuth\n\n**Bad implementation:**\n- GitHub, Google, Twitter, LinkedIn, Email, and \"Sign up with phone\" all given equal prominence\n- Requires email verification even after GitHub OAuth\n- Asks for additional profile information before showing dashboard\n\n### OAuth Option Hierarchy\n\nPrioritize based on your audience:\n\n| Audience | Primary | Secondary | Avoid |\n|----------|---------|-----------|-------|\n| Open source developers | GitHub | Email | Google Workspace |\n| Startup developers | GitHub | Google | Enterprise SSO |\n| Enterprise developers | SSO\u002FSAML | Google Workspace | Social logins |\n| Data scientists | GitHub | Google | Twitter |\n| Mobile developers | Google | GitHub | Facebook |\n\n### Google OAuth Considerations\n\nGoogle OAuth works well when:\n- Your tool integrates with Google Cloud services\n- You're targeting Android developers\n- Your audience includes non-technical stakeholders (product managers, designers)\n\nGoogle OAuth fails when:\n- Developers use personal Gmail but need to sign up with work identity\n- Your tool has no Google ecosystem integration\n- You require Google Workspace-specific scopes\n\n### Email Signup: When It Makes Sense\n\nEmail+password signup should exist but not dominate. It serves:\n- Developers in enterprise environments that block OAuth\n- Privacy-conscious developers who limit third-party access\n- Situations where GitHub\u002FGoogle accounts don't reflect professional identity\n\n**If you support email signup:**\n- Allow signup with just email—send magic link, don't require password creation\n- Never require email verification before showing the dashboard\n- Offer \"Set password later\" for developers who prefer magic links\n\n## Reducing Form Fields\n\n### The Zero-Field Ideal\n\nThe best signup has zero custom fields. Everything you need comes from OAuth:\n- Name (from OAuth profile)\n- Email (from OAuth profile)\n- Username\u002Fhandle (from GitHub username)\n- Avatar (from OAuth profile)\n\n### When You Must Ask Questions\n\nIf you genuinely need information, defer it:\n\n**Bad: Blocking signup**\n```\nCreate Account\n- Email\n- Password\n- Company Name (required)\n- Role (required)\n- Team Size (required)\n- How did you hear about us? (required)\n[Create Account]\n```\n\n**Good: Progressive collection**\n```\nContinue with GitHub\n[Immediate dashboard access]\n\n[Later, contextually in dashboard]\n\"To customize your experience, what are you building?\"\n[ ] API\u002FBackend\n[ ] Web app\n[ ] Mobile app\n[ ] Data pipeline\n[Skip for now]\n```\n\n### Field Elimination Checklist\n\nFor each field you want to add, answer:\n- Can we infer this from OAuth profile data?\n- Can we infer this from behavior after signup?\n- Can we ask this later when context makes it relevant?\n- What decision does this field enable that can't wait?\n- What's the conversion cost of this field?\n\nResearch suggests each additional required field reduces conversion by 5-10%.\n\n## API Key Generation UX\n\n### Immediate Key Generation\n\nDevelopers sign up to write code. Show them an API key immediately.\n\n**Good implementation (Stripe):**\n1. OAuth complete\n2. Dashboard shows test API keys immediately\n3. Keys are visible and copyable without extra clicks\n4. \"Reveal\" pattern for production keys, not test keys\n\n**Bad implementation:**\n1. OAuth complete\n2. \"Welcome! Complete your profile to get started\"\n3. Profile form required\n4. \"Create your first project\" wizard\n5. Project settings page\n6. \"Generate API key\" button\n7. Finally see a key\n\n### Key Display Best Practices\n\n```\nYour API Key\nsk_test_xxxxxxxxxxxxxxxxxxxx  [Copy]\n\n[Show in cURL example] [Show in SDK example]\n```\n\n- Show key in monospace font\n- Include one-click copy button\n- Show key in context (code example)\n- Test keys visible by default\n- Production keys behind \"reveal\" click\n- Never require downloading keys to a file\n\n### Multiple Keys and Key Management\n\nWait until developers need this. First-time signup should show one key.\n\nIntroduce key management when:\n- Developer creates a second project\n- Developer invites team members\n- Developer asks about key rotation\n\n## Onboarding Personalization\n\n### Use-Case Based Paths\n\nAsk one question, then customize the experience:\n\n**Question (shown post-signup, skippable):**\n\"What are you building?\"\n- [ ] Integrate with an existing app\n- [ ] Build something new\n- [ ] Evaluate for my team\n- [ ] Just exploring\n\n**Path customization:**\n\n| Selection | Dashboard emphasis | First CTA | Docs default |\n|-----------|-------------------|-----------|--------------|\n| Integrate existing | SDKs and integrations | \"Install SDK\" | Integration guides |\n| Build new | Quickstart tutorial | \"Start tutorial\" | Getting started |\n| Evaluate for team | Pricing and features | \"Book demo\" | Use cases |\n| Just exploring | Interactive playground | \"Try playground\" | API reference |\n\n### Framework\u002FLanguage Detection\n\nIf GitHub OAuth is used, check public repos for language patterns:\n\n```\nPrimary language: Python (45% of repos)\nAlso uses: JavaScript (30%), Go (15%)\n\n→ Show Python SDK first in docs\n→ Default code examples to Python\n→ Suggest Python quickstart\n```\n\n### Behavioral Personalization\n\nAfter signup, track and adapt:\n\n| Behavior | Adaptation |\n|----------|------------|\n| Copies HTTP request | Prefer HTTP examples over SDK-only flow |\n| Views pricing page early | Surface free tier limits in dashboard |\n| Creates multiple projects | Suggest team features |\n| Frequent docs visits | Add \"Stuck?\" help widget |\n\n## Progressive Profiling\n\n### What to Collect and When\n\n**Signup (OAuth only):**\n- Name, email, avatar (from OAuth)\n\n**First session (optional, in-context):**\n- Primary use case (one click)\n- Preferred language (inferred or one click)\n\n**After first API call:**\n- Company name (for enterprise features)\n- Team size (for collaboration features)\n\n**After hitting free tier limits:**\n- Phone number (for billing)\n- Billing address (for invoicing)\n\n**After upgrade:**\n- Full company profile (for account management)\n- Industry\u002Fvertical (for case studies)\n\n### Making Progressive Profiling Feel Natural\n\n**Bad: Random popup**\n```\n[Popup after 3 days]\nHelp us serve you better!\nCompany: ___\nRole: ___\nTeam size: ___\nHow did you hear about us: ___\n```\n\n**Good: Contextual ask**\n```\n[When developer invites first team member]\nTo set up your team workspace, what should we call it?\nCompany\u002FTeam name: ___\n\n[When developer hits rate limit]\nTo increase your rate limit, we need to verify your account:\nPhone: ___\n```\n\n## Measuring Signup Conversion\n\n### Primary Metrics\n\n**Signup start rate**\n- Visitors who click \"Sign up\" or \"Get started\"\n- Benchmark: 5-15% of landing page visitors\n\n**Signup completion rate**\n- Users who complete OAuth or form submission\n- Benchmark: 70-90% of signup starts (for OAuth)\n- Benchmark: 30-50% of signup starts (for forms)\n\n**Time to signup**\n- Seconds from signup click to dashboard\n- Benchmark: \u003C30 seconds for OAuth, \u003C60 seconds for forms\n\n### Activation Metrics (Post-Signup)\n\n**API key copy rate**\n- Users who copy their API key\n- Benchmark: 60-80% within first session\n\n**First API call rate**\n- Users who make at least one API call\n- Benchmark: 30-50% within first 24 hours\n\n**Time to first API call**\n- Minutes from signup to first API call\n- Benchmark: \u003C10 minutes for well-designed onboarding\n\n### Funnel Analysis\n\nTrack the complete funnel:\n```\nLanding page visitors: 10,000\n├── Clicked signup: 1,000 (10%)\n├── Completed signup: 800 (80% of clicks)\n├── Copied API key: 600 (75% of signups)\n├── First API call: 300 (50% of key copies)\n└── Second day return: 150 (50% of first call)\n```\n\nIdentify where developers drop off and why:\n- OAuth permission screen abandonment\n- Email verification delays\n- Confused by dashboard\n- Can't find API key\n- First API call failed\n\n### A\u002FB Testing Priorities\n\nTest in this order (highest impact first):\n1. Number of OAuth options shown\n2. Form field count\n3. Email verification timing\n4. API key placement on dashboard\n5. Default quickstart language\n6. Welcome email timing\n\n## Examples from Real Developer Tools\n\n### Excellent Signup: Vercel\n\n1. \"Continue with GitHub\" dominates\n2. OAuth completes in one click\n3. Immediate dashboard with import options\n4. No questions asked\n5. First deploy possible within 60 seconds\n\n### Excellent Signup: Stripe\n\n1. Email-based but minimal\n2. No email verification before dashboard\n3. Test API keys visible immediately\n4. Guided setup optional\n5. Clear test vs production modes\n\n### Poor Signup: [Common Patterns to Avoid]\n\n- \"Complete your profile\" blocking dashboard access\n- Email verification required before seeing anything\n- Required company name and team size\n- Mandatory phone verification\n- \"Create your first project\" wizard that can't be skipped\n- API keys hidden behind multiple navigation clicks\n\n## Tools\n\n### Analytics and Testing\n\n- **Amplitude\u002FMixpanel** - Funnel analysis and cohort tracking\n- **LaunchDarkly\u002FSplit** - A\u002FB testing OAuth flows\n- **FullStory\u002FLogRocket** - Session replay for signup debugging\n- **Customer.io\u002FIntercom** - Onboarding email sequences\n\n### Authentication Providers\n\n- **Auth0** - Full-featured but adds complexity\n- **Clerk** - Developer-focused, good defaults\n- **WorkOS** - Enterprise SSO when you need it\n- **Supabase Auth** - Simple, open source option\n- **Firebase Auth** - Good for mobile-first\n\n### API Key Management\n\n- **Unkey** - API key management as a service\n- **Custom** - Most developer tools build their own\n\n## Related Skills\n\n- `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-onboarding` - What happens after signup\n- `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-audience-context` - Understanding who's signing up\n- `\u002Fdevmarketing-skills\u002Fskills\u002Ffree-tier-strategy` - What they're signing up for\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Developer Signup Flow\n## When to Use\n\nUse this skill when you need design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion,...\n\n\nCreate signup experiences that respect developers' time and get them to code as fast as possible.\n\n## Overview\n\nDeveloper signup is your first chance to demonstrate that you understand developers. Every unnecessary form field, every extra click, every \"verify your email before continuing\" is a message that you don't value their time. The best developer signups feel like they barely exist—developers go from \"I want to try this\" to \"I'm writing code\" in under 60 seconds.\n\nThis skill covers OAuth integration, API key generation UX, progressive profiling, and measuring what actually matters in signup conversion.\n\n## Before You Start\n\nReview the `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-audience-context` skill to understand your target developer segments. Signup optimization varies significantly based on whether you're targeting hobbyists exploring on weekends versus enterprise developers evaluating tools for their company.\n\n## OAuth Options That Work\n\n### The GitHub-First Approach\n\nFor developer tools, GitHub OAuth should be your primary option. Here's why:\n\n1. **Identity verification built-in** - Active GitHub accounts have commit history, repos, and social proof\n2. **Scope familiarity** - Developers understand GitHub's permission model\n3. **Profile data** - You get username, email, and can infer experience level from public activity\n4. **Trust signal** - GitHub is where developers already live\n\n**Good implementation (Vercel):**\n- Single \"Continue with GitHub\" button dominates the page\n- Email option available but secondary\n- No password creation required\n- Immediate redirect to dashboard after OAuth\n\n**Bad implementation:**\n- GitHub, Google, Twitter, LinkedIn, Email, and \"Sign up with phone\" all given equal prominence\n- Requires email verification even after GitHub OAuth\n- Asks for additional profile information before showing dashboard\n\n### OAuth Option Hierarchy\n\nPrioritize based on your audience:\n\n| Audience | Primary | Secondary | Avoid |\n|----------|---------|-----------|-------|\n| Open source developers | GitHub | Email | Google Workspace |\n| Startup developers | GitHub | Google | Enterprise SSO |\n| Enterprise developers | SSO\u002FSAML | Google Workspace | Social logins |\n| Data scientists | GitHub | Google | Twitter |\n| Mobile developers | Google | GitHub | Facebook |\n\n### Google OAuth Considerations\n\nGoogle OAuth works well when:\n- Your tool integrates with Google Cloud services\n- You're targeting Android developers\n- Your audience includes non-technical stakeholders (product managers, designers)\n\nGoogle OAuth fails when:\n- Developers use personal Gmail but need to sign up with work identity\n- Your tool has no Google ecosystem integration\n- You require Google Workspace-specific scopes\n\n### Email Signup: When It Makes Sense\n\nEmail+password signup should exist but not dominate. It serves:\n- Developers in enterprise environments that block OAuth\n- Privacy-conscious developers who limit third-party access\n- Situations where GitHub\u002FGoogle accounts don't reflect professional identity\n\n**If you support email signup:**\n- Allow signup with just email—send magic link, don't require password creation\n- Never require email verification before showing the dashboard\n- Offer \"Set password later\" for developers who prefer magic links\n\n## Reducing Form Fields\n\n### The Zero-Field Ideal\n\nThe best signup has zero custom fields. Everything you need comes from OAuth:\n- Name (from OAuth profile)\n- Email (from OAuth profile)\n- Username\u002Fhandle (from GitHub username)\n- Avatar (from OAuth profile)\n\n### When You Must Ask Questions\n\nIf you genuinely need information, defer it:\n\n**Bad: Blocking signup**\n```\nCreate Account\n- Email\n- Password\n- Company Name (required)\n- Role (required)\n- Team Size (required)\n- How did you hear about us? (required)\n[Create Account]\n```\n\n**Good: Progressive collection**\n```\nContinue with GitHub\n[Immediate dashboard access]\n\n[Later, contextually in dashboard]\n\"To customize your experience, what are you building?\"\n[ ] API\u002FBackend\n[ ] Web app\n[ ] Mobile app\n[ ] Data pipeline\n[Skip for now]\n```\n\n### Field Elimination Checklist\n\nFor each field you want to add, answer:\n- Can we infer this from OAuth profile data?\n- Can we infer this from behavior after signup?\n- Can we ask this later when context makes it relevant?\n- What decision does this field enable that can't wait?\n- What's the conversion cost of this field?\n\nResearch suggests each additional required field reduces conversion by 5-10%.\n\n## API Key Generation UX\n\n### Immediate Key Generation\n\nDevelopers sign up to write code. Show them an API key immediately.\n\n**Good implementation (Stripe):**\n1. OAuth complete\n2. Dashboard shows test API keys immediately\n3. Keys are visible and copyable without extra clicks\n4. \"Reveal\" pattern for production keys, not test keys\n\n**Bad implementation:**\n1. OAuth complete\n2. \"Welcome! Complete your profile to get started\"\n3. Profile form required\n4. \"Create your first project\" wizard\n5. Project settings page\n6. \"Generate API key\" button\n7. Finally see a key\n\n### Key Display Best Practices\n\n```\nYour API Key\nsk_test_xxxxxxxxxxxxxxxxxxxx  [Copy]\n\n[Show in cURL example] [Show in SDK example]\n```\n\n- Show key in monospace font\n- Include one-click copy button\n- Show key in context (code example)\n- Test keys visible by default\n- Production keys behind \"reveal\" click\n- Never require downloading keys to a file\n\n### Multiple Keys and Key Management\n\nWait until developers need this. First-time signup should show one key.\n\nIntroduce key management when:\n- Developer creates a second project\n- Developer invites team members\n- Developer asks about key rotation\n\n## Onboarding Personalization\n\n### Use-Case Based Paths\n\nAsk one question, then customize the experience:\n\n**Question (shown post-signup, skippable):**\n\"What are you building?\"\n- [ ] Integrate with an existing app\n- [ ] Build something new\n- [ ] Evaluate for my team\n- [ ] Just exploring\n\n**Path customization:**\n\n| Selection | Dashboard emphasis | First CTA | Docs default |\n|-----------|-------------------|-----------|--------------|\n| Integrate existing | SDKs and integrations | \"Install SDK\" | Integration guides |\n| Build new | Quickstart tutorial | \"Start tutorial\" | Getting started |\n| Evaluate for team | Pricing and features | \"Book demo\" | Use cases |\n| Just exploring | Interactive playground | \"Try playground\" | API reference |\n\n### Framework\u002FLanguage Detection\n\nIf GitHub OAuth is used, check public repos for language patterns:\n\n```\nPrimary language: Python (45% of repos)\nAlso uses: JavaScript (30%), Go (15%)\n\n→ Show Python SDK first in docs\n→ Default code examples to Python\n→ Suggest Python quickstart\n```\n\n### Behavioral Personalization\n\nAfter signup, track and adapt:\n\n| Behavior | Adaptation |\n|----------|------------|\n| Copies HTTP request | Prefer HTTP examples over SDK-only flow |\n| Views pricing page early | Surface free tier limits in dashboard |\n| Creates multiple projects | Suggest team features |\n| Frequent docs visits | Add \"Stuck?\" help widget |\n\n## Progressive Profiling\n\n### What to Collect and When\n\n**Signup (OAuth only):**\n- Name, email, avatar (from OAuth)\n\n**First session (optional, in-context):**\n- Primary use case (one click)\n- Preferred language (inferred or one click)\n\n**After first API call:**\n- Company name (for enterprise features)\n- Team size (for collaboration features)\n\n**After hitting free tier limits:**\n- Phone number (for billing)\n- Billing address (for invoicing)\n\n**After upgrade:**\n- Full company profile (for account management)\n- Industry\u002Fvertical (for case studies)\n\n### Making Progressive Profiling Feel Natural\n\n**Bad: Random popup**\n```\n[Popup after 3 days]\nHelp us serve you better!\nCompany: ___\nRole: ___\nTeam size: ___\nHow did you hear about us: ___\n```\n\n**Good: Contextual ask**\n```\n[When developer invites first team member]\nTo set up your team workspace, what should we call it?\nCompany\u002FTeam name: ___\n\n[When developer hits rate limit]\nTo increase your rate limit, we need to verify your account:\nPhone: ___\n```\n\n## Measuring Signup Conversion\n\n### Primary Metrics\n\n**Signup start rate**\n- Visitors who click \"Sign up\" or \"Get started\"\n- Benchmark: 5-15% of landing page visitors\n\n**Signup completion rate**\n- Users who complete OAuth or form submission\n- Benchmark: 70-90% of signup starts (for OAuth)\n- Benchmark: 30-50% of signup starts (for forms)\n\n**Time to signup**\n- Seconds from signup click to dashboard\n- Benchmark: \u003C30 seconds for OAuth, \u003C60 seconds for forms\n\n### Activation Metrics (Post-Signup)\n\n**API key copy rate**\n- Users who copy their API key\n- Benchmark: 60-80% within first session\n\n**First API call rate**\n- Users who make at least one API call\n- Benchmark: 30-50% within first 24 hours\n\n**Time to first API call**\n- Minutes from signup to first API call\n- Benchmark: \u003C10 minutes for well-designed onboarding\n\n### Funnel Analysis\n\nTrack the complete funnel:\n```\nLanding page visitors: 10,000\n├── Clicked signup: 1,000 (10%)\n├── Completed signup: 800 (80% of clicks)\n├── Copied API key: 600 (75% of signups)\n├── First API call: 300 (50% of key copies)\n└── Second day return: 150 (50% of first call)\n```\n\nIdentify where developers drop off and why:\n- OAuth permission screen abandonment\n- Email verification delays\n- Confused by dashboard\n- Can't find API key\n- First API call failed\n\n### A\u002FB Testing Priorities\n\nTest in this order (highest impact first):\n1. Number of OAuth options shown\n2. Form field count\n3. Email verification timing\n4. API key placement on dashboard\n5. Default quickstart language\n6. Welcome email timing\n\n## Examples from Real Developer Tools\n\n### Excellent Signup: Vercel\n\n1. \"Continue with GitHub\" dominates\n2. OAuth completes in one click\n3. Immediate dashboard with import options\n4. No questions asked\n5. First deploy possible within 60 seconds\n\n### Excellent Signup: Stripe\n\n1. Email-based but minimal\n2. No email verification before dashboard\n3. Test API keys visible immediately\n4. Guided setup optional\n5. Clear test vs production modes\n\n### Poor Signup: [Common Patterns to Avoid]\n\n- \"Complete your profile\" blocking dashboard access\n- Email verification required before seeing anything\n- Required company name and team size\n- Mandatory phone verification\n- \"Create your first project\" wizard that can't be skipped\n- API keys hidden behind multiple navigation clicks\n\n## Tools\n\n### Analytics and Testing\n\n- **Amplitude\u002FMixpanel** - Funnel analysis and cohort tracking\n- **LaunchDarkly\u002FSplit** - A\u002FB testing OAuth flows\n- **FullStory\u002FLogRocket** - Session replay for signup debugging\n- **Customer.io\u002FIntercom** - Onboarding email sequences\n\n### Authentication Providers\n\n- **Auth0** - Full-featured but adds complexity\n- **Clerk** - Developer-focused, good defaults\n- **WorkOS** - Enterprise SSO when you need it\n- **Supabase Auth** - Simple, open source option\n- **Firebase Auth** - Good for mobile-first\n\n### API Key Management\n\n- **Unkey** - API key management as a service\n- **Custom** - Most developer tools build their own\n\n## Related Skills\n\n- `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-onboarding` - What happens after signup\n- `\u002Fdevmarketing-skills\u002Fskills\u002Fdeveloper-audience-context` - Understanding who's signing up\n- `\u002Fdevmarketing-skills\u002Fskills\u002Ffree-tier-strategy` - What they're signing up for\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdeveloper-signup-flow",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdeveloper-signup-flow",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill developer-signup-flow",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill developer-signup-flow",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill developer-signup-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdeveloper-signup-flow\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",1390,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdeveloper-signup-flow\u002FREADME.md",[60,67,74,81,90,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]