[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSGJ2NP3KG6DBC5FCW7JN1":3,"skill-same:01M7CSGJ2NP3KG6DBC5FCW7JN1":73},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CSGJ2NP3KG6DBC5FCW7JN1","expo-module",null,"Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.","peterish8\u002Fprats-skill-atlas","peterish8","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F181628466?v=4","01M7CHQAPN6X8D29E2Q8DW4BYF","Prathick Dhanes R","01M7CHQAQ7T42E6D8HH3CZH342",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: expo-module\ndescription: Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.\nversion: 1.0.0\nlicense: MIT\n---\n\n# Writing Expo Modules\n\nComplete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript.\n\n## When to Use\n\n- Creating a new Expo native module or native view\n- Adding native functionality (camera, sensors, system APIs) to an Expo app\n- Wrapping platform SDKs for React Native consumption\n- Building config plugins that modify native project files\n- Adding Android, Apple, or web support to an existing Expo module\n- Editing `expo-module.config.json`, config plugins, or lifecycle hooks\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  create-expo-module.md      Scaffolding and add-platform-support workflow, defaults, and quirks\n  native-module.md           Module definition DSL: Name, Function, AsyncFunction, Property, Constant, Events, type system, shared objects\n  native-view.md             Native view components: View, Prop, EventDispatcher, view lifecycle, ref-based functions\n  lifecycle.md               Lifecycle hooks: module, iOS app\u002FAppDelegate, Android activity\u002Fapplication listeners\n  config-plugin.md           Config plugins: modifying Info.plist, AndroidManifest.xml, reading values in native code\n  module-config.md           expo-module.config.json fields, file placement, and autolinking behavior\n```\n\n## Quick Start\n\nPrefer `create-expo-module` over manually creating native module files and directories. In practice, the best path is usually to create the scaffold first and then build on top of it. The scaffold sets up the expected layout, `expo-module.config.json`, podspec or Gradle files, TypeScript bindings, and the standalone example app flow.\n\nIf an existing Expo module only needs another platform, use `create-expo-module add-platform-support` instead of manually copying native directories.\n\nSee [references\u002Fcreate-expo-module.md](references\u002Fcreate-expo-module.md) before scaffolding or extending a module. It covers:\n\n- local vs standalone modules\n- `--platform`, `--features`, `--barrel`, `--package-manager`, and non-interactive mode\n- `expo.autolinking.nativeModulesDir`\n- `add-platform-support` behavior and quirks\n\n## Recommended Workflow\n\n1. Choose the scaffold type first:\n   - **Local module** for one app\n   - **Standalone module** for reuse, monorepos, or publishing\n2. Determine native `expo-module` features that you will need.\n   - Based on the user's instructions determine which feature scaffolding will be useful.\n   - Available features: `Constant`, `Function`, `AsyncFunction`, `Event`, `View`,`ViewEvent`, `SharedObject`\n3. Scaffold deliberately:\n   - pass an explicit slug or path\n   - choose `--platform` intentionally instead of relying on defaults\n   - use `--features` to choose code samples which you will modify in the next stepto match the real implementation.\n4. Replace generated example code with the real implementation.\n5. If you add a new platform later, prefer `add-platform-support` over manual file copying.\n\n## Practical Scaffolding Rules\n\n- Feature examples are **opt-in**. A newly scaffolded module may be minimal if no features were selected.\n- `ViewEvent` implies `View`.\n- Local modules do **not** generate an `index.ts` barrel by default. Use `--barrel` only if you want one.\n- In non-interactive local scaffolding, pass the positional slug or path explicitly. `--name` changes the native class name, not the folder name.\n- Local modules live in `expo.autolinking.nativeModulesDir` when configured, otherwise in `modules\u002F`.\n- Standalone modules have their own package metadata, scripts, and usually an example app. Local modules use the host app's tooling instead.\n\n## Core File Shapes\n\nThe Swift and Kotlin DSL share the same structure. Swift is usually the clearest primary example; consult the references for feature-specific details.\n\n## Module Structure Reference\n\nThe Swift and Kotlin DSL share the same structure. Both platforms are shown here for reference — in other reference files, Swift is shown as the primary language unless the Kotlin pattern meaningfully differs.\n\n**Swift (iOS):**\n\n```swift\nimport ExpoModulesCore\n\npublic class MyModule: Module {\n  public func definition() -> ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { (name: String) -> String in\n      return \"Hello \\(name)!\"\n    }\n  }\n}\n```\n\n**Kotlin (Android):**\n\n```kotlin\npackage expo.modules.mymodule\n\nimport expo.modules.kotlin.modules.Module\nimport expo.modules.kotlin.modules.ModuleDefinition\n\nclass MyModule : Module() {\n  override fun definition() = ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { name: String ->\n      \"Hello $name!\"\n    }\n  }\n}\n```\n\n**TypeScript:**\n\n```typescript\nimport { requireNativeModule } from \"expo\";\n\nconst MyModule = requireNativeModule(\"MyModule\");\n\nexport function hello(name: string): string {\n  return MyModule.hello(name);\n}\n```\n\n### expo-module.config.json\n\n```json\n{\n  \"platforms\": [\"android\", \"apple\"],\n  \"apple\": {\n    \"modules\": [\"MyModule\"]\n  },\n  \"android\": {\n    \"modules\": [\"expo.modules.mymodule.MyModule\"]\n  }\n}\n```\n\nNote: iOS uses just the class name; Android uses the fully-qualified class name (package + class). See `references\u002Fmodule-config.md` for all fields.\n","# Writing Expo Modules\n\nComplete reference for building native modules and views using the Expo Modules API. Covers Swift (iOS), Kotlin (Android), and TypeScript.\n\n## When to Use\n\n- Creating a new Expo native module or native view\n- Adding native functionality (camera, sensors, system APIs) to an Expo app\n- Wrapping platform SDKs for React Native consumption\n- Building config plugins that modify native project files\n- Adding Android, Apple, or web support to an existing Expo module\n- Editing `expo-module.config.json`, config plugins, or lifecycle hooks\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  create-expo-module.md      Scaffolding and add-platform-support workflow, defaults, and quirks\n  native-module.md           Module definition DSL: Name, Function, AsyncFunction, Property, Constant, Events, type system, shared objects\n  native-view.md             Native view components: View, Prop, EventDispatcher, view lifecycle, ref-based functions\n  lifecycle.md               Lifecycle hooks: module, iOS app\u002FAppDelegate, Android activity\u002Fapplication listeners\n  config-plugin.md           Config plugins: modifying Info.plist, AndroidManifest.xml, reading values in native code\n  module-config.md           expo-module.config.json fields, file placement, and autolinking behavior\n```\n\n## Quick Start\n\nPrefer `create-expo-module` over manually creating native module files and directories. In practice, the best path is usually to create the scaffold first and then build on top of it. The scaffold sets up the expected layout, `expo-module.config.json`, podspec or Gradle files, TypeScript bindings, and the standalone example app flow.\n\nIf an existing Expo module only needs another platform, use `create-expo-module add-platform-support` instead of manually copying native directories.\n\nSee [references\u002Fcreate-expo-module.md](references\u002Fcreate-expo-module.md) before scaffolding or extending a module. It covers:\n\n- local vs standalone modules\n- `--platform`, `--features`, `--barrel`, `--package-manager`, and non-interactive mode\n- `expo.autolinking.nativeModulesDir`\n- `add-platform-support` behavior and quirks\n\n## Recommended Workflow\n\n1. Choose the scaffold type first:\n   - **Local module** for one app\n   - **Standalone module** for reuse, monorepos, or publishing\n2. Determine native `expo-module` features that you will need.\n   - Based on the user's instructions determine which feature scaffolding will be useful.\n   - Available features: `Constant`, `Function`, `AsyncFunction`, `Event`, `View`,`ViewEvent`, `SharedObject`\n3. Scaffold deliberately:\n   - pass an explicit slug or path\n   - choose `--platform` intentionally instead of relying on defaults\n   - use `--features` to choose code samples which you will modify in the next stepto match the real implementation.\n4. Replace generated example code with the real implementation.\n5. If you add a new platform later, prefer `add-platform-support` over manual file copying.\n\n## Practical Scaffolding Rules\n\n- Feature examples are **opt-in**. A newly scaffolded module may be minimal if no features were selected.\n- `ViewEvent` implies `View`.\n- Local modules do **not** generate an `index.ts` barrel by default. Use `--barrel` only if you want one.\n- In non-interactive local scaffolding, pass the positional slug or path explicitly. `--name` changes the native class name, not the folder name.\n- Local modules live in `expo.autolinking.nativeModulesDir` when configured, otherwise in `modules\u002F`.\n- Standalone modules have their own package metadata, scripts, and usually an example app. Local modules use the host app's tooling instead.\n\n## Core File Shapes\n\nThe Swift and Kotlin DSL share the same structure. Swift is usually the clearest primary example; consult the references for feature-specific details.\n\n## Module Structure Reference\n\nThe Swift and Kotlin DSL share the same structure. Both platforms are shown here for reference — in other reference files, Swift is shown as the primary language unless the Kotlin pattern meaningfully differs.\n\n**Swift (iOS):**\n\n```swift\nimport ExpoModulesCore\n\npublic class MyModule: Module {\n  public func definition() -> ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { (name: String) -> String in\n      return \"Hello \\(name)!\"\n    }\n  }\n}\n```\n\n**Kotlin (Android):**\n\n```kotlin\npackage expo.modules.mymodule\n\nimport expo.modules.kotlin.modules.Module\nimport expo.modules.kotlin.modules.ModuleDefinition\n\nclass MyModule : Module() {\n  override fun definition() = ModuleDefinition {\n    Name(\"MyModule\")\n\n    Function(\"hello\") { name: String ->\n      \"Hello $name!\"\n    }\n  }\n}\n```\n\n**TypeScript:**\n\n```typescript\nimport { requireNativeModule } from \"expo\";\n\nconst MyModule = requireNativeModule(\"MyModule\");\n\nexport function hello(name: string): string {\n  return MyModule.hello(name);\n}\n```\n\n### expo-module.config.json\n\n```json\n{\n  \"platforms\": [\"android\", \"apple\"],\n  \"apple\": {\n    \"modules\": [\"MyModule\"]\n  },\n  \"android\": {\n    \"modules\": [\"expo.modules.mymodule.MyModule\"]\n  }\n}\n```\n\nNote: iOS uses just the class name; Android uses the fully-qualified class name (package + class). See `references\u002Fmodule-config.md` for all fields.\n",{"name":5,"license":15,"version":24,"description":7},"1.0.0","main","f1bcf88a052c2ccbb297666b33fb820cfd94ac71",".codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module",0,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas","https:\u002F\u002Fgithub.com\u002Fpeterish8","Building real-world products with clean UI, smart architecture, and privacy in mind. Frontend-focused, full-stack curious.","2026-10-15 19:02:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add peterish8\u002Fprats-skill-atlas --skill expo-module",{"tool":39,"command":40},"bunx","bunx skills add peterish8\u002Fprats-skill-atlas --skill expo-module",{"tool":42,"command":43},"pnpm","pnpm dlx skills add peterish8\u002Fprats-skill-atlas --skill expo-module","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002FSKILL.md",true,[47,53,57,61,65,69],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fconfig-plugin.md","REFERENCE","参考文档",2040,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Fconfig-plugin.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcreate-expo-module.md",10075,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Fcreate-expo-module.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Flifecycle.md",3763,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Flifecycle.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fmodule-config.md",1762,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Fmodule-config.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fnative-module.md",5869,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Fnative-module.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fnative-view.md",3590,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Fmobile\u002Fnative-and-cross-platform\u002Fexpo-module\u002Freferences\u002Fnative-view.md",[74,83,91,99,106,114],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CTAZW9MHV3RWH2ZEKDQXG9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\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":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CT8MG7NB1JR67XYZ9EWW3B","seo-audit","Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CT87F6GQ0WAD393PKPAGGX","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CT809RF90MG98MYEA97D8Z","gsap-performance","Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fgsap-performance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CT7Q4VD995JHZMQQFBZZV9","firecrawl-seo-audit","Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap\u002Fsite-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.","ISC","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-seo-audit\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":110,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7CT7JRJFC5RAKJBAP0VS1CV","firecrawl-qa","QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation\u002Flink checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-qa\u002FSKILL.md",[],[]]