[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79T60S8K6MDP8VVX574CTRM":3,"skill-same:01M79T60S8K6MDP8VVX574CTRM":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},"01M79T60S8K6MDP8VVX574CTRM","react-native-architect",null,"Architect-level React Native guidance — the new architecture boundary (JSI\u002FFabric\u002FTurboModules), when to write native code, navigation and state ownership, list and image performance, OTA update policy, and the shared-codebase structure that keeps the JS and native sides honest. Use for React Native 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\u002Freact-native-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: react-native-architect\ndescription: Architect-level React Native guidance — the new architecture boundary (JSI\u002FFabric\u002FTurboModules), when to write native code, navigation and state ownership, list and image performance, OTA update policy, and the shared-codebase structure that keeps the JS and native sides honest. Use for React Native apps.\nlicense: MIT\ncompatibility: React Native 0.74+ (New Architecture); Expo or bare\nmetadata:\n  crusor-domain: mobile-architect\n  crusor-path: mobile-architect\u002Fplatforms-architect\u002Freact-native-architect\n  crusor-origin: original\n  crusor-sources: \"reactnative.dev\u002Fdocs; reactnative.dev\u002Farchitecture; docs.expo.dev\"\n  crusor-triggers: \"react native, expo, fabric, turbo modules, jsi, metro, mobile react, native module\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# React Native Architect\n\nReact Native is **a JavaScript runtime hosting native views**. Every performance\nand capability question is answered at that boundary.\n\n## When to use\n\n- A web\u002FTypeScript team shipping to both stores.\n- Business-facing UI with moderate platform integration.\n- Sharing domain logic with an existing React codebase.\n\n## When NOT to use\n\n- Heavy graphics, audio DSP, or deep platform SDK integration (native is cheaper\n  than bridged workarounds).\n- Pixel-identical design requirements across platforms (see\n  `flutter-architect`).\n\n## Decision 1 — Architecture boundary\n\n| Layer | Runs in |\n|---|---|\n| business logic, state, validation | JS\u002FTS |\n| navigation | JS (React Navigation) |\n| media, sensors, crypto, push | native module (TurboModule) |\n| heavy rendering | native view, wrapped |\n\n- New Architecture (JSI\u002FFabric) is the default assumption: no bridge-batching\n  excuses, but async-native calls still cost.\n- Write a native module when a JS workaround costs more than the module; keep it\n  behind a TS interface in the domain.\n- Anything on the JS thread blocks the UI thread's effects: keep it small.\n\n## Decision 2 — Project structure\n\n```\nsrc\u002Fapp\u002F         navigation, providers\n  src\u002Ffeatures\u002F  feature modules (screens, hooks, state)\n    src\u002Fdomain\u002F  entities and rules, platform-free\n      src\u002Fdata\u002F  api clients, local db, sync\n        native\u002F  module interfaces + platform implementations\n```\n\n- Feature-first, not type-first; a \"components\u002F\" barrel for everything rots.\n- One navigation tree, deep links declared once, typed route params.\n- State: local first, then a store; server state via TanStack Query (see\n  `tanstack-query-architect`).\n\n## Decision 3 — Performance rules that matter\n\n- Lists: FlatList\u002FFlashList with `keyExtractor`, `getItemLayout` where possible,\n  memoised row components, no inline arrow props per row.\n- Images: sized, cached, and never decoded on the JS thread at full resolution.\n- Animations: Reanimated on the UI thread, not `Animated` driven by JS state.\n- Startup: lazy screens, deferred native module init, measure with a release\n  build (dev builds lie).\n- Re-render discipline: narrow selectors, `React.memo` where measured — not\n  everywhere.\n\n## Decision 4 — Native integration\n\n- Permissions and capabilities behind a typed interface with a JS fallback\n  (`isAvailable`).\n- iOS\u002FAndroid implementations live next to each other; a missing platform is a\n  compile-time or runtime-checked error, never a silent no-op.\n- Native versions pinned; upgrading RN is a scheduled project, not a patch.\n\n## Decision 5 — Release and updates\n\n- OTA updates (EAS Update\u002FCodePush-style) only for JS, never for native changes;\n  a broken native build still needs review.\n- Runtime version pinning: an OTA must never target a binary it was not built\n  for.\n- Crash reporting with JS error boundaries per screen; a crash in one screen must\n  not white-screen the app.\n- Feature flags for anything risky, because rollback is a release.\n\n## Failure modes at scale\n\n- Everything in one giant `App.tsx` with navigation and providers entangled.\n- JS-thread work in scroll handlers → dropped frames on mid-tier Android.\n- Native module with no JS-side capability check → crash on the other platform.\n- OTA shipped to an incompatible binary version → immediate crash loop.\n- \"Works in dev build\" performance claims that vanish in release.\n\n## Verification receipts\n\n1. Release-build profile: cold start, JS thread FPS during scroll.\n2. List performance on a 5,000-item dataset.\n3. Native module matrix: iOS + Android behaviour verified separately.\n4. OTA compatibility test: runtime version mismatch refused.\n5. Crash-free session rate by screen after release.\n","# React Native Architect\n\nReact Native is **a JavaScript runtime hosting native views**. Every performance\nand capability question is answered at that boundary.\n\n## When to use\n\n- A web\u002FTypeScript team shipping to both stores.\n- Business-facing UI with moderate platform integration.\n- Sharing domain logic with an existing React codebase.\n\n## When NOT to use\n\n- Heavy graphics, audio DSP, or deep platform SDK integration (native is cheaper\n  than bridged workarounds).\n- Pixel-identical design requirements across platforms (see\n  `flutter-architect`).\n\n## Decision 1 — Architecture boundary\n\n| Layer | Runs in |\n|---|---|\n| business logic, state, validation | JS\u002FTS |\n| navigation | JS (React Navigation) |\n| media, sensors, crypto, push | native module (TurboModule) |\n| heavy rendering | native view, wrapped |\n\n- New Architecture (JSI\u002FFabric) is the default assumption: no bridge-batching\n  excuses, but async-native calls still cost.\n- Write a native module when a JS workaround costs more than the module; keep it\n  behind a TS interface in the domain.\n- Anything on the JS thread blocks the UI thread's effects: keep it small.\n\n## Decision 2 — Project structure\n\n```\nsrc\u002Fapp\u002F         navigation, providers\n  src\u002Ffeatures\u002F  feature modules (screens, hooks, state)\n    src\u002Fdomain\u002F  entities and rules, platform-free\n      src\u002Fdata\u002F  api clients, local db, sync\n        native\u002F  module interfaces + platform implementations\n```\n\n- Feature-first, not type-first; a \"components\u002F\" barrel for everything rots.\n- One navigation tree, deep links declared once, typed route params.\n- State: local first, then a store; server state via TanStack Query (see\n  `tanstack-query-architect`).\n\n## Decision 3 — Performance rules that matter\n\n- Lists: FlatList\u002FFlashList with `keyExtractor`, `getItemLayout` where possible,\n  memoised row components, no inline arrow props per row.\n- Images: sized, cached, and never decoded on the JS thread at full resolution.\n- Animations: Reanimated on the UI thread, not `Animated` driven by JS state.\n- Startup: lazy screens, deferred native module init, measure with a release\n  build (dev builds lie).\n- Re-render discipline: narrow selectors, `React.memo` where measured — not\n  everywhere.\n\n## Decision 4 — Native integration\n\n- Permissions and capabilities behind a typed interface with a JS fallback\n  (`isAvailable`).\n- iOS\u002FAndroid implementations live next to each other; a missing platform is a\n  compile-time or runtime-checked error, never a silent no-op.\n- Native versions pinned; upgrading RN is a scheduled project, not a patch.\n\n## Decision 5 — Release and updates\n\n- OTA updates (EAS Update\u002FCodePush-style) only for JS, never for native changes;\n  a broken native build still needs review.\n- Runtime version pinning: an OTA must never target a binary it was not built\n  for.\n- Crash reporting with JS error boundaries per screen; a crash in one screen must\n  not white-screen the app.\n- Feature flags for anything risky, because rollback is a release.\n\n## Failure modes at scale\n\n- Everything in one giant `App.tsx` with navigation and providers entangled.\n- JS-thread work in scroll handlers → dropped frames on mid-tier Android.\n- Native module with no JS-side capability check → crash on the other platform.\n- OTA shipped to an incompatible binary version → immediate crash loop.\n- \"Works in dev build\" performance claims that vanish in release.\n\n## Verification receipts\n\n1. Release-build profile: cold start, JS thread FPS during scroll.\n2. List performance on a 5,000-item dataset.\n3. Native module matrix: iOS + Android behaviour verified separately.\n4. OTA compatibility test: runtime version mismatch refused.\n5. Crash-free session rate by screen after 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\u002Freact-native-architect","mobile-architect","original","reactnative.dev\u002Fdocs; reactnative.dev\u002Farchitecture; docs.expo.dev","react native, expo, fabric, turbo modules, jsi, metro, mobile react, native module","2026-10-30","React Native 0.74+ (New Architecture); Expo or bare","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fmobile-architect\u002Fplatforms-architect\u002Freact-native-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 react-native-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill react-native-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill react-native-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fmobile-architect\u002Fplatforms-architect\u002Freact-native-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",[],[]]