Onboarding Flow Design

Onboarding Flow Design is a skill for Claude Code, Codex from GktuOktay/ai-skills. It costs 57 tokens per session (913 once invoked), scanned A, original, MIT.

A skill for designing the first-time experience of a web or mobile application. It covers onboarding, which introduces new users to a product, and progressive disclosure, which reveals information and options only when needed.

In plain words
What is it for?
Use it to plan welcome screens, product tours, checklists, guided steps, contextual tips, permission prompts, and other first-use flows.
Why use it?
It helps new users understand what to do without being overwhelmed by too much information or too many permission requests at once.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to plan welcome screens, product tours, checklists, guided steps, contextual tips, permission prompts, and other first-use flows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gktuoktay/ai-skills/onboarding
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add GktuOktay/ai-skills --skill onboarding
Clone the repo
git clone --depth 1 https://github.com/GktuOktay/ai-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for Onboarding Flow Design

README.md
[![agentmods](https://agentmods.dev/badge/skills/gktuoktay/ai-skills/onboarding/github.svg)](https://agentmods.dev/skills/gktuoktay/ai-skills/onboarding)
Your own site
<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/onboarding"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/onboarding/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for Onboarding Flow Design

Your own site · 80×15
<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/onboarding"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 913 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00913
Opus 5 $0.00028 $0.00456
Sonnet 5 $0.00011 $0.00183
Haiku 4.5 $0.00006 $0.00091

Measured 11d ago against content hash ddb3aa2d115e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Onboarding Flow Design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/onboarding/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Onboarding Flow Design

Creating an effective onboarding experience is critical for user retention, feature discovery, and product success. A well-designed onboarding flow guides users to their "Aha!" moment as quickly as possible.

1. First-Time User Experience (FTUE) Patterns

FTUE sets the tone for the user's relationship with the product. Key patterns include:

  • Welcome Screens: A warm greeting setting expectations and showcasing core value propositions.
  • Product Tours: Guided walkthroughs of the interface.
  • Progressive Profiling: Asking for user data incrementally rather than upfront.
  • Sandbox Environments: Providing a safe, pre-populated space for users to experiment.
  • Checklists: Gamified lists of tasks to guide initial actions.

2. Progressive Disclosure

Do not overwhelm the user. Reveal information and features only when they are needed.

  • Contextual Tooltips: Show hints when a user interacts with or hovers over a new feature.
  • Just-in-Time Permissions: Request permissions (camera, location, notifications) exactly when the feature requiring them is used, not immediately upon launch.
  • Advanced Features: Hide complex settings behind "Advanced" toggles or menus until the user demonstrates basic proficiency.

3. Empty States

Empty states (e.g., a newly created inbox or an empty dashboard) are prime onboarding opportunities.

  • Educate: Explain what will appear in this space.
  • Direct Action: Provide clear primary CTAs (e.g., "Create your first project").
  • Provide Templates: Offer starter content instead of starting from absolute zero.

4. Mobile App Permission Requests (iOS/Android Best Practices)

Mobile OS permissions can make or break an app. Rejection rates are high if handled poorly.

  • Prime the User: Before showing the system dialogue, show a custom pre-prompt explaining why the permission is needed and how it benefits the user.
  • Delay Requests: Never ask for push notifications or location access immediately after installation. Wait until the user performs an action that justifies it.
  • Graceful Degradation: If permission is denied, ensure the app still functions in a limited capacity and provide a path to enable it later in settings.

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 69 lines · 57 tokens per session scan A ddb3aa2d115e

Subscribe to this mod's changes

Onboarding Flow Design is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 57 tokens to every session and 913 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

RainMT-dv/skills-pack · 39 tokens

design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

RainMT-dv/skills-pack · 61 tokens

design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…

wondelai/skills · 132 tokens

distinctive-frontend-design

Context-driven aesthetic exploration with anti-cliche validation.

notque/vexjoy-agent · 16 tokens

tool-design-sprint-decide-and-storyboard

Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives Thursday's prototype build. The most decision-heavy day of the sprint. Use Wednesday morning and afternoon after Tuesday's…

product-on-purpose/pm-skills · 102 tokens

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

ComposioHQ/awesome-claude-skills · 59 tokens