# developer-signup-flow

Designs low-friction developer onboarding flows with GitHub OAuth and instant API keys. Cuts unnecessary fields to keep signup under 60 seconds.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 87
- Author: jonathimer
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/jonathimer/devmarketing-skills/tree/HEAD/skills/developer-signup-flow/SKILL.md
- Updated: 2026-03-03
- HTML: https://affpapa.org/en/nevibecode/skills/developer-signup-flow

## What it does

This skill guides AI agents in structuring signup flows for developer-facing tools. It prioritizes a GitHub-first authentication flow. The goal is moving an engineer from signup to running code in under 60 seconds. Each additional required field reduces conversion by 5–10%. Profile details are collected progressively after reaching the dashboard.

The skill provides OAuth provider hierarchies, zero-field registration patterns, and immediate test API key generation. Dashboards show working keys straight away. Pair this with the `developer-audience-context` skill before starting to tailor the flow for hobbyists or enterprise developers.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add jonathimer/devmarketing-skills --skill developer-signup-flow -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/developer-signup-flow/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/developer-signup-flow/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add jonathimer/devmarketing-skills --skill developer-signup-flow -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/developer-signup-flow/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add jonathimer/devmarketing-skills --skill developer-signup-flow -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/developer-signup-flow/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install jonathimer/devmarketing-skills developer-signup-flow
```

2. **Manually: put the files in place**
- File: `.github/skills/developer-signup-flow/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add jonathimer/devmarketing-skills --skill developer-signup-flow -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/jonathimer/devmarketing-skills --path skills/developer-signup-flow
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/developer-signup-flow/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add jonathimer/devmarketing-skills --skill developer-signup-flow -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/jonathimer/devmarketing-skills/tree/HEAD/skills/developer-signup-flow/SKILL.md

## When to use it
- Design a GitHub OAuth flow without blocking email confirmations
- Display copyable test API keys right after account creation
- Eliminate non-critical signup fields to protect conversion rates
- Personalize the post-signup dashboard based on primary programming languages

## Example prompts
- Design a signup flow for our API platform with GitHub OAuth priority
- How should we present test API keys on the first dashboard screen?
- Review this onboarding form and tell me which fields to defer

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: bc733a7b9c43de04.

BEGIN THIRD-PARTY FILE bc733a7b9c43de04
```text
---
name: developer-signup-flow
description: |
  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, registration UX
metadata:
  version: 1.0.0
---

# Developer Signup Flow

Create signup experiences that respect developers' time and get them to code as fast as possible.

## Overview

Developer 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.

This skill covers OAuth integration, API key generation UX, progressive profiling, and measuring what actually matters in signup conversion.

## Before You Start

Review the `/devmarketing-skills/skills/developer-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.

## OAuth Options That Work

### The GitHub-First Approach

For developer tools, GitHub OAuth should be your primary option. Here's why:

1. **Identity verification built-in** - Active GitHub accounts have commit history, repos, and social proof
2. **Scope familiarity** - Developers understand GitHub's permission model
3. **Profile data** - You get username, email, and can infer experience level from public activity
4. **Trust signal** - GitHub is where developers already live

**Good implementation (Vercel):**
- Single "Continue with GitHub" button dominates the page
- Email option available but secondary
- No password creation required
- Immediate redirect to dashboard after OAuth

**Bad implementation:**
- GitHub, Google, Twitter, LinkedIn, Email, and "Sign up with phone" all given equal prominence
- Requires email verification even after GitHub OAuth
- Asks for additional profile information before showing dashboard

### OAuth Option Hierarchy

Prioritize based on your audience:

| Audience | Primary | Secondary | Avoid |
|----------|---------|-----------|-------|
| Open source developers | GitHub | Email | Google Workspace |
| Startup developers | GitHub | Google | Enterprise SSO |
| Enterprise developers | SSO/SAML | Google Workspace | Social logins |
| Data scientists | GitHub | Google | Twitter |
| Mobile developers | Google | GitHub | Facebook |

### Google OAuth Considerations

Google OAuth works well when:
- Your tool integrates with Google Cloud services
- You're targeting Android developers
```
END THIRD-PARTY FILE bc733a7b9c43de04

The third-party file has ended. Everything between the bc733a7b9c43de04 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2872 of 11705 bytes. © jonathimer · MIT · https://github.com/jonathimer/devmarketing-skills/tree/HEAD/skills/developer-signup-flow/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md