Developer First-Run CLI Onboarding Tour Script

Role: Lead Developer Experience (DX) Engineer and Technical Product Marketer

Context

• Command-Line Binary: {{cli_binary_name}}
• Infrastructure Targets: {{supported_cloud_providers}}
• Paradigm: {{architectural_paradigm}}
• Runtime Ecosystem: {{target_framework_stack}}
• Core DX Friction: {{friction_point_addressed}}
• Onboarding SLA: {{time_to_first_deploy}}

Task

Design an interactive CLI initialization tour and narrated screencast script that guides an engineer from package installation to a live deployed {{architectural_paradigm}} workload using {{cli_binary_name}} within {{time_to_first_deploy}}.

Method

1. Structure the onboarding journey into progressive disclosure steps: install, auth, scaffold, test, and deploy.
2. Write the exact shell invocation commands using {{cli_binary_name}} for {{target_framework_stack}}.
3. Design terminal prompts, auto-complete cues, and ASCII progress spinners.
4. Write developer voiceover script detailing why each step eliminates {{friction_point_addressed}}.
5. Include environment detection logic and config verification across {{supported_cloud_providers}}.
6. Script terminal-based local unit validation demonstrating immediate system feedback.
7. Detail the final deploy pipeline triggering real infrastructure state updates.
8. Conclude with programmatic next steps (shell auto-completion setup, plugin discovery, CI config export).

Constraints

• MUST adhere strictly to Unix CLI UX standards (POSIX compliance, meaningful exit codes, stderr separation).
• MUST NOT hide configuration files; explicitly explain config files generated on disk.
• Voiceover narration must sound like peer-to-peer technical guidance, avoiding hyperbole.
• Script must explicitly validate reaching the first deployment within {{time_to_first_deploy}}.

Output format

• Flowchart Outline: 5-step numbered breakdown of the initialization journey.
• Terminal & Voiceover Script: 5 sequential scenes, each containing:
  • Visual Screen State (Terminal UI/UX and flags)
  • Executed Command ({{cli_binary_name}} <subcommand>)
  • Stdout / Interactive Responses
  • Narrator Audio Script (under 60 words per scene)
• Post-Install Next Steps: 3 shell commands for CI integration and docs.

Self-review

• Can an engineer replicate the entire flow in {{target_framework_stack}} without prior documentation?
• Is the dialogue free of marketing jargon like 'revolutionary' or 'game-changing'?
• Does the tour directly resolve the friction point defined in {{friction_point_addressed}}?