[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DJY2CYV0JDC5DRAYBP03Y2":3,"skill-same:01M6DJY2CYV0JDC5DRAYBP03Y2":98},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6DJY2CYV0JDC5DRAYBP03Y2","ck:mobile-development",null,"Build mobile apps with React Native, Flutter, Swift\u002FSwiftUI, Kotlin\u002FJetpack Compose. Use for iOS\u002FAndroid, mobile UX, performance optimization, offline-first, app store deployment.","bkdev98\u002Fcautious-rotary-phone","bkdev98","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16166195?v=4","01M6DJJTJ383MRQSK35DJ6VE8N","Khanh Bui","01M6DJJTQ26138J2RXZGN4SF0N",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"ck:mobile development","development","mobile","mobile development","compose","apps","app","feature","platform","jetpack","build mobile","performance","jetpack compose","use","flutter","swiftui","kotlin","Optimization","deployment","react","2026-11-10 10:12:30",false,"---\nname: ck:mobile-development\ndescription: Build mobile apps with React Native, Flutter, Swift\u002FSwiftUI, Kotlin\u002FJetpack Compose. Use for iOS\u002FAndroid, mobile UX, performance optimization, offline-first, app store deployment.\nlicense: MIT\nversion: 1.0.0\nargument-hint: \"[platform] [feature]\"\n---\n\n# Mobile Development Skill\n\nProduction-ready mobile development with modern frameworks, best practices, and mobile-first thinking patterns.\n\n## When to Use\n\n- Building mobile applications (iOS, Android, or cross-platform)\n- Implementing mobile-first design and UX patterns\n- Optimizing for mobile constraints (battery, memory, network, small screens)\n- Making native vs cross-platform technology decisions\n- Implementing offline-first architecture and data sync\n- Following platform-specific guidelines (iOS HIG, Material Design)\n- Optimizing mobile app performance and user experience\n- Implementing mobile security and authentication\n- Testing mobile applications (unit, integration, E2E)\n- Deploying to App Store and Google Play\n\n## Technology Selection Guide\n\n**Cross-Platform Frameworks:**\n- **React Native**: JavaScript expertise, web code sharing, mature ecosystem (121K stars, 67% familiarity)\n- **Flutter**: Performance-critical apps, complex animations, fastest-growing (170K stars, 46% adoption)\n\n**Native Development:**\n- **iOS (Swift\u002FSwiftUI)**: Maximum iOS performance, latest features, Apple ecosystem integration\n- **Android (Kotlin\u002FJetpack Compose)**: Maximum Android performance, Material Design 3, platform optimization\n\nSee: `references\u002Fmobile-frameworks.md` for detailed framework comparisons\n\n## Mobile Development Mindset\n\n**The 10 Commandments of Mobile Development:**\n\n1. **Performance is Foundation, Not Feature** - 70% abandon apps >3s load time\n2. **Every Kilobyte, Every Millisecond Matters** - Mobile constraints are real\n3. **Offline-First by Default** - Network is unreliable, design for it\n4. **User Context > Developer Environment** - Think real-world usage scenarios\n5. **Platform Awareness Without Platform Lock-In** - Respect platform conventions\n6. **Iterate, Don't Perfect** - Ship, measure, improve cycle is survival\n7. **Security and Accessibility by Design** - Not afterthoughts\n8. **Test on Real Devices** - Simulators lie about performance\n9. **Architecture Scales with Complexity** - Don't over-engineer simple apps\n10. **Continuous Learning is Survival** - Mobile landscape evolves rapidly\n\nSee: `references\u002Fmobile-mindset.md` for thinking patterns and decision frameworks\n\n## Reference Navigation\n\n**Core Technologies:**\n- `mobile-frameworks.md` - React Native, Flutter, Swift, Kotlin, framework comparison matrices, when to use each\n- `mobile-ios.md` - Swift 6, SwiftUI, iOS architecture patterns, HIG, App Store requirements, platform capabilities\n- `mobile-android.md` - Kotlin, Jetpack Compose, Material Design 3, Play Store, Android-specific features\n\n**Best Practices & Development Mindset:**\n- `mobile-best-practices.md` - Mobile-first design, performance optimization, offline-first architecture, security, testing, accessibility, deployment, analytics\n- `mobile-debugging.md` - Debugging tools, performance profiling, crash analysis, network debugging, platform-specific debugging\n- `mobile-mindset.md` - Thinking patterns, decision frameworks, platform-specific thinking, common pitfalls, debugging strategies\n\n## Key Best Practices (2024-2025)\n\n**Performance Targets:**\n- App launch: \u003C2 seconds (70% abandon if >3s)\n- Memory usage: \u003C100MB for typical screens\n- Network requests: Batch and cache aggressively\n- Battery impact: Respect Doze Mode and background restrictions\n- Animation: 60 FPS (16.67ms per frame)\n\n**Architecture:**\n- MVVM for small-medium apps (clean separation, testable)\n- MVVM + Clean Architecture for large enterprise apps\n- Offline-first with hybrid sync (push + pull)\n- State management: Zustand (React Native), Riverpod 3 (Flutter), StateFlow (Android)\n\n**Security (OWASP Mobile Top 10):**\n- OAuth 2.0 + JWT + Biometrics for authentication\n- Keychain (iOS) \u002F KeyStore (Android) for sensitive data\n- Certificate pinning for network security\n- Never hardcode credentials or API keys\n- Implement proper session management\n\n**Testing Strategy:**\n- Unit tests: 70%+ coverage for business logic\n- Integration tests: Critical user flows\n- E2E tests: Detox (React Native), Appium (cross-platform), XCUITest (iOS), Espresso (Android)\n- Real device testing mandatory before release\n\n**Deployment:**\n- Fastlane for automation across platforms\n- Staged rollouts: Internal → Closed → Open → Production\n- Mandatory: iOS 17 SDK (2024), Android 15 API 35 (Aug 2025)\n- CI\u002FCD saves 20% development time\n\n## Quick Decision Matrix\n\n| Need | Choose |\n|------|--------|\n| JavaScript team, web code sharing | React Native |\n| Performance-critical, complex animations | Flutter |\n| Maximum iOS performance, latest features | Swift\u002FSwiftUI native |\n| Maximum Android performance, Material 3 | Kotlin\u002FCompose native |\n| Rapid prototyping | React Native + Expo |\n| Desktop + mobile | Flutter |\n| Enterprise with JavaScript skills | React Native |\n| Startup with limited resources | Flutter or React Native |\n| Gaming or heavy graphics | Native (Swift\u002FKotlin) or Unity |\n\n## Framework Quick Comparison (2024-2025)\n\n| Criterion | React Native | Flutter | Swift\u002FSwiftUI | Kotlin\u002FCompose |\n|-----------|--------------|---------|---------------|----------------|\n| **Stars** | 121K | 170K | N\u002FA | N\u002FA |\n| **Adoption** | 35% | 46% | iOS only | Android only |\n| **Performance** | 80-90% native | 85-95% native | 100% native | 100% native |\n| **Dev Speed** | Fast (hot reload) | Very fast (hot reload) | Fast (Xcode Previews) | Fast (Live Edit) |\n| **Learning Curve** | Easy (JavaScript) | Medium (Dart) | Medium (Swift) | Medium (Kotlin) |\n| **UI Paradigm** | Component-based | Widget-based | Declarative | Declarative |\n| **Community** | Huge (npm) | Growing | Apple ecosystem | Android ecosystem |\n| **Best For** | JS teams, web sharing | Performance, animations | iOS-only apps | Android-only apps |\n\n## Implementation Checklist\n\n**Project Setup:**\n- Choose framework → Initialize project → Configure dev environment → Setup version control → Configure CI\u002FCD → Team standards\n\n**Architecture:**\n- Choose pattern (MVVM\u002FClean) → Setup folders → State management → Navigation → API layer → Error handling → Logging\n\n**Core Features:**\n- Authentication → Data persistence → API integration → Offline sync → Push notifications → Deep linking → Analytics\n\n**UI\u002FUX:**\n- Design system → Platform guidelines → Accessibility → Responsive layouts → Dark mode → Localization → Animations\n\n**Performance:**\n- Image optimization → Lazy loading → Memory profiling → Network optimization → Battery testing → Launch time optimization\n\n**Quality:**\n- Unit tests (70%+) → Integration tests → E2E tests → Accessibility testing → Performance testing → Security audit\n\n**Security:**\n- Secure storage → Authentication flow → Network security → Input validation → Session management → Encryption\n\n**Deployment:**\n- App icons\u002Fsplash → Screenshots → Store listings → Privacy policy → TestFlight\u002FInternal testing → Staged rollout → Monitoring\n\n## Platform-Specific Guidelines\n\n**iOS (Human Interface Guidelines):**\n- Native navigation patterns (tab bar, navigation bar)\n- iOS design patterns (pull to refresh, swipe actions)\n- San Francisco font, iOS color system\n- Haptic feedback, 3D Touch\u002FHaptic Touch\n- Respect safe areas and notch\n\n**Android (Material Design 3):**\n- Material navigation (bottom nav, navigation drawer)\n- Floating action buttons, material components\n- Roboto font, Material You dynamic colors\n- Touch feedback (ripple effects)\n- Respect system bars and gestures\n\n## Common Pitfalls to Avoid\n\n1. **Testing only on simulators** - Real devices show true performance\n2. **Ignoring platform conventions** - Users expect platform-specific patterns\n3. **No offline handling** - Network failures will happen\n4. **Poor memory management** - Leads to crashes and poor UX\n5. **Hardcoded credentials** - Security vulnerability\n6. **No accessibility** - Excludes 15%+ of users\n7. **Premature optimization** - Optimize based on metrics, not assumptions\n8. **Over-engineering** - Start simple, scale as needed\n9. **Skipping real device testing** - Simulators don't show battery\u002Fnetwork issues\n10. **Not respecting battery** - Background processing must be justified\n\n## Performance Budgets\n\n**Recommended Targets:**\n- **App size**: \u003C50MB initial download, \u003C200MB total\n- **Launch time**: \u003C2 seconds to interactive\n- **Screen load**: \u003C1 second for cached data\n- **Network request**: \u003C3 seconds for API calls\n- **Memory**: \u003C100MB for typical screens, \u003C200MB peak\n- **Battery**: \u003C5% drain per hour of active use\n- **Frame rate**: 60 FPS (16.67ms per frame)\n\n## Resources\n\n**Official Documentation:**\n- React Native: https:\u002F\u002Freactnative.dev\u002F\n- Flutter: https:\u002F\u002Fflutter.dev\u002F\n- iOS HIG: https:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002F\n- Material Design: https:\u002F\u002Fm3.material.io\u002F\n- OWASP Mobile: https:\u002F\u002Fowasp.org\u002Fwww-project-mobile-top-10\u002F\n\n**Tools & Testing:**\n- Detox E2E: https:\u002F\u002Fwix.github.io\u002FDetox\u002F\n- Appium: https:\u002F\u002Fappium.io\u002F\n- Fastlane: https:\u002F\u002Ffastlane.tools\u002F\n- Firebase: https:\u002F\u002Ffirebase.google.com\u002F\n\n**Community:**\n- React Native Directory: https:\u002F\u002Freactnative.directory\u002F\n- Pub.dev (Flutter packages): https:\u002F\u002Fpub.dev\u002F\n- Awesome React Native: https:\u002F\u002Fgithub.com\u002Fjondot\u002Fawesome-react-native\n- Awesome Flutter: https:\u002F\u002Fgithub.com\u002FSolido\u002Fawesome-flutter\n","# Mobile Development Skill\n\nProduction-ready mobile development with modern frameworks, best practices, and mobile-first thinking patterns.\n\n## When to Use\n\n- Building mobile applications (iOS, Android, or cross-platform)\n- Implementing mobile-first design and UX patterns\n- Optimizing for mobile constraints (battery, memory, network, small screens)\n- Making native vs cross-platform technology decisions\n- Implementing offline-first architecture and data sync\n- Following platform-specific guidelines (iOS HIG, Material Design)\n- Optimizing mobile app performance and user experience\n- Implementing mobile security and authentication\n- Testing mobile applications (unit, integration, E2E)\n- Deploying to App Store and Google Play\n\n## Technology Selection Guide\n\n**Cross-Platform Frameworks:**\n- **React Native**: JavaScript expertise, web code sharing, mature ecosystem (121K stars, 67% familiarity)\n- **Flutter**: Performance-critical apps, complex animations, fastest-growing (170K stars, 46% adoption)\n\n**Native Development:**\n- **iOS (Swift\u002FSwiftUI)**: Maximum iOS performance, latest features, Apple ecosystem integration\n- **Android (Kotlin\u002FJetpack Compose)**: Maximum Android performance, Material Design 3, platform optimization\n\nSee: `references\u002Fmobile-frameworks.md` for detailed framework comparisons\n\n## Mobile Development Mindset\n\n**The 10 Commandments of Mobile Development:**\n\n1. **Performance is Foundation, Not Feature** - 70% abandon apps >3s load time\n2. **Every Kilobyte, Every Millisecond Matters** - Mobile constraints are real\n3. **Offline-First by Default** - Network is unreliable, design for it\n4. **User Context > Developer Environment** - Think real-world usage scenarios\n5. **Platform Awareness Without Platform Lock-In** - Respect platform conventions\n6. **Iterate, Don't Perfect** - Ship, measure, improve cycle is survival\n7. **Security and Accessibility by Design** - Not afterthoughts\n8. **Test on Real Devices** - Simulators lie about performance\n9. **Architecture Scales with Complexity** - Don't over-engineer simple apps\n10. **Continuous Learning is Survival** - Mobile landscape evolves rapidly\n\nSee: `references\u002Fmobile-mindset.md` for thinking patterns and decision frameworks\n\n## Reference Navigation\n\n**Core Technologies:**\n- `mobile-frameworks.md` - React Native, Flutter, Swift, Kotlin, framework comparison matrices, when to use each\n- `mobile-ios.md` - Swift 6, SwiftUI, iOS architecture patterns, HIG, App Store requirements, platform capabilities\n- `mobile-android.md` - Kotlin, Jetpack Compose, Material Design 3, Play Store, Android-specific features\n\n**Best Practices & Development Mindset:**\n- `mobile-best-practices.md` - Mobile-first design, performance optimization, offline-first architecture, security, testing, accessibility, deployment, analytics\n- `mobile-debugging.md` - Debugging tools, performance profiling, crash analysis, network debugging, platform-specific debugging\n- `mobile-mindset.md` - Thinking patterns, decision frameworks, platform-specific thinking, common pitfalls, debugging strategies\n\n## Key Best Practices (2024-2025)\n\n**Performance Targets:**\n- App launch: \u003C2 seconds (70% abandon if >3s)\n- Memory usage: \u003C100MB for typical screens\n- Network requests: Batch and cache aggressively\n- Battery impact: Respect Doze Mode and background restrictions\n- Animation: 60 FPS (16.67ms per frame)\n\n**Architecture:**\n- MVVM for small-medium apps (clean separation, testable)\n- MVVM + Clean Architecture for large enterprise apps\n- Offline-first with hybrid sync (push + pull)\n- State management: Zustand (React Native), Riverpod 3 (Flutter), StateFlow (Android)\n\n**Security (OWASP Mobile Top 10):**\n- OAuth 2.0 + JWT + Biometrics for authentication\n- Keychain (iOS) \u002F KeyStore (Android) for sensitive data\n- Certificate pinning for network security\n- Never hardcode credentials or API keys\n- Implement proper session management\n\n**Testing Strategy:**\n- Unit tests: 70%+ coverage for business logic\n- Integration tests: Critical user flows\n- E2E tests: Detox (React Native), Appium (cross-platform), XCUITest (iOS), Espresso (Android)\n- Real device testing mandatory before release\n\n**Deployment:**\n- Fastlane for automation across platforms\n- Staged rollouts: Internal → Closed → Open → Production\n- Mandatory: iOS 17 SDK (2024), Android 15 API 35 (Aug 2025)\n- CI\u002FCD saves 20% development time\n\n## Quick Decision Matrix\n\n| Need | Choose |\n|------|--------|\n| JavaScript team, web code sharing | React Native |\n| Performance-critical, complex animations | Flutter |\n| Maximum iOS performance, latest features | Swift\u002FSwiftUI native |\n| Maximum Android performance, Material 3 | Kotlin\u002FCompose native |\n| Rapid prototyping | React Native + Expo |\n| Desktop + mobile | Flutter |\n| Enterprise with JavaScript skills | React Native |\n| Startup with limited resources | Flutter or React Native |\n| Gaming or heavy graphics | Native (Swift\u002FKotlin) or Unity |\n\n## Framework Quick Comparison (2024-2025)\n\n| Criterion | React Native | Flutter | Swift\u002FSwiftUI | Kotlin\u002FCompose |\n|-----------|--------------|---------|---------------|----------------|\n| **Stars** | 121K | 170K | N\u002FA | N\u002FA |\n| **Adoption** | 35% | 46% | iOS only | Android only |\n| **Performance** | 80-90% native | 85-95% native | 100% native | 100% native |\n| **Dev Speed** | Fast (hot reload) | Very fast (hot reload) | Fast (Xcode Previews) | Fast (Live Edit) |\n| **Learning Curve** | Easy (JavaScript) | Medium (Dart) | Medium (Swift) | Medium (Kotlin) |\n| **UI Paradigm** | Component-based | Widget-based | Declarative | Declarative |\n| **Community** | Huge (npm) | Growing | Apple ecosystem | Android ecosystem |\n| **Best For** | JS teams, web sharing | Performance, animations | iOS-only apps | Android-only apps |\n\n## Implementation Checklist\n\n**Project Setup:**\n- Choose framework → Initialize project → Configure dev environment → Setup version control → Configure CI\u002FCD → Team standards\n\n**Architecture:**\n- Choose pattern (MVVM\u002FClean) → Setup folders → State management → Navigation → API layer → Error handling → Logging\n\n**Core Features:**\n- Authentication → Data persistence → API integration → Offline sync → Push notifications → Deep linking → Analytics\n\n**UI\u002FUX:**\n- Design system → Platform guidelines → Accessibility → Responsive layouts → Dark mode → Localization → Animations\n\n**Performance:**\n- Image optimization → Lazy loading → Memory profiling → Network optimization → Battery testing → Launch time optimization\n\n**Quality:**\n- Unit tests (70%+) → Integration tests → E2E tests → Accessibility testing → Performance testing → Security audit\n\n**Security:**\n- Secure storage → Authentication flow → Network security → Input validation → Session management → Encryption\n\n**Deployment:**\n- App icons\u002Fsplash → Screenshots → Store listings → Privacy policy → TestFlight\u002FInternal testing → Staged rollout → Monitoring\n\n## Platform-Specific Guidelines\n\n**iOS (Human Interface Guidelines):**\n- Native navigation patterns (tab bar, navigation bar)\n- iOS design patterns (pull to refresh, swipe actions)\n- San Francisco font, iOS color system\n- Haptic feedback, 3D Touch\u002FHaptic Touch\n- Respect safe areas and notch\n\n**Android (Material Design 3):**\n- Material navigation (bottom nav, navigation drawer)\n- Floating action buttons, material components\n- Roboto font, Material You dynamic colors\n- Touch feedback (ripple effects)\n- Respect system bars and gestures\n\n## Common Pitfalls to Avoid\n\n1. **Testing only on simulators** - Real devices show true performance\n2. **Ignoring platform conventions** - Users expect platform-specific patterns\n3. **No offline handling** - Network failures will happen\n4. **Poor memory management** - Leads to crashes and poor UX\n5. **Hardcoded credentials** - Security vulnerability\n6. **No accessibility** - Excludes 15%+ of users\n7. **Premature optimization** - Optimize based on metrics, not assumptions\n8. **Over-engineering** - Start simple, scale as needed\n9. **Skipping real device testing** - Simulators don't show battery\u002Fnetwork issues\n10. **Not respecting battery** - Background processing must be justified\n\n## Performance Budgets\n\n**Recommended Targets:**\n- **App size**: \u003C50MB initial download, \u003C200MB total\n- **Launch time**: \u003C2 seconds to interactive\n- **Screen load**: \u003C1 second for cached data\n- **Network request**: \u003C3 seconds for API calls\n- **Memory**: \u003C100MB for typical screens, \u003C200MB peak\n- **Battery**: \u003C5% drain per hour of active use\n- **Frame rate**: 60 FPS (16.67ms per frame)\n\n## Resources\n\n**Official Documentation:**\n- React Native: https:\u002F\u002Freactnative.dev\u002F\n- Flutter: https:\u002F\u002Fflutter.dev\u002F\n- iOS HIG: https:\u002F\u002Fdeveloper.apple.com\u002Fdesign\u002Fhuman-interface-guidelines\u002F\n- Material Design: https:\u002F\u002Fm3.material.io\u002F\n- OWASP Mobile: https:\u002F\u002Fowasp.org\u002Fwww-project-mobile-top-10\u002F\n\n**Tools & Testing:**\n- Detox E2E: https:\u002F\u002Fwix.github.io\u002FDetox\u002F\n- Appium: https:\u002F\u002Fappium.io\u002F\n- Fastlane: https:\u002F\u002Ffastlane.tools\u002F\n- Firebase: https:\u002F\u002Ffirebase.google.com\u002F\n\n**Community:**\n- React Native Directory: https:\u002F\u002Freactnative.directory\u002F\n- Pub.dev (Flutter packages): https:\u002F\u002Fpub.dev\u002F\n- Awesome React Native: https:\u002F\u002Fgithub.com\u002Fjondot\u002Fawesome-react-native\n- Awesome Flutter: https:\u002F\u002Fgithub.com\u002FSolido\u002Fawesome-flutter\n",{"name":5,"license":15,"version":44,"description":7,"argument-hint":45},"1.0.0","[platform] [feature]","main","281d4781645af618daed3d899b2ca2c04c1fe60c",".claude\u002Fskills\u002Fmobile-development","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone","https:\u002F\u002Fgithub.com\u002Fbkdev98","https:\u002F\u002Fquocs.com","Building polished mobile and web experiences.","2026-03-12 10:15:41",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add bkdev98\u002Fcautious-rotary-phone --skill \"ck:mobile-development\"",{"tool":60,"command":61},"bunx","bunx skills add bkdev98\u002Fcautious-rotary-phone --skill \"ck:mobile-development\"",{"tool":63,"command":64},"pnpm","pnpm dlx skills add bkdev98\u002Fcautious-rotary-phone --skill \"ck:mobile-development\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002FSKILL.md",true,[68,74,78,82,86,90,94],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fbrainstorming_methods.md","REFERENCE","参考文档",12065,"https:\u002F\u002Fgithub.com\u002Fstrmt7\u002Fai_skills_collection_benchmarked\u002Fblob\u002Fmain\u002Fincluded\u002Fskills\u002Fby-category\u002Fscience-research-data-analysis\u002Flatest-release-community\u002Fscientific-brainstorming\u002Freferences\u002Fbrainstorming_methods.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmobile-android.md",14033,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-android.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fmobile-best-practices.md",12672,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-best-practices.md",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fmobile-debugging.md",21605,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-debugging.md",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fmobile-frameworks.md",13999,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-frameworks.md",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fmobile-ios.md",10583,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-ios.md",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fmobile-mindset.md",16098,"https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmobile-development\u002Freferences\u002Fmobile-mindset.md",[99,130,150,184,210,228],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":39},"01M6DKK3NBKMHRVBX4XNCS7WG5","ck:web-testing","Web testing with Playwright, Vitest, k6. E2E\u002Funit\u002Fintegration\u002Fload\u002Fsecurity\u002Fvisual\u002Fa11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-testing\u002FSKILL.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,32,21,128,129],"testing","web","web testing","ck:web testing","security","gestures","automation","playwright","test","test automation","core","browser","integration","core web vitals","e2e","vitest","visual","type",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":39},"01M6DKJZMMJW529FDS878H3M8V","ck:web-frameworks","Build with Next.js (App Router, RSC, SSR, ISR), Turborepo monorepos. Use for React apps, server rendering, build optimization, caching strategies, shared dependencies.","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fweb-frameworks\u002FSKILL.md",[],[113,137,138,139,38,140,141,142,143,36,144,32,145,146,147,148,149,26,25,24],"web frameworks","frameworks","ck:web frameworks","ssr","framework","server","turborepo","Next.js","router","next","caching","strategies","shared",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":164,"publishedAt":39},"01M6DKJ88WV49J39MS714ZYSVC","ck:ui-styling","Style UIs with shadcn\u002Fui components (Radix UI + Tailwind CSS). Use for accessible components, themes, dark mode, responsive layouts, design systems, color customization.","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fui-styling\u002FSKILL.md",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[165,166,167,168,169,170,171,172,173,174,175,176,177,32,178,179,180,181,182,183],"ui styling","ui","styling","ck:ui styling","design","css","components","component","design systems","shadcn","Tailwind","customization","radix ui","Tailwind CSS","responsive","layout","systems","dark mode","style",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":193,"publishedAt":39},"01M6DKJ0NJ6AC3S2AKCJXVPDF0","ck:threejs","Build 3D web apps with Three.js (WebGL\u002FWebGPU). 556 searchable examples, 60 API classes, 20 use cases. Actions: create 3D scene, load model, add animation, implement physics, build VR\u002FXR. Topics: GLTF loader, PBR materials, particle effects, shadows, post-processing, compute shaders, TSL. Integrations: WebGPU, physics engines, spatial audio.","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fthreejs\u002FSKILL.md",[190],{"categoryNo":191,"categoryName":192,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口",[194,186,195,196,197,198,199,200,201,202,203,204,205,206,32,207,208,209,26,24],"threejs","gltf","implement","webgpu","create","examples","actions","api","Animation","3D","Audio","model","integrations","three","compute","physics",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":216,"publishedAt":39},"01M6DKH5P6MD48X0JW4MC2BYGY","ck:sequential-thinking","Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsequential-thinking\u002FSKILL.md",[],[217,218,219,220,221,222,223,224,225,32,226,227],"sequential thinking","thinking","ck:sequential thinking","planning","reasoning","verification","hypothesis","analysis","analyze","decomposition","problem",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":237,"publishedAt":39},"01M6DKGRQDXHFT07KCK450EY3P","ck:research","Research technical solutions, analyze architectures, gather requirements thoroughly. Use for technology evaluation, best practices research, solution design, scalability\u002Fsecurity\u002Fmaintainability analysis.","https:\u002F\u002Fgithub.com\u002Fbkdev98\u002Fcautious-rotary-phone\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fresearch\u002FSKILL.md",[234],{"categoryNo":235,"categoryName":236,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000021","资料检索与研究",[238,230,169,116,239,240,224,225,241,32,242,243,244,245],"research","best practices","Evaluation","technical","scalability","technology","requirements","maintainability"]