[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T5Q2AC2V03DW4XS1FQQ7H":3,"skill-same:01M79T5Q2AC2V03DW4XS1FQQ7H":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},"01M79T5Q2AC2V03DW4XS1FQQ7H","mobile-modularization-architect",null,"Architect-level app modularisation — module boundaries by feature and layer, dependency rules and API surfaces, build-time impact, dynamic feature delivery, and the ownership model that makes modules worth their cost. Use when an app has outgrown a single module.","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\u002Fmobile-modularization-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mobile-modularization-architect\ndescription: Architect-level app modularisation — module boundaries by feature and layer, dependency rules and API surfaces, build-time impact, dynamic feature delivery, and the ownership model that makes modules worth their cost. Use when an app has outgrown a single module.\nlicense: MIT\ncompatibility: Gradle modules, Xcode frameworks\u002FSwift packages, Bazel\nmetadata:\n  crusor-domain: mobile-architect\n  crusor-path: mobile-architect\u002Fplatforms-architect\u002Fmobile-modularization-architect\n  crusor-origin: original\n  crusor-sources: \"developer.android.com\u002Ftopic\u002Fmodularization; developer.apple.com\u002Fdocumentation\u002Fxcode\u002Fcreating-a-multiplatform-framework; developer.android.com\u002Fguide\u002Fplaycore\u002Ffeature-delivery\"\n  crusor-triggers: \"modularization, gradle modules, swift packages, xcode framework, dynamic feature, module boundaries, build times, dependency graph, modularize, modularise, split into modules, feature module\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Mobile Modularisation Architect\n\nModules buy **boundaries and build parallelism**, at the cost of ceremony. Split for a\nreason; every module has an owner and a tax.\n\n## When to use\n\n- Build times over ~5 minutes on the main path.\n- Multiple teams editing the same module daily.\n- Features that should ship independently or on demand.\n\n## When NOT to use\n\n- A small app with one team — modules add configuration and indirection for nothing.\n- Splitting before you have a dependency problem; measurement comes first.\n\n## Decision 1 — Boundary type\n\n| Split by | Use when |\n|---|---|\n| feature | teams own vertical slices |\n| layer (data\u002Fdomain\u002Fui) | strict dependency direction matters |\n| library\u002FSDK | reused across apps |\n| dynamic feature | on-demand install, large optional flows |\n\n- Feature modules with internal layers beat layer-per-module-everywhere at small scale.\n- One module per screen is over-fragmentation; one module per bounded feature is the\n  usual sweet spot.\n\n## Decision 2 — Dependency rules\n\n```\napp → feature-*  →  core-ui \u002F core-domain\n                     ↑\n             feature-* never depends on feature-*\n```\n\n- Features communicate through the app module or a shared domain API, not by direct\n  dependency.\n- Enforce with build tooling (`implementation` vs `api`, or a lint rule); documented\n  rules decay in a quarter.\n- Public surface = a small API module per feature; internals stay `internal`.\n\n## Decision 3 — Build performance\n\n- Measure clean and incremental builds before and after each split.\n- Gradle configuration cache and Kotlin incremental compilation matter more than module\n  count.\n- iOS: Swift packages and frameworks parallelise better than one target with folders.\n- A split that increases build time is a net loss — revert it.\n\n## Decision 4 — Dynamic delivery\n\n- Dynamic features for large, rarely used flows (onboarding extras, editor tools).\n- Every dynamic module adds install-time state and failure modes; test on low-end\n  devices and slow networks.\n- Base module size is the download metric users feel; keep it lean.\n\n## Decision 5 — Ownership\n\n- Each module has an owner team and a CODEOWNERS entry; orphan modules are deleted.\n- Module boundaries are architecture: changes go through review.\n- Document the graph; a diagram nobody updates is fiction — generate it from the build.\n\n## Failure modes at scale\n\n- 80 modules, 9-minute builds, no ownership.\n- Features depending on each other's internals; boundaries are decorative.\n- One \"core\" module that everything imports and everyone edits.\n- Dynamic feature that breaks on first launch for 2% of devices.\n- Modules split by layer only; every feature change touches five modules.\n\n## Verification receipts\n\n1. Module graph generated from the build, with ownership.\n2. Clean and incremental build times before and after the split.\n3. Dependency rule violation caught by tooling in a test PR.\n4. Dynamic feature installed and exercised on a slow network.\n5. Base app download size tracked per release.\n","# Mobile Modularisation Architect\n\nModules buy **boundaries and build parallelism**, at the cost of ceremony. Split for a\nreason; every module has an owner and a tax.\n\n## When to use\n\n- Build times over ~5 minutes on the main path.\n- Multiple teams editing the same module daily.\n- Features that should ship independently or on demand.\n\n## When NOT to use\n\n- A small app with one team — modules add configuration and indirection for nothing.\n- Splitting before you have a dependency problem; measurement comes first.\n\n## Decision 1 — Boundary type\n\n| Split by | Use when |\n|---|---|\n| feature | teams own vertical slices |\n| layer (data\u002Fdomain\u002Fui) | strict dependency direction matters |\n| library\u002FSDK | reused across apps |\n| dynamic feature | on-demand install, large optional flows |\n\n- Feature modules with internal layers beat layer-per-module-everywhere at small scale.\n- One module per screen is over-fragmentation; one module per bounded feature is the\n  usual sweet spot.\n\n## Decision 2 — Dependency rules\n\n```\napp → feature-*  →  core-ui \u002F core-domain\n                     ↑\n             feature-* never depends on feature-*\n```\n\n- Features communicate through the app module or a shared domain API, not by direct\n  dependency.\n- Enforce with build tooling (`implementation` vs `api`, or a lint rule); documented\n  rules decay in a quarter.\n- Public surface = a small API module per feature; internals stay `internal`.\n\n## Decision 3 — Build performance\n\n- Measure clean and incremental builds before and after each split.\n- Gradle configuration cache and Kotlin incremental compilation matter more than module\n  count.\n- iOS: Swift packages and frameworks parallelise better than one target with folders.\n- A split that increases build time is a net loss — revert it.\n\n## Decision 4 — Dynamic delivery\n\n- Dynamic features for large, rarely used flows (onboarding extras, editor tools).\n- Every dynamic module adds install-time state and failure modes; test on low-end\n  devices and slow networks.\n- Base module size is the download metric users feel; keep it lean.\n\n## Decision 5 — Ownership\n\n- Each module has an owner team and a CODEOWNERS entry; orphan modules are deleted.\n- Module boundaries are architecture: changes go through review.\n- Document the graph; a diagram nobody updates is fiction — generate it from the build.\n\n## Failure modes at scale\n\n- 80 modules, 9-minute builds, no ownership.\n- Features depending on each other's internals; boundaries are decorative.\n- One \"core\" module that everything imports and everyone edits.\n- Dynamic feature that breaks on first launch for 2% of devices.\n- Modules split by layer only; every feature change touches five modules.\n\n## Verification receipts\n\n1. Module graph generated from the build, with ownership.\n2. Clean and incremental build times before and after the split.\n3. Dependency rule violation caught by tooling in a test PR.\n4. Dynamic feature installed and exercised on a slow network.\n5. Base app download size tracked per release.\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\u002Fmobile-modularization-architect","mobile-architect","original","developer.android.com\u002Ftopic\u002Fmodularization; developer.apple.com\u002Fdocumentation\u002Fxcode\u002Fcreating-a-multiplatform-framework; developer.android.com\u002Fguide\u002Fplaycore\u002Ffeature-delivery","modularization, gradle modules, swift packages, xcode framework, dynamic feature, module boundaries, build times, dependency graph, modularize, modularise, split into modules, feature module","2026-10-30","Gradle modules, Xcode frameworks\u002FSwift packages, Bazel","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fmobile-architect\u002Fplatforms-architect\u002Fmobile-modularization-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 mobile-modularization-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill mobile-modularization-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill mobile-modularization-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fplatforms-architect\u002Fmobile-modularization-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",[],[]]