[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CT9B0C3E04N4VR5XDDBMA4":3,"skill-same:01M6CT9B0C3E04N4VR5XDDBMA4":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6CT9B0C3E04N4VR5XDDBMA4","mobile-readiness",null,"Defines responsive web patterns and a React Native\u002FExpo plan so the product works on every screen. Use when building mobile-first UI or planning a native or PWA app.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-readiness\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"mobile","mobile readiness","web","react","planning","product","ui","first","plan","pwa","react native","use","expo","patterns","2026-11-10 10:12:30",false,"---\nname: mobile-readiness\ndescription: Defines responsive web patterns and a React Native\u002FExpo plan so the product works on every screen. Use when building mobile-first UI or planning a native or PWA app.\nuser-invocable: false\n---\n\n# Mobile Readiness\n\n## Reference\n- **ID**: S-ENG-09\n- **Category**: Engineering\n- **Inputs**: company.config.yaml (platforms section, tech_stack), RFCs\n- **Outputs**: mobile patterns guide (standards\u002Fmobile\u002F), per-feature responsive\u002Fmobile specifications\n- **Used by**: Engineering Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nEnsure every product surface works across all screen sizes and platforms. This skill produces responsive web patterns, React Native\u002FExpo native mobile architecture guidance, and PWA configuration -- driven by the platforms configured in `company.config.yaml`.\n\n## When to Use\n\n- New feature needs responsive design specifications\n- Product is adding native mobile (iOS\u002FAndroid) support\n- PWA support is being configured\n- Existing UI needs mobile optimization\n\n## Procedure\n\n### Step 1: Load Context\n\n1. Read `company.config.yaml` for:\n   - `platforms.targets` (web, mobile-web, ios, android)\n   - `platforms.mobile_framework` (array: expo, react-native-cli, etc.)\n   - `platforms.responsive` (true\u002Ffalse)\n   - `platforms.pwa` (true\u002Ffalse)\n   - `tech_stack.framework`\n2. Read relevant RFCs for the feature being built.\n3. Check `standards\u002Fmobile\u002F` for any existing mobile patterns.\n\n### Step 2: Responsive Web Patterns\n\nIf `platforms.targets` includes \"web\" or \"mobile-web\", produce `standards\u002Fmobile\u002Fresponsive-web.md` covering the following.\n\n**Required Viewport Configuration**:\n\n```html\n\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n```\n\n**Breakpoint System**:\n\n| Breakpoint | Range | Layout |\n|------------|-------|--------|\n| Mobile | 320px - 767px | Single column, stacked layout |\n| Tablet | 768px - 1023px | 2-column where appropriate |\n| Desktop | 1024px - 1439px | Full layout |\n| Large | 1440px+ | Max-width container, centered |\n\n**Touch Targets**:\n\n- Minimum size: 44x44px (WCAG 2.5.5 AAA)\n- Minimum spacing: 8px between targets\n- No hover-only interactions (must work with tap)\n\n**Mobile-First CSS**:\n\n- Write base styles for mobile, add complexity with `min-width` media queries\n- Avoid `max-width` queries (they override mobile-first approach)\n- Use relative units (`rem`, `em`, `%`, `vh`\u002F`vw`) over fixed pixels\n- Example pattern:\n\n```css\n\u002F* Base: mobile *\u002F\n.container { padding: 1rem; }\n\n\u002F* Tablet and up *\u002F\n@media (min-width: 768px) {\n  .container { padding: 2rem; max-width: 720px; }\n}\n\n\u002F* Desktop and up *\u002F\n@media (min-width: 1024px) {\n  .container { padding: 2rem; max-width: 960px; }\n}\n```\n\n**Image Optimization**:\n\n- `srcset` for responsive images\n- Lazy loading for below-fold images (`loading=\"lazy\"`)\n- WebP format with fallback\n- Maximum image width: 100% of container\n\n**Performance Budget**:\n\n| Metric | Target |\n|--------|--------|\n| LCP (Largest Contentful Paint) | \u003C 2.5s on 3G |\n| FID (First Input Delay) | \u003C 100ms |\n| CLS (Cumulative Layout Shift) | \u003C 0.1 |\n| Total page weight (initial load, mobile) | \u003C 500KB |\n\n**Typography**:\n\n- Minimum body text: 16px (prevents iOS zoom on focus)\n- Line height: 1.5 minimum for readability\n- No horizontal scrolling at any breakpoint\n\n**Forms on Mobile**:\n\n- Use appropriate input types (`email`, `tel`, `number`) for keyboard optimization\n- Labels above inputs (not beside)\n- Single column form layout on mobile\n- Clear error states with inline validation\n\n### Step 3: React Native \u002F Expo Patterns\n\nIf `platforms.targets` includes \"ios\" or \"android\", produce `standards\u002Fmobile\u002Fnative-mobile.md` covering the following.\n\n**Project Structure** (per `mobile_framework`):\n\n- **Expo (managed)**: `app\u002F` directory with file-based routing (Expo Router)\n- **Expo (bare)**: `ios\u002F` and `android\u002F` directories exposed alongside JS\n- **React Native CLI**: standard RN structure with platform folders\n\n**Navigation**:\n\n- Expo Router (recommended for Expo): file-based routing in `app\u002F`\n- React Navigation: Stack, Tab, Drawer navigators\n- Deep linking configuration for both platforms\n\n**Platform-Specific Considerations**:\n\n- **iOS**: Safe Area handling (`SafeAreaView`), status bar styling, home indicator inset\n- **Android**: back button handling, status bar translucency, navigation bar\n- **Keyboard handling**: `KeyboardAvoidingView`, keyboard dismiss on tap outside inputs\n\n**Shared Code Strategy**:\n\n- React Native Web for code sharing between web and native\n- Platform-specific files: `.ios.tsx`, `.android.tsx`, `.web.tsx`\n- Shared business logic in platform-agnostic modules, platform-specific UI where needed\n\n**Native Modules**:\n\n| Capability | Expo | React Native CLI |\n|------------|------|-----------------|\n| Camera | expo-camera | react-native-camera |\n| Push notifications | expo-notifications | react-native-push-notification |\n| Biometrics | expo-local-authentication | react-native-biometrics |\n| Secure storage | expo-secure-store | react-native-keychain |\n| General storage | AsyncStorage | AsyncStorage |\n\n**App Store Requirements**:\n\n- **iOS**: screenshots (6.7\", 6.5\", 5.5\"), app description, privacy nutrition labels\n- **Android**: screenshots, feature graphic, content rating questionnaire\n- **Both**: privacy policy URL required\n\n**OTA Updates**:\n\n- Expo Updates: JS bundle updates without app store review\n- Update strategies: automatic (on launch), manual (check for update), forced (critical fixes)\n- Rollback: revert to previous bundle if crash rate increases\n\n### Step 4: PWA Patterns\n\nIf `platforms.pwa` is true, document the following:\n\n- **Service worker registration**: register on load, handle update lifecycle\n- **Web app manifest**: icons (192px, 512px), theme color, background color, `display: standalone`\n- **Offline-first caching strategy**: cache static assets on install, network-first for API calls with cache fallback\n- **Install prompt handling**: listen for `beforeinstallprompt`, show custom install UI at appropriate moment\n\n### Step 5: Per-Feature Mobile Specification\n\nFor each feature being built, answer:\n\n1. **Responsive behavior**: how does this feature adapt across breakpoints? (stacking, hiding, simplifying)\n2. **Touch interactions**: does this feature need swipe, long press, pinch, or other gestures?\n3. **Offline behavior**: does this feature work offline? What degrades gracefully?\n4. **Platform-specific UI**: are there iOS\u002FAndroid differences in this feature's presentation?\n5. **Performance impact**: does this feature affect the mobile performance budget? (heavy images, large JS bundles, etc.)\n\n### Step 5.5: App Store Optimization (ASO)\n\nOnly produce this section when `platforms.targets` includes \"ios\" or \"android\".\n\n#### Keyword Research\n- **Primary keyword**: the single most important term users search for your app category\n- **Long-tail keywords**: 5-10 specific phrases (lower competition, higher intent)\n- **Competitor keywords**: terms where top competitors rank\n- Research tools: App Store Connect search metrics, Google Play Console acquisition reports, third-party (Sensor Tower, App Annie, AppFollow)\n\n#### Metadata Optimization\n\n| Element | iOS Limit | Android Limit | Best Practice |\n|---------|-----------|---------------|---------------|\n| Title | 30 chars | 30 chars | Primary keyword + brand name |\n| Subtitle | 30 chars | 80 chars (short desc) | Secondary keyword + value prop |\n| Keyword field | 100 chars | N\u002FA (use description) | Comma-separated, no spaces, no duplicates |\n| Description | 4000 chars | 4000 chars | First 3 lines visible without \"more\" — front-load benefits |\n\n- Title formula: `[Primary Keyword] - [Brand Name]` or `[Brand Name]: [Primary Keyword]`\n- Never stuff keywords — write for humans first, algorithms second\n- Update metadata quarterly based on search trend changes\n\n#### Screenshot Strategy\n- **First 3 screenshots are the conversion funnel** — they appear in search results\n  - Screenshot 1: Hero shot — the single most impressive feature or outcome\n  - Screenshot 2: Key differentiator — what makes this app different\n  - Screenshot 3: Social proof or secondary feature — builds confidence\n- Screenshots 4-8: additional features, settings, edge cases\n- Format: device frame + annotation text (benefit, not feature name)\n- A\u002FB test screenshot order using App Store Connect experiments or Google Play experiments\n\n#### Review Management\n- **Response templates**: thank positive reviewers, acknowledge negative feedback with resolution\n- **Rating prompt timing**: after 3+ successful sessions AND a positive action (never on first launch, never after an error)\n- **Star rating monitoring**: track weekly average, investigate any drop >0.2 stars\n- **Feature request extraction**: tag reviews mentioning missing features → feed to feedback-synthesizer\n\n#### ASO A\u002FB Testing\n- **iOS**: App Store Connect product page optimization (up to 3 treatments)\n- **Android**: Google Play Store listing experiments (up to 5 variants)\n- Test one element at a time: icon, screenshots, description, or title\n- Run for minimum 7 days, need 90% confidence before declaring winner\n\n### Step 6: Verify\n\n- Responsive breakpoints cover all screen sizes (320px through 1440px+)\n- Touch targets meet 44x44px minimum\n- Performance budget is achievable with the planned feature set\n- Platform-specific patterns are documented for all configured targets\n- Run `.\u002Ftools\u002Fartifact\u002Fvalidate.sh` on any produced artifacts\n\n## Quality Checklist\n\n- [ ] Viewport meta tag specified\n- [ ] Breakpoints defined with layout guidance per breakpoint\n- [ ] Touch targets minimum 44x44px enforced\n- [ ] Mobile-first CSS approach documented\n- [ ] Image optimization patterns specified (srcset, lazy loading, WebP)\n- [ ] Performance budget defined (LCP, FID, CLS thresholds)\n- [ ] If native mobile: project structure, navigation, platform considerations documented\n- [ ] If PWA: service worker, manifest, offline strategy documented\n- [ ] Per-feature template includes responsive, touch, offline, platform sections\n- [ ] If native mobile: ASO keyword research completed (primary + long-tail)\n- [ ] If native mobile: metadata optimized within character limits\n- [ ] If native mobile: first 3 screenshots form a conversion narrative\n- [ ] If native mobile: review management and rating prompt strategy defined\n","# Mobile Readiness\n\n## Reference\n- **ID**: S-ENG-09\n- **Category**: Engineering\n- **Inputs**: company.config.yaml (platforms section, tech_stack), RFCs\n- **Outputs**: mobile patterns guide (standards\u002Fmobile\u002F), per-feature responsive\u002Fmobile specifications\n- **Used by**: Engineering Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\n\nEnsure every product surface works across all screen sizes and platforms. This skill produces responsive web patterns, React Native\u002FExpo native mobile architecture guidance, and PWA configuration -- driven by the platforms configured in `company.config.yaml`.\n\n## When to Use\n\n- New feature needs responsive design specifications\n- Product is adding native mobile (iOS\u002FAndroid) support\n- PWA support is being configured\n- Existing UI needs mobile optimization\n\n## Procedure\n\n### Step 1: Load Context\n\n1. Read `company.config.yaml` for:\n   - `platforms.targets` (web, mobile-web, ios, android)\n   - `platforms.mobile_framework` (array: expo, react-native-cli, etc.)\n   - `platforms.responsive` (true\u002Ffalse)\n   - `platforms.pwa` (true\u002Ffalse)\n   - `tech_stack.framework`\n2. Read relevant RFCs for the feature being built.\n3. Check `standards\u002Fmobile\u002F` for any existing mobile patterns.\n\n### Step 2: Responsive Web Patterns\n\nIf `platforms.targets` includes \"web\" or \"mobile-web\", produce `standards\u002Fmobile\u002Fresponsive-web.md` covering the following.\n\n**Required Viewport Configuration**:\n\n```html\n\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n```\n\n**Breakpoint System**:\n\n| Breakpoint | Range | Layout |\n|------------|-------|--------|\n| Mobile | 320px - 767px | Single column, stacked layout |\n| Tablet | 768px - 1023px | 2-column where appropriate |\n| Desktop | 1024px - 1439px | Full layout |\n| Large | 1440px+ | Max-width container, centered |\n\n**Touch Targets**:\n\n- Minimum size: 44x44px (WCAG 2.5.5 AAA)\n- Minimum spacing: 8px between targets\n- No hover-only interactions (must work with tap)\n\n**Mobile-First CSS**:\n\n- Write base styles for mobile, add complexity with `min-width` media queries\n- Avoid `max-width` queries (they override mobile-first approach)\n- Use relative units (`rem`, `em`, `%`, `vh`\u002F`vw`) over fixed pixels\n- Example pattern:\n\n```css\n\u002F* Base: mobile *\u002F\n.container { padding: 1rem; }\n\n\u002F* Tablet and up *\u002F\n@media (min-width: 768px) {\n  .container { padding: 2rem; max-width: 720px; }\n}\n\n\u002F* Desktop and up *\u002F\n@media (min-width: 1024px) {\n  .container { padding: 2rem; max-width: 960px; }\n}\n```\n\n**Image Optimization**:\n\n- `srcset` for responsive images\n- Lazy loading for below-fold images (`loading=\"lazy\"`)\n- WebP format with fallback\n- Maximum image width: 100% of container\n\n**Performance Budget**:\n\n| Metric | Target |\n|--------|--------|\n| LCP (Largest Contentful Paint) | \u003C 2.5s on 3G |\n| FID (First Input Delay) | \u003C 100ms |\n| CLS (Cumulative Layout Shift) | \u003C 0.1 |\n| Total page weight (initial load, mobile) | \u003C 500KB |\n\n**Typography**:\n\n- Minimum body text: 16px (prevents iOS zoom on focus)\n- Line height: 1.5 minimum for readability\n- No horizontal scrolling at any breakpoint\n\n**Forms on Mobile**:\n\n- Use appropriate input types (`email`, `tel`, `number`) for keyboard optimization\n- Labels above inputs (not beside)\n- Single column form layout on mobile\n- Clear error states with inline validation\n\n### Step 3: React Native \u002F Expo Patterns\n\nIf `platforms.targets` includes \"ios\" or \"android\", produce `standards\u002Fmobile\u002Fnative-mobile.md` covering the following.\n\n**Project Structure** (per `mobile_framework`):\n\n- **Expo (managed)**: `app\u002F` directory with file-based routing (Expo Router)\n- **Expo (bare)**: `ios\u002F` and `android\u002F` directories exposed alongside JS\n- **React Native CLI**: standard RN structure with platform folders\n\n**Navigation**:\n\n- Expo Router (recommended for Expo): file-based routing in `app\u002F`\n- React Navigation: Stack, Tab, Drawer navigators\n- Deep linking configuration for both platforms\n\n**Platform-Specific Considerations**:\n\n- **iOS**: Safe Area handling (`SafeAreaView`), status bar styling, home indicator inset\n- **Android**: back button handling, status bar translucency, navigation bar\n- **Keyboard handling**: `KeyboardAvoidingView`, keyboard dismiss on tap outside inputs\n\n**Shared Code Strategy**:\n\n- React Native Web for code sharing between web and native\n- Platform-specific files: `.ios.tsx`, `.android.tsx`, `.web.tsx`\n- Shared business logic in platform-agnostic modules, platform-specific UI where needed\n\n**Native Modules**:\n\n| Capability | Expo | React Native CLI |\n|------------|------|-----------------|\n| Camera | expo-camera | react-native-camera |\n| Push notifications | expo-notifications | react-native-push-notification |\n| Biometrics | expo-local-authentication | react-native-biometrics |\n| Secure storage | expo-secure-store | react-native-keychain |\n| General storage | AsyncStorage | AsyncStorage |\n\n**App Store Requirements**:\n\n- **iOS**: screenshots (6.7\", 6.5\", 5.5\"), app description, privacy nutrition labels\n- **Android**: screenshots, feature graphic, content rating questionnaire\n- **Both**: privacy policy URL required\n\n**OTA Updates**:\n\n- Expo Updates: JS bundle updates without app store review\n- Update strategies: automatic (on launch), manual (check for update), forced (critical fixes)\n- Rollback: revert to previous bundle if crash rate increases\n\n### Step 4: PWA Patterns\n\nIf `platforms.pwa` is true, document the following:\n\n- **Service worker registration**: register on load, handle update lifecycle\n- **Web app manifest**: icons (192px, 512px), theme color, background color, `display: standalone`\n- **Offline-first caching strategy**: cache static assets on install, network-first for API calls with cache fallback\n- **Install prompt handling**: listen for `beforeinstallprompt`, show custom install UI at appropriate moment\n\n### Step 5: Per-Feature Mobile Specification\n\nFor each feature being built, answer:\n\n1. **Responsive behavior**: how does this feature adapt across breakpoints? (stacking, hiding, simplifying)\n2. **Touch interactions**: does this feature need swipe, long press, pinch, or other gestures?\n3. **Offline behavior**: does this feature work offline? What degrades gracefully?\n4. **Platform-specific UI**: are there iOS\u002FAndroid differences in this feature's presentation?\n5. **Performance impact**: does this feature affect the mobile performance budget? (heavy images, large JS bundles, etc.)\n\n### Step 5.5: App Store Optimization (ASO)\n\nOnly produce this section when `platforms.targets` includes \"ios\" or \"android\".\n\n#### Keyword Research\n- **Primary keyword**: the single most important term users search for your app category\n- **Long-tail keywords**: 5-10 specific phrases (lower competition, higher intent)\n- **Competitor keywords**: terms where top competitors rank\n- Research tools: App Store Connect search metrics, Google Play Console acquisition reports, third-party (Sensor Tower, App Annie, AppFollow)\n\n#### Metadata Optimization\n\n| Element | iOS Limit | Android Limit | Best Practice |\n|---------|-----------|---------------|---------------|\n| Title | 30 chars | 30 chars | Primary keyword + brand name |\n| Subtitle | 30 chars | 80 chars (short desc) | Secondary keyword + value prop |\n| Keyword field | 100 chars | N\u002FA (use description) | Comma-separated, no spaces, no duplicates |\n| Description | 4000 chars | 4000 chars | First 3 lines visible without \"more\" — front-load benefits |\n\n- Title formula: `[Primary Keyword] - [Brand Name]` or `[Brand Name]: [Primary Keyword]`\n- Never stuff keywords — write for humans first, algorithms second\n- Update metadata quarterly based on search trend changes\n\n#### Screenshot Strategy\n- **First 3 screenshots are the conversion funnel** — they appear in search results\n  - Screenshot 1: Hero shot — the single most impressive feature or outcome\n  - Screenshot 2: Key differentiator — what makes this app different\n  - Screenshot 3: Social proof or secondary feature — builds confidence\n- Screenshots 4-8: additional features, settings, edge cases\n- Format: device frame + annotation text (benefit, not feature name)\n- A\u002FB test screenshot order using App Store Connect experiments or Google Play experiments\n\n#### Review Management\n- **Response templates**: thank positive reviewers, acknowledge negative feedback with resolution\n- **Rating prompt timing**: after 3+ successful sessions AND a positive action (never on first launch, never after an error)\n- **Star rating monitoring**: track weekly average, investigate any drop >0.2 stars\n- **Feature request extraction**: tag reviews mentioning missing features → feed to feedback-synthesizer\n\n#### ASO A\u002FB Testing\n- **iOS**: App Store Connect product page optimization (up to 3 treatments)\n- **Android**: Google Play Store listing experiments (up to 5 variants)\n- Test one element at a time: icon, screenshots, description, or title\n- Run for minimum 7 days, need 90% confidence before declaring winner\n\n### Step 6: Verify\n\n- Responsive breakpoints cover all screen sizes (320px through 1440px+)\n- Touch targets meet 44x44px minimum\n- Performance budget is achievable with the planned feature set\n- Platform-specific patterns are documented for all configured targets\n- Run `.\u002Ftools\u002Fartifact\u002Fvalidate.sh` on any produced artifacts\n\n## Quality Checklist\n\n- [ ] Viewport meta tag specified\n- [ ] Breakpoints defined with layout guidance per breakpoint\n- [ ] Touch targets minimum 44x44px enforced\n- [ ] Mobile-first CSS approach documented\n- [ ] Image optimization patterns specified (srcset, lazy loading, WebP)\n- [ ] Performance budget defined (LCP, FID, CLS thresholds)\n- [ ] If native mobile: project structure, navigation, platform considerations documented\n- [ ] If PWA: service worker, manifest, offline strategy documented\n- [ ] Per-feature template includes responsive, touch, offline, platform sections\n- [ ] If native mobile: ASO keyword research completed (primary + long-tail)\n- [ ] If native mobile: metadata optimized within character limits\n- [ ] If native mobile: first 3 screenshots form a conversion narrative\n- [ ] If native mobile: review management and rating prompt strategy defined\n",{"name":5,"description":7,"user-invocable":39},"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4",".claude\u002Fskills\u002Fmobile-readiness",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add vibbs\u002Fcompany-os --skill mobile-readiness",{"tool":57,"command":58},"bunx","bunx skills add vibbs\u002Fcompany-os --skill mobile-readiness",{"tool":60,"command":61},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill mobile-readiness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-readiness\u002FSKILL.md",true,[],[66,75,83,93,109,125],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":38},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[73,74],"typo field","fixture skill",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":38},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[82,74],"spaced comments",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":38},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[90,91,92,74],"crlf comments","CRLF","windows",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":38},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[100,101,102,103,104,105,74,106,107,108],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":118,"publishedAt":38},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[119,120,121,122,123,35,124],"workflow","router","workflow router","next","maps","artifacts",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":38},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[132,133,134,122,35,135,136,137,138],"weekly review","review","priorities","health","save","support","security"]