developer-onboarding

Name: developer-onboarding
Author: jonathimer

73installs6forks

How to install developer-onboarding?

jonathimer/devmarketing-skills/developer-onboarding

$npx -y skills add jonathimer/devmarketing-skills --skill developer-onboarding

Installs into the current project.

Summary

Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, re

Files · 1

View on GitHub

SKILL.md

1	# Developer Onboarding
2
3	Get developers from signup to working code as fast as possible, then guide them to deeper engagement.
4
5	## Overview
6
7	Developer onboarding is the critical window between "I signed up" and "I understand how to use this." You have about 10 minutes of developer attention. Every second of confusion, every error message without guidance, every "it should work but doesn't" moment costs you users.
8
9	Great onboarding feels like pair programming with someone who anticipated every question. Bad onboarding feels like being dropped in a foreign city without a map.
10
11	## Before You Start
12
13	Review the `/devmarketing-skills/skills/developer-audience-context` skill to understand your target developers. A hobbyist building side projects needs different onboarding than an enterprise architect evaluating tools for production. Review `/devmarketing-skills/skills/developer-signup-flow` to ensure signup flows smoothly into onboarding.
14
15	## Time-to-First-Value Optimization
16
17	### Defining "First Value"
18
19	First value isn't "made an API call." First value is when the developer sees your tool doing something useful for them.
20
21	\| Tool Type \| First Value Moment \|
22	\|-----------\|-------------------\|
23	\| API \| Response returns meaningful data \|
24	\| SDK \| Library performs expected function \|
25	\| Database \| Query returns results \|
26	\| Hosting \| App is live and accessible \|
27	\| Auth \| User successfully logs in \|
28	\| Payment \| Test charge processes \|
29
30	### Measuring Time to First Value (TTFV)
31
32	Track timestamps at each stage:
33
34	```
35	signup_completed: 2024-01-15T10:00:00Z
36	dashboard_loaded: 2024-01-15T10:00:05Z
37	api_key_copied: 2024-01-15T10:01:30Z
38	first_api_call: 2024-01-15T10:04:45Z
39	first_successful_response: 2024-01-15T10:04:46Z # TTFV = 4:46
40	```
41
42	Benchmarks by category:
43	- Simple APIs: <5 minutes
44	- SDKs requiring installation: <10 minutes
45	- Complex infrastructure: <30 minutes
46	- Self-hosted: <60 minutes
47
48	### Removing TTFV Obstacles
49
50	Map every step and eliminate blockers:
51
52	Common TTFV killers:
53	1. Email verification before dashboard access
54	2. API keys hidden in account settings
55	3. Quickstart assumes dependencies already installed
56	4. First example requires paid features
57	5. Error messages without resolution guidance
58	6. Docs search finds outdated tutorials
59
60	TTFV audit process:
61	1. Create new account (fresh browser, no cookies)
62	2. Screen record your first 30 minutes
63	3. Note every moment of confusion or friction
64	4. Time each step
65	5. Repeat with 5 different developer personas
66
67	## Quickstart Checklist Design
68
69	### The Ideal Quickstart Structure
70
71	```markdown
72	# Quickstart: [Specific Goal] in 5 Minutes
73
74	What you'll build: [Screenshot or description of end result]
75
76	Prerequisites:
77	- Node.js 18+ (check: node --version)
78	- npm or yarn
79
80	## Step 1: Install the SDK
81	[One command, copy button]
82
83	## Step 2: Initialize with your API key
84	[Code with placeholder, copy button]
85
86	## Step 3: Make your first request
87	[Complete working example, copy button]
88
89	## Step 4: See the result
90	[Expected output shown]
91
92	## Next steps
93	- [Link to common second task]
94	- [Link to full documentation]
95	```
96
97	### Checklist Patterns That Work
98
99	Progress indicators (Stripe style):
100	```
101	Your integration progress:
102	[x] Create account
103	[x] Get API keys
104	[ ] Install SDK
105	[ ] Make first API call
106	[ ] Handle webhooks
107	```
108
109	Contextual next steps (Vercel style):
110	```
111	You've deployed your first site.
112
113	What's next?
114	[ ] Add a custom domain
115	[ ] Set up environment variables
116	[ ] Enable analytics
117	```
118
119	### Common Quickstart Failures
120
121	Too much context upfront:
122	```
123	# Bad: The history of authentication
124	Before we begin, let's understand OAuth 2.0...
125	[500 words of background]
126
127	# Good: Jump to action
128	Install the SDK and make your first authenticated request.
129	```
130
131	Assuming environment:
132	```
133	# Bad
134	Run `npm install` to install dependencies.
135
136	# Good
137	npm install our-sdk
138	# Or with yarn: yarn add our-sdk
139	# Or with pnpm: pnpm add our-sdk
140	```
141
142	Hidden prerequisites:
143	```
144	# Bad (prerequisite discovered in Step 3)
145	Step 3: Connect to Redis
146	First, make sure Redis is running...
147
148	# Good (prerequisites listed upfront)
149	Prerequisites:
150	- Redis 6+ running locally (docker run -p 6379:6379 redis)
151	```
152
153	## Interactive vs Static Tutorials
154
155	### When to Use Interactive Tutorials
156
157	Interactive tutorials work for:
158	- Complex setup sequences
159	- Concepts that benefit from immediate feedback
160	- Onboarding flows where you control the environment
161	- Features requiring API keys or credentials
162
163	Interactive tutorial tools:
164	- Embedded code editors (CodeSandbox, StackBlitz)
165	- Terminal emulators (Instruqt, Killercoda)
166	- In-dashboard walkthroughs (Appcues, Pendo)
167	- I

People who liked this also viewed

6 picks

Type

developer-onboarding

73installs6forks

View on GitHub

How to install developer-onboarding?

jonathimer/devmarketing-skills/developer-onboarding

$npx -y skills add jonathimer/devmarketing-skills --skill developer-onboarding

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Developer Onboarding
2
3	Get developers from signup to working code as fast as possible, then guide them to deeper engagement.
4
5	## Overview
6
7	Developer onboarding is the critical window between "I signed up" and "I understand how to use this." You have about 10 minutes of developer attention. Every second of confusion, every error message without guidance, every "it should work but doesn't" moment costs you users.
8
9	Great onboarding feels like pair programming with someone who anticipated every question. Bad onboarding feels like being dropped in a foreign city without a map.
10
11	## Before You Start
12
13	Review the `/devmarketing-skills/skills/developer-audience-context` skill to understand your target developers. A hobbyist building side projects needs different onboarding than an enterprise architect evaluating tools for production. Review `/devmarketing-skills/skills/developer-signup-flow` to ensure signup flows smoothly into onboarding.
14
15	## Time-to-First-Value Optimization
16
17	### Defining "First Value"
18
19	First value isn't "made an API call." First value is when the developer sees your tool doing something useful for them.
20
21	\| Tool Type \| First Value Moment \|
22	\|-----------\|-------------------\|
23	\| API \| Response returns meaningful data \|
24	\| SDK \| Library performs expected function \|
25	\| Database \| Query returns results \|
26	\| Hosting \| App is live and accessible \|
27	\| Auth \| User successfully logs in \|
28	\| Payment \| Test charge processes \|
29
30	### Measuring Time to First Value (TTFV)
31
32	Track timestamps at each stage:
33
34	```
35	signup_completed: 2024-01-15T10:00:00Z
36	dashboard_loaded: 2024-01-15T10:00:05Z
37	api_key_copied: 2024-01-15T10:01:30Z
38	first_api_call: 2024-01-15T10:04:45Z
39	first_successful_response: 2024-01-15T10:04:46Z # TTFV = 4:46
40	```
41
42	Benchmarks by category:
43	- Simple APIs: <5 minutes
44	- SDKs requiring installation: <10 minutes
45	- Complex infrastructure: <30 minutes
46	- Self-hosted: <60 minutes
47
48	### Removing TTFV Obstacles
49
50	Map every step and eliminate blockers:
51
52	Common TTFV killers:
53	1. Email verification before dashboard access
54	2. API keys hidden in account settings
55	3. Quickstart assumes dependencies already installed
56	4. First example requires paid features
57	5. Error messages without resolution guidance
58	6. Docs search finds outdated tutorials
59
60	TTFV audit process:
61	1. Create new account (fresh browser, no cookies)
62	2. Screen record your first 30 minutes
63	3. Note every moment of confusion or friction
64	4. Time each step
65	5. Repeat with 5 different developer personas
66
67	## Quickstart Checklist Design
68
69	### The Ideal Quickstart Structure
70
71	```markdown
72	# Quickstart: [Specific Goal] in 5 Minutes
73
74	What you'll build: [Screenshot or description of end result]
75
76	Prerequisites:
77	- Node.js 18+ (check: node --version)
78	- npm or yarn
79
80	## Step 1: Install the SDK
81	[One command, copy button]
82
83	## Step 2: Initialize with your API key
84	[Code with placeholder, copy button]
85
86	## Step 3: Make your first request
87	[Complete working example, copy button]
88
89	## Step 4: See the result
90	[Expected output shown]
91
92	## Next steps
93	- [Link to common second task]
94	- [Link to full documentation]
95	```
96
97	### Checklist Patterns That Work
98
99	Progress indicators (Stripe style):
100	```
101	Your integration progress:
102	[x] Create account
103	[x] Get API keys
104	[ ] Install SDK
105	[ ] Make first API call
106	[ ] Handle webhooks
107	```
108
109	Contextual next steps (Vercel style):
110	```
111	You've deployed your first site.
112
113	What's next?
114	[ ] Add a custom domain
115	[ ] Set up environment variables
116	[ ] Enable analytics
117	```
118
119	### Common Quickstart Failures
120
121	Too much context upfront:
122	```
123	# Bad: The history of authentication
124	Before we begin, let's understand OAuth 2.0...
125	[500 words of background]
126
127	# Good: Jump to action
128	Install the SDK and make your first authenticated request.
129	```
130
131	Assuming environment:
132	```
133	# Bad
134	Run `npm install` to install dependencies.
135
136	# Good
137	npm install our-sdk
138	# Or with yarn: yarn add our-sdk
139	# Or with pnpm: pnpm add our-sdk
140	```
141
142	Hidden prerequisites:
143	```
144	# Bad (prerequisite discovered in Step 3)
145	Step 3: Connect to Redis
146	First, make sure Redis is running...
147
148	# Good (prerequisites listed upfront)
149	Prerequisites:
150	- Redis 6+ running locally (docker run -p 6379:6379 redis)
151	```
152
153	## Interactive vs Static Tutorials
154
155	### When to Use Interactive Tutorials
156
157	Interactive tutorials work for:
158	- Complex setup sequences
159	- Concepts that benefit from immediate feedback
160	- Onboarding flows where you control the environment
161	- Features requiring API keys or credentials
162
163	Interactive tutorial tools:
164	- Embedded code editors (CodeSandbox, StackBlitz)
165	- Terminal emulators (Instruqt, Killercoda)
166	- In-dashboard walkthroughs (Appcues, Pendo)
167	- I

People who liked this also viewed

6 picks

Type