[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79HTMHAWFSMF985PPAJN43Q":3,"skill-same:01M79HTMHAWFSMF985PPAJN43Q":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},"01M79HTMHAWFSMF985PPAJN43Q","android-module-structure",null,"Module layout, dependency rules, and Gradle convention plugins for Android and Kotlin Multiplatform (KMP) projects. Use this skill whenever setting up a new Android\u002FKMP project, deciding where a new module should live, asking \"how should I structure this\", creating a new feature module, adding a core submodule, configuring Gradle convention plugins, working with version catalogs, or making any decision about project-level architecture. Trigger on phrases like \"set up the project\", \"add a module\", \"create a feature\", \"how should I structure\", \"project structure\", \"convention plugin\", \"build-logic\", or \"where does X live\".","cosmictaserdev-creator\u002FConvx","cosmictaserdev-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F278399831?v=4","01M79HSPX02ZNGBSR0HA77WMX1","Aryan sharma","01M79HSPY09R4SAB7DAFCQWSKV",1420,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fandroid-module-structure\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: android-module-structure\ndescription: Module layout, dependency rules, and Gradle convention plugins for Android and Kotlin Multiplatform (KMP) projects. Use this skill whenever setting up a new Android\u002FKMP project, deciding where a new module should live, asking \"how should I structure this\", creating a new feature module, adding a core submodule, configuring Gradle convention plugins, working with version catalogs, or making any decision about project-level architecture. Trigger on phrases like \"set up the project\", \"add a module\", \"create a feature\", \"how should I structure\", \"project structure\", \"convention plugin\", \"build-logic\", or \"where does X live\".\n---\n \n# Android \u002F KMP Module Structure\n \n## Core Philosophy\n \n- **Feature-layered modularization**: split by feature first, then by layer within each feature.\n- **Clean Architecture layers**: `presentation` → `domain` ← `data`. Domain is innermost and depends on nothing.\n- **Code lives in a feature module unless it is needed by more than one feature** — then it moves to the appropriate `core` submodule.\n- Features **never depend on each other**. Cross-feature shared data belongs in `core:domain` (domain models) or `core:presentation` (shared composables\u002FUI logic), not in the owning feature.\n \n---\n \n## Module Layout\n \n```\n:app\n:build-logic                    ← Gradle convention plugins\n:core:domain                    ← Shared domain models, repository interfaces, error types, Result\n:core:data                      ← Shared data logic, Ktor HttpClient factory, shared DB schemas\u002FDAOs\n:core:presentation              ← Shared UI utilities (ObserveAsEvents, UiText, etc.)\n:core:design-system             ← Reusable Compose components, colors, theme, typography\n:feature:\u003Cname>:domain          ← Feature-specific domain models, repo interfaces, error types\n:feature:\u003Cname>:data            ← Repo implementations, DTOs, mappers, Room DAOs\n:feature:\u003Cname>:presentation    ← ViewModel, screen composables, state, actions, events\n```\n \nFor standalone, self-contained concerns that involve meaningful complexity (multiple classes, configuration, or a non-trivial API surface), create a dedicated module under `:core` (e.g., `:core:location`, `:core:analytics`). Do not create a separate module for a single class or a trivial utility — that belongs in an existing `core` module instead.\n\nA shared Room database is a good candidate for a dedicated `:core:database` module. It contains the `@Database` class, all entity definitions, all DAOs, and migrations. Feature modules that need DB access depend on `:core:database` directly, while features that don't need it remain decoupled.\n \n---\n \n## Dependency Rules\n \n| Layer | May depend on |\n|---|---|\n| `presentation` | `domain` (own feature), `core:domain`, `core:presentation`, `core:design-system` |\n| `data` | `domain` (own feature), `core:domain`, `core:data` |\n| `domain` | `core:domain` only — never `data` or `presentation` |\n| `:app` | everything (wires all modules) |\n\n**Every** layer and module may access `core:domain`.\n \n---\n \n## Convention Plugins (`:build-logic`)\n \nDefine a convention plugin for every non-trivial Gradle config:\n \n| Plugin | Purpose |\n|---|---|\n| `android-application` | App module config (applicationId, versionCode, etc.) |\n| `android-library` | Base Android library config |\n| `android-feature` | Android library + Compose + Koin + shared feature deps bundled |\n| `domain-module` | Pure Kotlin\u002FKMP module, no Android deps |\n| `compose` | Compose compiler + BOM |\n| `koin` | Koin dependency block |\n| `ktor` | Ktor client + serialization |\n| `room` | Room + KSP config |\n| `kotlinx-serialization` | KotlinX Serialization plugin + dep |\n \nUse **version catalogs** (`libs.versions.toml`) for all dependency and version management. No hardcoded versions in build files.\n \n---\n \n## Key Libraries\n \n| Concern | Library |\n|---|---|\n| DI | Koin |\n| Networking | Ktor Client |\n| Local DB | Room |\n| Preferences | DataStore |\n| Navigation | Compose Navigation (type-safe) |\n| Serialization | KotlinX Serialization (Ktor + Nav routes) |\n| Image loading | Coil |\n| Logging | Kermit |\n| Async | Coroutines + Flow |\n| Background tasks | WorkManager |\n| Secrets | `local.properties` + `BuildConfig` (Android); `BuildKonfig` (KMP) |\n| Testing | JUnit5, Turbine, AssertK, `kotlinx-coroutines-test` |\n| UI testing | `ComposeTestRule` |\n \n---\n \n## Checklist: Adding a New Feature Module\n \n- [ ] Create `:feature:\u003Cname>:domain`, `:feature:\u003Cname>:data`, `:feature:\u003Cname>:presentation` modules\n- [ ] Apply appropriate convention plugins to each module (`domain-module`, `android-library`\u002F`android-feature`)\n- [ ] Verify no cross-feature dependencies are introduced\n- [ ] If logic is shared across 2+ features, extract to the appropriate `core` submodule","# Android \u002F KMP Module Structure\n \n## Core Philosophy\n \n- **Feature-layered modularization**: split by feature first, then by layer within each feature.\n- **Clean Architecture layers**: `presentation` → `domain` ← `data`. Domain is innermost and depends on nothing.\n- **Code lives in a feature module unless it is needed by more than one feature** — then it moves to the appropriate `core` submodule.\n- Features **never depend on each other**. Cross-feature shared data belongs in `core:domain` (domain models) or `core:presentation` (shared composables\u002FUI logic), not in the owning feature.\n \n---\n \n## Module Layout\n \n```\n:app\n:build-logic                    ← Gradle convention plugins\n:core:domain                    ← Shared domain models, repository interfaces, error types, Result\n:core:data                      ← Shared data logic, Ktor HttpClient factory, shared DB schemas\u002FDAOs\n:core:presentation              ← Shared UI utilities (ObserveAsEvents, UiText, etc.)\n:core:design-system             ← Reusable Compose components, colors, theme, typography\n:feature:\u003Cname>:domain          ← Feature-specific domain models, repo interfaces, error types\n:feature:\u003Cname>:data            ← Repo implementations, DTOs, mappers, Room DAOs\n:feature:\u003Cname>:presentation    ← ViewModel, screen composables, state, actions, events\n```\n \nFor standalone, self-contained concerns that involve meaningful complexity (multiple classes, configuration, or a non-trivial API surface), create a dedicated module under `:core` (e.g., `:core:location`, `:core:analytics`). Do not create a separate module for a single class or a trivial utility — that belongs in an existing `core` module instead.\n\nA shared Room database is a good candidate for a dedicated `:core:database` module. It contains the `@Database` class, all entity definitions, all DAOs, and migrations. Feature modules that need DB access depend on `:core:database` directly, while features that don't need it remain decoupled.\n \n---\n \n## Dependency Rules\n \n| Layer | May depend on |\n|---|---|\n| `presentation` | `domain` (own feature), `core:domain`, `core:presentation`, `core:design-system` |\n| `data` | `domain` (own feature), `core:domain`, `core:data` |\n| `domain` | `core:domain` only — never `data` or `presentation` |\n| `:app` | everything (wires all modules) |\n\n**Every** layer and module may access `core:domain`.\n \n---\n \n## Convention Plugins (`:build-logic`)\n \nDefine a convention plugin for every non-trivial Gradle config:\n \n| Plugin | Purpose |\n|---|---|\n| `android-application` | App module config (applicationId, versionCode, etc.) |\n| `android-library` | Base Android library config |\n| `android-feature` | Android library + Compose + Koin + shared feature deps bundled |\n| `domain-module` | Pure Kotlin\u002FKMP module, no Android deps |\n| `compose` | Compose compiler + BOM |\n| `koin` | Koin dependency block |\n| `ktor` | Ktor client + serialization |\n| `room` | Room + KSP config |\n| `kotlinx-serialization` | KotlinX Serialization plugin + dep |\n \nUse **version catalogs** (`libs.versions.toml`) for all dependency and version management. No hardcoded versions in build files.\n \n---\n \n## Key Libraries\n \n| Concern | Library |\n|---|---|\n| DI | Koin |\n| Networking | Ktor Client |\n| Local DB | Room |\n| Preferences | DataStore |\n| Navigation | Compose Navigation (type-safe) |\n| Serialization | KotlinX Serialization (Ktor + Nav routes) |\n| Image loading | Coil |\n| Logging | Kermit |\n| Async | Coroutines + Flow |\n| Background tasks | WorkManager |\n| Secrets | `local.properties` + `BuildConfig` (Android); `BuildKonfig` (KMP) |\n| Testing | JUnit5, Turbine, AssertK, `kotlinx-coroutines-test` |\n| UI testing | `ComposeTestRule` |\n \n---\n \n## Checklist: Adding a New Feature Module\n \n- [ ] Create `:feature:\u003Cname>:domain`, `:feature:\u003Cname>:data`, `:feature:\u003Cname>:presentation` modules\n- [ ] Apply appropriate convention plugins to each module (`domain-module`, `android-library`\u002F`android-feature`)\n- [ ] Verify no cross-feature dependencies are introduced\n- [ ] If logic is shared across 2+ features, extract to the appropriate `core` submodule",{"name":5,"description":7},"main","f3dd4f71d603f8eb5828696fa7bab18c6172fb55","contributor\u002Fskills\u002Fandroid-module-structure",82,"https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx","https:\u002F\u002Fcosmictaser.de5.net","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator","Android developer who do side quest on backend and other things 😗","2026-11-14 01:39:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add cosmictaserdev-creator\u002FConvx --skill android-module-structure",{"tool":39,"command":40},"bunx","bunx skills add cosmictaserdev-creator\u002FConvx --skill android-module-structure",{"tool":42,"command":43},"pnpm","pnpm dlx skills add cosmictaserdev-creator\u002FConvx --skill android-module-structure","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fandroid-module-structure\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},"01M79HYWSY9H6DNW14YM28D5NH","review-animations","Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Freview-animations\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},"01M79HYS6N1DJE11T0B8HZKHQP","prototype","Build multiple genuinely different versions of a UI piece you describe, rendered behind a visual picker so you can flip through them live and promote the one that feels right. Only runs when explicitly invoked; it does not trigger on its own.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fprototype\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},"01M79HYNBQ5NK2STBY5E1JMDZS","pick-ui-library","Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fpick-ui-library\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},"01M79HYG5N018C9KB5SZAJ03VK","improve-animations","Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to \"improve the animations\", \"audit the motion\", \"make this app feel better\", or wants a roadmap of animation fixes rather than a review of a single diff.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fimprove-animations\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},"01M79HYD3F6PR68BVEK4NYQT66","grilling","Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fgrilling\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},"01M79HYAYH7PR194SMGTP7NZWZ","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002Fcosmictaserdev-creator\u002FConvx\u002Fblob\u002Fmain\u002Fcontributor\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[]]