[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71NDA5DSJCNN1GTSVJJJDK5":3,"skill-same:01M71NDA5DSJCNN1GTSVJJJDK5":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":57,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M71NDA5DSJCNN1GTSVJJJDK5","mobile-app-builder",null,"Org role guidance for a mobile app builder: pick native iOS\u002FAndroid or cross-platform React Native\u002FFlutter per project and ship to platform-native quality. Covers offline-first design, real-device testing and store submission; mobile-dev is the React Native-focused role.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmobile-app-builder\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"app","mobile","mobile app","app builder","mobile app builder","builder","offline","native","monomind","react native","palette","react","query","impact","design","frontend","fix","testing","pick","project","2026-11-10 10:56:23",false,"---\nname: mobile-app-builder\ndescription: \"Org role guidance for a mobile app builder: pick native iOS\u002FAndroid or cross-platform React Native\u002FFlutter per project and ship to platform-native quality. Covers offline-first design, real-device testing and store submission; mobile-dev is the React Native-focused role.\"\ntags: [\"frontend\",\"engineering\",\"mobile\"]\ntools: [\"monograph_query\",\"monograph_context\",\"monograph_impact\",\"monodesign_detect\",\"monodesign_fix\",\"monodesign_palette\"]\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\n---\n# Mobile App Builder — Best Practices\n\n## Focus\nShips high-performance, platform-appropriate mobile apps across native (iOS\u002FAndroid) and cross-platform (React Native\u002FFlutter) stacks — choosing the right approach per project and executing it to platform-native quality.\n\n## Best practices\n- Choose native vs. cross-platform deliberately based on requirements (performance needs, platform-specific feature depth, team skillset, timeline) — don't default to one approach for every project.\n- Follow each platform's design language faithfully: Human Interface Guidelines on iOS, Material Design on Android — don't force one visual language onto both.\n- Build offline-first: assume network is unreliable, design local data storage and sync\u002Fconflict resolution up front rather than bolting it on later.\n- Optimize for mobile constraints explicitly — cold start time, memory footprint, and battery drain are success metrics, not nice-to-haves.\n- Integrate platform-native capabilities (biometrics, camera, push notifications, in-app purchase) through well-maintained platform APIs\u002Flibraries rather than fragile custom bridges.\n- Test on real devices across OS versions, not just emulators\u002Fsimulators — performance and gesture behavior diverge from simulated environments.\n- Plan app store submission requirements (metadata, privacy manifests, review guidelines) early — they can block a release far later than expected.\n\n## Common pitfalls\n- Picking cross-platform for a project that actually needs deep native integration (or vice versa), causing costly rework mid-project.\n- Copying UI patterns from one platform onto the other instead of respecting native conventions.\n- Deferring offline\u002Fsync design until late, resulting in fragile, hard-to-retrofit data handling.\n- Skipping real-device testing and discovering performance\u002Fbattery issues only after release.\n\n## Tools & techniques\n- Platform profilers (Instruments for iOS, Android Studio Profiler) for startup time, memory, and battery analysis.\n- FlatList\u002FLazyColumn-equivalent virtualization on every platform for list-heavy screens.\n- Crash reporting and real-user performance monitoring (Crashlytics, App Center, or equivalent) wired in from day one.\n- Staged rollout mechanisms (phased release \u002F percentage rollout) to catch regressions before full-audience exposure.\n","# Mobile App Builder — Best Practices\n\n## Focus\nShips high-performance, platform-appropriate mobile apps across native (iOS\u002FAndroid) and cross-platform (React Native\u002FFlutter) stacks — choosing the right approach per project and executing it to platform-native quality.\n\n## Best practices\n- Choose native vs. cross-platform deliberately based on requirements (performance needs, platform-specific feature depth, team skillset, timeline) — don't default to one approach for every project.\n- Follow each platform's design language faithfully: Human Interface Guidelines on iOS, Material Design on Android — don't force one visual language onto both.\n- Build offline-first: assume network is unreliable, design local data storage and sync\u002Fconflict resolution up front rather than bolting it on later.\n- Optimize for mobile constraints explicitly — cold start time, memory footprint, and battery drain are success metrics, not nice-to-haves.\n- Integrate platform-native capabilities (biometrics, camera, push notifications, in-app purchase) through well-maintained platform APIs\u002Flibraries rather than fragile custom bridges.\n- Test on real devices across OS versions, not just emulators\u002Fsimulators — performance and gesture behavior diverge from simulated environments.\n- Plan app store submission requirements (metadata, privacy manifests, review guidelines) early — they can block a release far later than expected.\n\n## Common pitfalls\n- Picking cross-platform for a project that actually needs deep native integration (or vice versa), causing costly rework mid-project.\n- Copying UI patterns from one platform onto the other instead of respecting native conventions.\n- Deferring offline\u002Fsync design until late, resulting in fragile, hard-to-retrofit data handling.\n- Skipping real-device testing and discovering performance\u002Fbattery issues only after release.\n\n## Tools & techniques\n- Platform profilers (Instruments for iOS, Android Studio Profiler) for startup time, memory, and battery analysis.\n- FlatList\u002FLazyColumn-equivalent virtualization on every platform for list-heavy screens.\n- Crash reporting and real-user performance monitoring (Crashlytics, App Center, or equivalent) wired in from day one.\n- Staged rollout mechanisms (phased release \u002F percentage rollout) to catch regressions before full-audience exposure.\n",{"name":5,"tags":48,"tools":50,"source":57,"license":14,"description":7},[38,49,24],"engineering",[51,52,53,54,55,56],"monograph_query","monograph_context","monograph_impact","monodesign_detect","monodesign_fix","monodesign_palette","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmobile-app-builder",2,"https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add monoes\u002Fmonomind --skill mobile-app-builder",{"tool":72,"command":73},"bunx","bunx skills add monoes\u002Fmonomind --skill mobile-app-builder",{"tool":75,"command":76},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill mobile-app-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fmobile-app-builder\u002FSKILL.md",true,[],[81,105,140,167,192,219],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":104},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[88,89,90,91,92,93,37,94,36,35,95,96,31,97,98,99,100,101,102,103],"zk","zk steward","steward","zero-knowledge","engineer","choice","knowledge","snark","review","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":121,"publishedAt":104},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[113,116],{"categoryNo":114,"categoryName":115,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[122,123,124,92,125,126,127,128,35,129,130,131,132,133,134,135,136,137,138,139],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":144,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":104},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000031","产品经理",[133,151,152,153,154,94,155,127,156,157,158,132,159,160,161,162,163,164,165,166],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":171,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":104},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000033","数据分析师",[35,133,178,179,180,181,94,165,127,182,183,184,185,158,186,187,188,189,190,191],"write query","postgres","for","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":204,"publishedAt":104},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[205,206,207,208,180,209,210,211,212,36,213,214,215,35,31,186,216,217,218,188],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":104},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[225],{"categoryNo":202,"categoryName":203,"taxonomyType":20,"taxonomyTypeDesc":21},[207,227,228,229,230,231,232,180,233,234,129,235,236,237,31,186,238,239,188,240],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]