[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ENGPPBDBMNTC5MX5YYNMY1":3,"skill-same:01M6ENGPPBDBMNTC5MX5YYNMY1":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":60},"01M6ENGPPBDBMNTC5MX5YYNMY1","onboard",null,"Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.","launchpathventures\u002Fditto-os","launchpathventures","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F248658966?v=4","01M6ENF40K8DMPD2Q4YBJX3EWK","01M6ENF4541FAB13MQFNS8RMK8",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fonboard\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[5,23,24,25,26,27,28,29,30,31,32,33],"run","help","onboarding","first","getting started","user","use","activation","time","empty","users","2026-11-10 10:12:30",false,"---\nname: onboard\ndescription: Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first. Additionally gather: the \"aha moment\" you want users to reach, and users' experience level.\n\n---\n\nCreate or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.\n\n## Assess Onboarding Needs\n\nUnderstand what users need to learn and why:\n\n1. **Identify the challenge**:\n   - What are users trying to accomplish?\n   - What's confusing or unclear about current experience?\n   - Where do users get stuck or drop off?\n   - What's the \"aha moment\" we want users to reach?\n\n2. **Understand the users**:\n   - What's their experience level? (Beginners, power users, mixed?)\n   - What's their motivation? (Excited and exploring? Required by work?)\n   - What's their time commitment? (5 minutes? 30 minutes?)\n   - What alternatives do they know? (Coming from competitor? New to category?)\n\n3. **Define success**:\n   - What's the minimum users need to learn to be successful?\n   - What's the key action we want them to take? (First project? First invite?)\n   - How do we know onboarding worked? (Completion rate? Time to value?)\n\n**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.\n\n## Onboarding Principles\n\nFollow these core principles:\n\n### Show, Don't Tell\n- Demonstrate with working examples, not just descriptions\n- Provide real functionality in onboarding, not separate tutorial mode\n- Use progressive disclosure - teach one thing at a time\n\n### Make It Optional (When Possible)\n- Let experienced users skip onboarding\n- Don't block access to product\n- Provide \"Skip\" or \"I'll explore on my own\" options\n\n### Time to Value\n- Get users to their \"aha moment\" ASAP\n- Front-load most important concepts\n- Teach 20% that delivers 80% of value\n- Save advanced features for contextual discovery\n\n### Context Over Ceremony\n- Teach features when users need them, not upfront\n- Empty states are onboarding opportunities\n- Tooltips and hints at point of use\n\n### Respect User Intelligence\n- Don't patronize or over-explain\n- Be concise and clear\n- Assume users can figure out standard patterns\n\n## Design Onboarding Experiences\n\nCreate appropriate onboarding for the context:\n\n### Initial Product Onboarding\n\n**Welcome Screen**:\n- Clear value proposition (what is this product?)\n- What users will learn\u002Faccomplish\n- Time estimate (honest about commitment)\n- Option to skip (for experienced users)\n\n**Account Setup**:\n- Minimal required information (collect more later)\n- Explain why you're asking for each piece of information\n- Smart defaults where possible\n- Social login when appropriate\n\n**Core Concept Introduction**:\n- Introduce 1-3 core concepts (not everything)\n- Use simple language and examples\n- Interactive when possible (do, don't just read)\n- Progress indication (step 1 of 3)\n\n**First Success**:\n- Guide users to accomplish something real\n- Pre-populated examples or templates\n- Celebrate completion (but don't overdo it)\n- Clear next steps\n\n### Feature Discovery & Adoption\n\n**Empty States**:\nInstead of blank space, show:\n- What will appear here (description + screenshot\u002Fillustration)\n- Why it's valuable\n- Clear CTA to create first item\n- Example or template option\n\nExample:\n```\nNo projects yet\nProjects help you organize your work and collaborate with your team.\n[Create your first project] or [Start from template]\n```\n\n**Contextual Tooltips**:\n- Appear at relevant moment (first time user sees feature)\n- Point directly at relevant UI element\n- Brief explanation + benefit\n- Dismissable (with \"Don't show again\" option)\n- Optional \"Learn more\" link\n\n**Feature Announcements**:\n- Highlight new features when they're released\n- Show what's new and why it matters\n- Let users try immediately\n- Dismissable\n\n**Progressive Onboarding**:\n- Teach features when users encounter them\n- Badges or indicators on new\u002Funused features\n- Unlock complexity gradually (don't show all options immediately)\n\n### Guided Tours & Walkthroughs\n\n**When to use**:\n- Complex interfaces with many features\n- Significant changes to existing product\n- Industry-specific tools needing domain knowledge\n\n**How to design**:\n- Spotlight specific UI elements (dim rest of page)\n- Keep steps short (3-7 steps max per tour)\n- Allow users to click through tour freely\n- Include \"Skip tour\" option\n- Make replayable (help menu)\n\n**Best practices**:\n- Interactive > passive (let users click real buttons)\n- Focus on workflow, not features (\"Create a project\" not \"This is the project button\")\n- Provide sample data so actions work\n\n### Interactive Tutorials\n\n**When to use**:\n- Users need hands-on practice\n- Concepts are complex or unfamiliar\n- High stakes (better to practice in safe environment)\n\n**How to design**:\n- Sandbox environment with sample data\n- Clear objectives (\"Create a chart showing sales by region\")\n- Step-by-step guidance\n- Validation (confirm they did it right)\n- Graduation moment (you're ready!)\n\n### Documentation & Help\n\n**In-product help**:\n- Contextual help links throughout interface\n- Keyboard shortcut reference\n- Search-able help center\n- Video tutorials for complex workflows\n\n**Help patterns**:\n- `?` icon near complex features\n- \"Learn more\" links in tooltips\n- Keyboard shortcut hints (`⌘K` shown on search box)\n\n## Empty State Design\n\nEvery empty state needs:\n\n### What Will Be Here\n\"Your recent projects will appear here\"\n\n### Why It Matters  \n\"Projects help you organize your work and collaborate with your team\"\n\n### How to Get Started\n[Create project] or [Import from template]\n\n### Visual Interest\nIllustration or icon (not just text on blank page)\n\n### Contextual Help\n\"Need help getting started? [Watch 2-min tutorial]\"\n\n**Empty state types**:\n- **First use**: Never used this feature (emphasize value, provide template)\n- **User cleared**: Intentionally deleted everything (light touch, easy to recreate)\n- **No results**: Search or filter returned nothing (suggest different query, clear filters)\n- **No permissions**: Can't access (explain why, how to get access)\n- **Error state**: Failed to load (explain what happened, retry option)\n\n## Implementation Patterns\n\n### Technical approaches:\n\n**Tooltip libraries**: Tippy.js, Popper.js\n**Tour libraries**: Intro.js, Shepherd.js, React Joyride\n**Modal patterns**: Focus trap, backdrop, ESC to close\n**Progress tracking**: LocalStorage for \"seen\" states\n**Analytics**: Track completion, drop-off points\n\n**Storage patterns**:\n```javascript\n\u002F\u002F Track which onboarding steps user has seen\nlocalStorage.setItem('onboarding-completed', 'true');\nlocalStorage.setItem('feature-tooltip-seen-reports', 'true');\n```\n\n**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.\n\n**NEVER**:\n- Force users through long onboarding before they can use product\n- Patronize users with obvious explanations\n- Show same tooltip repeatedly (respect dismissals)\n- Block all UI during tour (let users explore)\n- Create separate tutorial mode disconnected from real product\n- Overwhelm with information upfront (progressive disclosure!)\n- Hide \"Skip\" or make it hard to find\n- Forget about returning users (don't show initial onboarding again)\n\n## Verify Onboarding Quality\n\nTest with real users:\n\n- **Time to completion**: Can users complete onboarding quickly?\n- **Comprehension**: Do users understand after completing?\n- **Action**: Do users take desired next step?\n- **Skip rate**: Are too many users skipping? (Maybe it's too long\u002Fnot valuable)\n- **Completion rate**: Are users completing? (If low, simplify)\n- **Time to value**: How long until users get first value?\n\nRemember: You're a product educator with excellent teaching instincts. Get users to their \"aha moment\" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence.","## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first. Additionally gather: the \"aha moment\" you want users to reach, and users' experience level.\n\n---\n\nCreate or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.\n\n## Assess Onboarding Needs\n\nUnderstand what users need to learn and why:\n\n1. **Identify the challenge**:\n   - What are users trying to accomplish?\n   - What's confusing or unclear about current experience?\n   - Where do users get stuck or drop off?\n   - What's the \"aha moment\" we want users to reach?\n\n2. **Understand the users**:\n   - What's their experience level? (Beginners, power users, mixed?)\n   - What's their motivation? (Excited and exploring? Required by work?)\n   - What's their time commitment? (5 minutes? 30 minutes?)\n   - What alternatives do they know? (Coming from competitor? New to category?)\n\n3. **Define success**:\n   - What's the minimum users need to learn to be successful?\n   - What's the key action we want them to take? (First project? First invite?)\n   - How do we know onboarding worked? (Completion rate? Time to value?)\n\n**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.\n\n## Onboarding Principles\n\nFollow these core principles:\n\n### Show, Don't Tell\n- Demonstrate with working examples, not just descriptions\n- Provide real functionality in onboarding, not separate tutorial mode\n- Use progressive disclosure - teach one thing at a time\n\n### Make It Optional (When Possible)\n- Let experienced users skip onboarding\n- Don't block access to product\n- Provide \"Skip\" or \"I'll explore on my own\" options\n\n### Time to Value\n- Get users to their \"aha moment\" ASAP\n- Front-load most important concepts\n- Teach 20% that delivers 80% of value\n- Save advanced features for contextual discovery\n\n### Context Over Ceremony\n- Teach features when users need them, not upfront\n- Empty states are onboarding opportunities\n- Tooltips and hints at point of use\n\n### Respect User Intelligence\n- Don't patronize or over-explain\n- Be concise and clear\n- Assume users can figure out standard patterns\n\n## Design Onboarding Experiences\n\nCreate appropriate onboarding for the context:\n\n### Initial Product Onboarding\n\n**Welcome Screen**:\n- Clear value proposition (what is this product?)\n- What users will learn\u002Faccomplish\n- Time estimate (honest about commitment)\n- Option to skip (for experienced users)\n\n**Account Setup**:\n- Minimal required information (collect more later)\n- Explain why you're asking for each piece of information\n- Smart defaults where possible\n- Social login when appropriate\n\n**Core Concept Introduction**:\n- Introduce 1-3 core concepts (not everything)\n- Use simple language and examples\n- Interactive when possible (do, don't just read)\n- Progress indication (step 1 of 3)\n\n**First Success**:\n- Guide users to accomplish something real\n- Pre-populated examples or templates\n- Celebrate completion (but don't overdo it)\n- Clear next steps\n\n### Feature Discovery & Adoption\n\n**Empty States**:\nInstead of blank space, show:\n- What will appear here (description + screenshot\u002Fillustration)\n- Why it's valuable\n- Clear CTA to create first item\n- Example or template option\n\nExample:\n```\nNo projects yet\nProjects help you organize your work and collaborate with your team.\n[Create your first project] or [Start from template]\n```\n\n**Contextual Tooltips**:\n- Appear at relevant moment (first time user sees feature)\n- Point directly at relevant UI element\n- Brief explanation + benefit\n- Dismissable (with \"Don't show again\" option)\n- Optional \"Learn more\" link\n\n**Feature Announcements**:\n- Highlight new features when they're released\n- Show what's new and why it matters\n- Let users try immediately\n- Dismissable\n\n**Progressive Onboarding**:\n- Teach features when users encounter them\n- Badges or indicators on new\u002Funused features\n- Unlock complexity gradually (don't show all options immediately)\n\n### Guided Tours & Walkthroughs\n\n**When to use**:\n- Complex interfaces with many features\n- Significant changes to existing product\n- Industry-specific tools needing domain knowledge\n\n**How to design**:\n- Spotlight specific UI elements (dim rest of page)\n- Keep steps short (3-7 steps max per tour)\n- Allow users to click through tour freely\n- Include \"Skip tour\" option\n- Make replayable (help menu)\n\n**Best practices**:\n- Interactive > passive (let users click real buttons)\n- Focus on workflow, not features (\"Create a project\" not \"This is the project button\")\n- Provide sample data so actions work\n\n### Interactive Tutorials\n\n**When to use**:\n- Users need hands-on practice\n- Concepts are complex or unfamiliar\n- High stakes (better to practice in safe environment)\n\n**How to design**:\n- Sandbox environment with sample data\n- Clear objectives (\"Create a chart showing sales by region\")\n- Step-by-step guidance\n- Validation (confirm they did it right)\n- Graduation moment (you're ready!)\n\n### Documentation & Help\n\n**In-product help**:\n- Contextual help links throughout interface\n- Keyboard shortcut reference\n- Search-able help center\n- Video tutorials for complex workflows\n\n**Help patterns**:\n- `?` icon near complex features\n- \"Learn more\" links in tooltips\n- Keyboard shortcut hints (`⌘K` shown on search box)\n\n## Empty State Design\n\nEvery empty state needs:\n\n### What Will Be Here\n\"Your recent projects will appear here\"\n\n### Why It Matters  \n\"Projects help you organize your work and collaborate with your team\"\n\n### How to Get Started\n[Create project] or [Import from template]\n\n### Visual Interest\nIllustration or icon (not just text on blank page)\n\n### Contextual Help\n\"Need help getting started? [Watch 2-min tutorial]\"\n\n**Empty state types**:\n- **First use**: Never used this feature (emphasize value, provide template)\n- **User cleared**: Intentionally deleted everything (light touch, easy to recreate)\n- **No results**: Search or filter returned nothing (suggest different query, clear filters)\n- **No permissions**: Can't access (explain why, how to get access)\n- **Error state**: Failed to load (explain what happened, retry option)\n\n## Implementation Patterns\n\n### Technical approaches:\n\n**Tooltip libraries**: Tippy.js, Popper.js\n**Tour libraries**: Intro.js, Shepherd.js, React Joyride\n**Modal patterns**: Focus trap, backdrop, ESC to close\n**Progress tracking**: LocalStorage for \"seen\" states\n**Analytics**: Track completion, drop-off points\n\n**Storage patterns**:\n```javascript\n\u002F\u002F Track which onboarding steps user has seen\nlocalStorage.setItem('onboarding-completed', 'true');\nlocalStorage.setItem('feature-tooltip-seen-reports', 'true');\n```\n\n**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.\n\n**NEVER**:\n- Force users through long onboarding before they can use product\n- Patronize users with obvious explanations\n- Show same tooltip repeatedly (respect dismissals)\n- Block all UI during tour (let users explore)\n- Create separate tutorial mode disconnected from real product\n- Overwhelm with information upfront (progressive disclosure!)\n- Hide \"Skip\" or make it hard to find\n- Forget about returning users (don't show initial onboarding again)\n\n## Verify Onboarding Quality\n\nTest with real users:\n\n- **Time to completion**: Can users complete onboarding quickly?\n- **Comprehension**: Do users understand after completing?\n- **Action**: Do users take desired next step?\n- **Skip rate**: Are too many users skipping? (Maybe it's too long\u002Fnot valuable)\n- **Completion rate**: Are users completing? (If low, simplify)\n- **Time to value**: How long until users get first value?\n\nRemember: You're a product educator with excellent teaching instincts. Get users to their \"aha moment\" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence.",{"name":5,"description":7,"argument-hint":39,"user-invocable":40},"[target]",true,"main","b033b1a8919dbb7c98e97cf24547a2416f65b53e",".agents\u002Fskills\u002Fonboard",0,"https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os","https:\u002F\u002Fgithub.com\u002Flaunchpathventures","2026-06-08 19:31:48",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":40},[50,53,56],{"tool":51,"command":52},"npx","npx skills add launchpathventures\u002Fditto-os --skill onboard",{"tool":54,"command":55},"bunx","bunx skills add launchpathventures\u002Fditto-os --skill onboard",{"tool":57,"command":58},"pnpm","pnpm dlx skills add launchpathventures\u002Fditto-os --skill onboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fonboard\u002FSKILL.md",[],[62,81,101,122,127,132],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":34},"01M6ENJ12VWSMRZ4MW8550AG69","drain-queue","Cross-brief autopilot — claim the oldest ready brief whose Brief NNN deps are satisfied via atomic push, run \u002Fautobuild on each, stop when the queue is empty, blocked, or hits a failure.","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdrain-queue\u002FSKILL.md",[],[69,70,71,72,73,74,32,75,76,77,78,79,80,23],"drain queue","queue","push","autobuild","via","autopilot","claim","max","stop","ready","deps","brief",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":34},"01M6ENHXG16WJ4PN8CJHZYNT5T","dev-review","Post-coding exhaustive review — catches integration bugs, runtime crashes, performance issues, and convention drift across all changed files","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdev-review\u002FSKILL.md",[],[88,89,90,91,92,93,94,95,96,97,98,99,100],"dev","review","dev review","performance","issues","post","runtime","across","drift","files","fix","coding","integration",{"skillNo":102,"name":72,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":34},"01M6ENHSZBZFSB69TSV2TWGRJ1","End-to-end autopilot for a single brief — pre-flight, \u002Fdev-builder, fresh-subagent reviewers, push, open PR, mark **PR:** line on feature branch. Stops at the human merge gate.","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fautobuild\u002FSKILL.md",[],[72,107,108,80,109,110,111,112,113,74,114,115,116,117,118,119,120,88,121,71],"subagent","merge","open","line","name","merge gate","fresh","end","branch","open pr","feature","human","gate","builder","pr",{"skillNo":123,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":34},"01M6ENHPWYMN66EYQBV56HP9CW","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.catalyst\u002Fskills\u002Fdrain-queue\u002FSKILL.md",[],[70,69,78,72,73,74,32,75,76,77,79,80,71,23],{"skillNo":128,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":34},"01M6ENHM3W1A0MY44ZD8D4NWVF","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.catalyst\u002Fskills\u002Fdev-review\u002FSKILL.md",[],[90,88,89,100,92,91,99,93,94,95,96,97,98],{"skillNo":133,"name":72,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":34},"01M6ENHF62C7G6BC4YG44RWFB0","https:\u002F\u002Fgithub.com\u002Flaunchpathventures\u002Fditto-os\u002Fblob\u002Fmain\u002F.catalyst\u002Fskills\u002Fautobuild\u002FSKILL.md",[],[72,119,110,111,113,74,114,117,118,120,115,107,112,109,80,116,71,88,121,108]]