[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T48E2CQK3XE17QSCS39Z2":3,"skill-same:01M79T48E2CQK3XE17QSCS39Z2":53},{"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":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79T48E2CQK3XE17QSCS39Z2","android-architect",null,"Architect-level Android guidance — Compose versus View system boundaries, lifecycle and configuration changes, state holders and unidirectional data flow, coroutine and work scheduling discipline, and the process-death and permission realities of the platform. Use for Android apps.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fplatforms-architect\u002Fandroid-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: android-architect\ndescription: Architect-level Android guidance — Compose versus View system boundaries, lifecycle and configuration changes, state holders and unidirectional data flow, coroutine and work scheduling discipline, and the process-death and permission realities of the platform. Use for Android apps.\nlicense: MIT\ncompatibility: Android 8+\u002FAPI 26+; Kotlin; Jetpack Compose\nmetadata:\n  crusor-domain: mobile-architect\n  crusor-path: mobile-architect\u002Fplatforms-architect\u002Fandroid-architect\n  crusor-origin: original\n  crusor-sources: \"developer.android.com\u002Fguide; developer.android.com\u002Fjetpack\u002Fcompose; developer.android.com\u002Ftopic\u002Farchitecture\"\n  crusor-triggers: \"android, kotlin, jetpack compose, viewmodel, gradle android, android app, coroutines\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Android Architect\n\nAndroid gives you **a process that can die at any time and a very wide device\nrange**. Architecture is about surviving both.\n\n## When to use\n\n- Building or reviewing an Android app.\n- Choosing Compose vs the View system, or migrating.\n- Lifecycle, background work or state loss problems.\n\n## When NOT to use\n\n- Cross-platform apps where the shared layer dominates.\n\n## Decision 1 — Compose vs Views\n\n| Need | Choose |\n|---|---|\n| new UI, most screens | Jetpack Compose |\n| legacy screens, complex custom views | View system, migrated incrementally |\n| interop | `ComposeView` \u002F `AndroidView` at the seam |\n\n- Migrate screen by screen; a half-migrated app is expected, an unplanned one is\n  not.\n- Compose state hoisting: UI is a function of state; state lives in a holder,\n  not in composables.\n- No business logic in composables — they must be previewable and testable.\n\n## Decision 2 — Layering\n\n```\nui\u002F (compose screens, viewmodels)\n  domain\u002F (use-cases, entities — no Android imports)\n    data\u002F (repositories, Room, Retrofit)\n      framework (DI modules, platform adapters)\n```\n\n- ViewModel holds UI state and survives configuration change — not process\n  death.\n- One-shot effects (navigation, snackbar) are events, not state that replays.\n- DI (Hilt\u002FKoin) wires the graph; screens never construct dependencies.\n\n## Decision 3 — Lifecycle and process death\n\n- Configuration changes recreate activities; state must survive or be restored.\n- `SavedStateHandle`\u002F`SavedStateRegistry` for anything the user typed.\n- Background work: WorkManager with constraints and backoff — never a `Thread`\n  or an alarm.\n- Doze and app-standby will defer your timers; design for late, not exact.\n\n## Decision 4 — Concurrency\n\n- Coroutines with structured scopes: `viewModelScope`, `lifecycleScope`;\n  cancellation is automatic when the owner dies.\n- Dispatchers explicit: `IO` for disk\u002Fnetwork, `Default` for CPU, `Main` only\n  for UI.\n- Flows for streams; `StateFlow` for UI state; one source of truth per screen.\n- No blocking calls on the main thread; StrictMode on in debug.\n\n## Decision 5 — Platform realities\n\n- Permissions: request in context, handle permanent denial with a path to\n  settings.\n- Storage scoped storage rules; no writes outside app directories without SAF.\n- Back navigation and predictive back gestures handled by the nav graph.\n- Device fragmentation: test on API floor, a mid-tier device and a foldable\n  profile.\n\n## Failure modes at scale\n\n- God ViewModels with 40 fields and mixed responsibilities.\n- State living in composables, lost on rotation.\n- WorkManager chains that run forever because they are never cancelled.\n- Two sources of truth (Room + in-memory cache) drifting apart.\n- Blocking the main thread with JSON parsing on large payloads.\n\n## Verification receipts\n\n1. Rotation test on every stateful screen.\n2. Process-death restore test (developer option \"don't keep activities\").\n3. StrictMode clean in debug; no main-thread disk\u002Fnetwork.\n4. Offline journey test with WorkManager retry.\n5. Baseline profile \u002F startup time and jank trace on a mid-tier device.\n","# Android Architect\n\nAndroid gives you **a process that can die at any time and a very wide device\nrange**. Architecture is about surviving both.\n\n## When to use\n\n- Building or reviewing an Android app.\n- Choosing Compose vs the View system, or migrating.\n- Lifecycle, background work or state loss problems.\n\n## When NOT to use\n\n- Cross-platform apps where the shared layer dominates.\n\n## Decision 1 — Compose vs Views\n\n| Need | Choose |\n|---|---|\n| new UI, most screens | Jetpack Compose |\n| legacy screens, complex custom views | View system, migrated incrementally |\n| interop | `ComposeView` \u002F `AndroidView` at the seam |\n\n- Migrate screen by screen; a half-migrated app is expected, an unplanned one is\n  not.\n- Compose state hoisting: UI is a function of state; state lives in a holder,\n  not in composables.\n- No business logic in composables — they must be previewable and testable.\n\n## Decision 2 — Layering\n\n```\nui\u002F (compose screens, viewmodels)\n  domain\u002F (use-cases, entities — no Android imports)\n    data\u002F (repositories, Room, Retrofit)\n      framework (DI modules, platform adapters)\n```\n\n- ViewModel holds UI state and survives configuration change — not process\n  death.\n- One-shot effects (navigation, snackbar) are events, not state that replays.\n- DI (Hilt\u002FKoin) wires the graph; screens never construct dependencies.\n\n## Decision 3 — Lifecycle and process death\n\n- Configuration changes recreate activities; state must survive or be restored.\n- `SavedStateHandle`\u002F`SavedStateRegistry` for anything the user typed.\n- Background work: WorkManager with constraints and backoff — never a `Thread`\n  or an alarm.\n- Doze and app-standby will defer your timers; design for late, not exact.\n\n## Decision 4 — Concurrency\n\n- Coroutines with structured scopes: `viewModelScope`, `lifecycleScope`;\n  cancellation is automatic when the owner dies.\n- Dispatchers explicit: `IO` for disk\u002Fnetwork, `Default` for CPU, `Main` only\n  for UI.\n- Flows for streams; `StateFlow` for UI state; one source of truth per screen.\n- No blocking calls on the main thread; StrictMode on in debug.\n\n## Decision 5 — Platform realities\n\n- Permissions: request in context, handle permanent denial with a path to\n  settings.\n- Storage scoped storage rules; no writes outside app directories without SAF.\n- Back navigation and predictive back gestures handled by the nav graph.\n- Device fragmentation: test on API floor, a mid-tier device and a foldable\n  profile.\n\n## Failure modes at scale\n\n- God ViewModels with 40 fields and mixed responsibilities.\n- State living in composables, lost on rotation.\n- WorkManager chains that run forever because they are never cancelled.\n- Two sources of truth (Room + in-memory cache) drifting apart.\n- Blocking the main thread with JSON parsing on large payloads.\n\n## Verification receipts\n\n1. Rotation test on every stateful screen.\n2. Process-death restore test (developer option \"don't keep activities\").\n3. StrictMode clean in debug; no main-thread disk\u002Fnetwork.\n4. Offline journey test with WorkManager retry.\n5. Baseline profile \u002F startup time and jank trace on a mid-tier device.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"mobile-architect\u002Fplatforms-architect\u002Fandroid-architect","mobile-architect","original","developer.android.com\u002Fguide; developer.android.com\u002Fjetpack\u002Fcompose; developer.android.com\u002Ftopic\u002Farchitecture","android, kotlin, jetpack compose, viewmodel, gradle android, android app, coroutines","2026-10-30","Android 8+\u002FAPI 26+; Kotlin; Jetpack Compose","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fmobile-architect\u002Fplatforms-architect\u002Fandroid-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill android-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill android-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill android-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fplatforms-architect\u002Fandroid-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"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":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]