[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M783CZJG9NXT6WJ7KX1AXFN2":3,"skill-same:01M783CZJG9NXT6WJ7KX1AXFN2":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M783CZJG9NXT6WJ7KX1AXFN2","android-development",null,"Android development guidelines for Kotlin with clean architecture, MVI pattern, Material Design, and best practices for building robust mobile applications","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_mindrally_skills_android-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: android-development\ndescription: Android development guidelines for Kotlin with clean architecture, MVI pattern, Material Design, and best practices for building robust mobile applications\n---\n\n# Android Development Best Practices\n\n## General Kotlin Guidelines\n\n### Basic Principles\n- Use English for all code and documentation\n- Always declare variable and function types explicitly\n- Avoid the `any` type; create necessary custom types\n- Eliminate blank lines within function bodies\n\n### Naming Standards\n- **PascalCase**: Classes, interfaces, enums\n- **camelCase**: Variables, functions, methods\n- **underscores_case**: Files and directories\n- **UPPERCASE**: Environment variables, constants\n- Avoid magic numbers; define constants instead\n- Functions should start with action verbs\n- Boolean variables use prefixes: `isLoading`, `hasError`, `canDelete`\n\n### Function Design\n- Keep functions under 20 instructions with single responsibility\n- Use verb-based naming\n- Prefix boolean returns with `is`, `has`, or `can`\n- Prefix void returns with `execute`, `save`, `send`\n- Combat nesting through early returns, utility extraction, and higher-order functions\n- Use default parameters instead of null checks\n- Consolidate parameters into objects (RO-RO pattern)\n\n### Data and Classes\n- Employ data classes for data structures\n- Encapsulate primitives in composite types; validate internally\n- Favor immutability; use `val` for unchanging values\n- Follow SOLID principles; prefer composition over inheritance\n- Keep classes under 200 instructions, 10 public methods, 10 properties\n\n### Exception Handling\n- Reserve exceptions for unexpected errors\n- Catch exceptions only to fix anticipated issues or add context\n- Create custom exception types for domain errors\n\n## Android Architecture\n\n### Clean Architecture\n- Implement clean architecture with clear layer separation\n- Use repository pattern for data persistence and caching\n- Keep business logic in Use Cases or Interactors\n- Separate concerns between UI, domain, and data layers\n\n### Project Structure\n```\napp\u002F\n├── data\u002F           # Data sources, repositories, models\n├── domain\u002F         # Use cases, domain models, interfaces\n├── presentation\u002F   # UI components, ViewModels, state\n└── di\u002F             # Dependency injection modules\n```\n\n### MVI Pattern\n- Deploy MVI pattern for state and event management\n- ViewModels manage UI state as a single immutable state object\n- UI components observe state and render accordingly\n- Handle user intents\u002Fevents through a single entry point\n- Keep side effects predictable and traceable\n\n## UI Development\n\n### Navigation\n- Use Navigation Component for fragment and activity routing\n- Define navigation graph for app flow\n- Handle deep links through Navigation Component\n- Implement safe args for type-safe navigation arguments\n\n### Main Activity Structure\n- MainActivity manages primary navigation\n- Use BottomNavigationView for main destinations (Home, Profile, Settings, etc.)\n- Handle navigation state properly across configuration changes\n\n### View Binding and State\n- Use ViewBinding for type-safe view access\n- Use Flow or LiveData for UI state management\n- Observe state changes in lifecycle-aware manner\n- Handle loading, error, and success states consistently\n\n### UI Framework Preferences\n- Prefer XML layouts and Fragments over Jetpack Compose (unless Compose is specifically required)\n- Use ConstraintLayout for complex layouts\n- Apply Material 3 design guidelines\n- Follow responsive design practices for different screen sizes\n\n## Authentication Flow\n\nStructure authentication screens properly:\n1. Splash Screen - Initial app launch\n2. Login Screen - User authentication\n3. Register Screen - New user registration\n4. Forgot Password Screen - Password recovery\n5. Verify Email Screen - Email verification\n\n## Testing\n\n### Unit Testing\n- Follow Arrange-Act-Assert conventions\n- Test ViewModels, Use Cases, and Repositories\n- Use test doubles for dependencies\n- Achieve good coverage of business logic\n\n### UI Testing\n- Implement widget testing for UI components\n- Write integration tests for API modules\n- Test navigation flows\n- Use Espresso for instrumented tests\n\n## Best Practices\n\n### Lifecycle Management\n- Handle lifecycle events properly\n- Avoid memory leaks from improper lifecycle handling\n- Use lifecycle-aware components\n\n### Background Processing\n- Use Coroutines for async operations\n- Handle cancellation properly\n- Use WorkManager for deferrable background work\n\n### Dependency Injection\n- Use Hilt or Dagger for dependency injection\n- Scope dependencies appropriately\n- Keep DI configuration organized\n\n### Performance\n- Avoid work on the main thread\n- Optimize RecyclerView with DiffUtil\n- Use lazy loading for heavy resources\n- Profile and optimize memory usage\n","# Android Development Best Practices\n\n## General Kotlin Guidelines\n\n### Basic Principles\n- Use English for all code and documentation\n- Always declare variable and function types explicitly\n- Avoid the `any` type; create necessary custom types\n- Eliminate blank lines within function bodies\n\n### Naming Standards\n- **PascalCase**: Classes, interfaces, enums\n- **camelCase**: Variables, functions, methods\n- **underscores_case**: Files and directories\n- **UPPERCASE**: Environment variables, constants\n- Avoid magic numbers; define constants instead\n- Functions should start with action verbs\n- Boolean variables use prefixes: `isLoading`, `hasError`, `canDelete`\n\n### Function Design\n- Keep functions under 20 instructions with single responsibility\n- Use verb-based naming\n- Prefix boolean returns with `is`, `has`, or `can`\n- Prefix void returns with `execute`, `save`, `send`\n- Combat nesting through early returns, utility extraction, and higher-order functions\n- Use default parameters instead of null checks\n- Consolidate parameters into objects (RO-RO pattern)\n\n### Data and Classes\n- Employ data classes for data structures\n- Encapsulate primitives in composite types; validate internally\n- Favor immutability; use `val` for unchanging values\n- Follow SOLID principles; prefer composition over inheritance\n- Keep classes under 200 instructions, 10 public methods, 10 properties\n\n### Exception Handling\n- Reserve exceptions for unexpected errors\n- Catch exceptions only to fix anticipated issues or add context\n- Create custom exception types for domain errors\n\n## Android Architecture\n\n### Clean Architecture\n- Implement clean architecture with clear layer separation\n- Use repository pattern for data persistence and caching\n- Keep business logic in Use Cases or Interactors\n- Separate concerns between UI, domain, and data layers\n\n### Project Structure\n```\napp\u002F\n├── data\u002F           # Data sources, repositories, models\n├── domain\u002F         # Use cases, domain models, interfaces\n├── presentation\u002F   # UI components, ViewModels, state\n└── di\u002F             # Dependency injection modules\n```\n\n### MVI Pattern\n- Deploy MVI pattern for state and event management\n- ViewModels manage UI state as a single immutable state object\n- UI components observe state and render accordingly\n- Handle user intents\u002Fevents through a single entry point\n- Keep side effects predictable and traceable\n\n## UI Development\n\n### Navigation\n- Use Navigation Component for fragment and activity routing\n- Define navigation graph for app flow\n- Handle deep links through Navigation Component\n- Implement safe args for type-safe navigation arguments\n\n### Main Activity Structure\n- MainActivity manages primary navigation\n- Use BottomNavigationView for main destinations (Home, Profile, Settings, etc.)\n- Handle navigation state properly across configuration changes\n\n### View Binding and State\n- Use ViewBinding for type-safe view access\n- Use Flow or LiveData for UI state management\n- Observe state changes in lifecycle-aware manner\n- Handle loading, error, and success states consistently\n\n### UI Framework Preferences\n- Prefer XML layouts and Fragments over Jetpack Compose (unless Compose is specifically required)\n- Use ConstraintLayout for complex layouts\n- Apply Material 3 design guidelines\n- Follow responsive design practices for different screen sizes\n\n## Authentication Flow\n\nStructure authentication screens properly:\n1. Splash Screen - Initial app launch\n2. Login Screen - User authentication\n3. Register Screen - New user registration\n4. Forgot Password Screen - Password recovery\n5. Verify Email Screen - Email verification\n\n## Testing\n\n### Unit Testing\n- Follow Arrange-Act-Assert conventions\n- Test ViewModels, Use Cases, and Repositories\n- Use test doubles for dependencies\n- Achieve good coverage of business logic\n\n### UI Testing\n- Implement widget testing for UI components\n- Write integration tests for API modules\n- Test navigation flows\n- Use Espresso for instrumented tests\n\n## Best Practices\n\n### Lifecycle Management\n- Handle lifecycle events properly\n- Avoid memory leaks from improper lifecycle handling\n- Use lifecycle-aware components\n\n### Background Processing\n- Use Coroutines for async operations\n- Handle cancellation properly\n- Use WorkManager for deferrable background work\n\n### Dependency Injection\n- Use Hilt or Dagger for dependency injection\n- Scope dependencies appropriately\n- Keep DI configuration organized\n\n### Performance\n- Avoid work on the main thread\n- Optimize RecyclerView with DiffUtil\n- Use lazy loading for heavy resources\n- Profile and optimize memory usage\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fskills_sh\u002Fs\u002Fskills-sh_mindrally_skills_android-development",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill android-development",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill android-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill android-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fskills_sh\u002Fs\u002Fskills-sh_mindrally_skills_android-development\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"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":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]