Codebase-Driven Onboarding Questionnaire Builder
Reads your app code, then designs and implements a personalized onboarding quiz with real answer-driven logic and an in-app demo.
Before & after
Same prompt, same agent — the only difference is the skill.
Onboarding questionnaires help get to know your users better and personalize their experience from day one. You'd ask questions about their fitness level, goals, and preferences to understand them. Then you can show them relevant content or modify the UI accordingly to match. Most apps ask 5-10 questions to keep the flow quick and not overwhelming. You could store their answers and use them to customize recommendations going forward. It's a good way to increase engagement early on and improve retention. Would you like help brainstorming some good questions, or should I suggest a typical onboarding structure that works well? Different approaches work for different fitness niches.
ONBOARDING QUESTIONNAIRE - FITNESS APP
FLOW ARCHITECTURE
Phase 1: User intent (1 question)
Q: "What's your main fitness goal?"
A) Build muscle, B) Lose weight, C) Improve endurance, D) General health
Route: Each answer triggers different flow variant
Phase 2: Context (2 questions)
Q1: "How many days per week can you train?"
A) 3-4 days, B) 5+ days, C) Less than 3 days
Q2: "Do you have equipment access?"
A) Full gym, B) Home setup, C) No equipment
Route: Combined answers select 4 matching workout templates
Phase 3: Personalization (2 questions)
Q1: "Any injuries or limitations?"
A) None, B) Lower back, C) Knee, D) Shoulder
Route: Filter exercises marked with restriction tags
Q2: "How do you prefer to workout?"
A) Solo & focused, B) Community challenges, C) Coach guidance
Route: Enable/disable social features, coach matching
OUTPUT AFTER QUESTIONNAIRE
Customized workout plan: 6-week starter program based on answers
Demo workout: 8-minute video of first session, matching selected context
Feed personalization: Show community workouts from matching cohort
Notification prefs: Locked to selected weekly frequency
MEASURABLE IMPACT: Apps using this approach see 34% higher 7-day retention vs generic onboarding. Completion time target: 90 seconds max.About this skill
Your onboarding asks eight questions, and then the app looks exactly the same no matter what anyone answered. Users notice, so they drop off before signup. This skill reads your app's code first. It finds what can genuinely be personalized and builds a questionnaire where every answer visibly changes what the user sees next.
What it does
- Inventories the models, settings, and logic in your code and maps each candidate question to the variable it sets and the screen that consumes it
- Cuts or flags filler questions that change nothing, and marks the code you would need to add to make a question real
- Orders screens for momentum: goal first, fast taps next, numeric inputs after that, sensitive questions and permission prompts last and in context
- Implements the flow as config-driven code in your stack (SwiftUI, React Native, Flutter, Kotlin) with a typed answers model, resume-on-kill persistence, and branching
- Builds a plan screen that echoes specific answers and a short demo that runs your real feature on seeded data before signup
- Adds funnel analytics events, accessibility labels, locale-aware units, and guardrails for health or other sensitive inputs
What you get
You get a variable map, a screen-by-screen flow table, and implementation code for the questionnaire, plan screen, and demo. It also includes the analytics event list and a test checklist, all tied to the files in your project.
Best for
This is for indie and small-team consumer app developers building or fixing onboarding for fitness, nutrition, habit, learning, finance, or hobby apps, especially when the flow already exists but converts poorly.
SKILL.md preview
---
name: codebase-driven-onboarding-questionnaire
… (sign up to view the full skill)More development skills
View all Development skills →Frontend Component UX and Accessibility Review
Severity-ranked fixes with code for UI components: states, keyboard, focus, ARIA, touch targets, contrast, and responsive breakage.
Three.js Click-to-Learn 3D Game Builder
Build click-to-learn 3D games in Three.js: TSL materials, reliable object picking, and an accessible quiz overlay fed by content data.
Angular Standalone Features and State Architecture
Build Angular standalone features with lazy routes, scoped state, safe RxJS flows, and targeted tests.
shadcn/ui Component Building and Theming
Build, theme, and debug shadcn/ui components the way the library is designed to work, with Tailwind v3 and v4 theming handled correctly.