[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HCCKVFXTXBKREP08GS7GH":3,"skill-same:01M71HCCKVFXTXBKREP08GS7GH":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M71HCCKVFXTXBKREP08GS7GH","expo-ui-jetpack-compose",null,"@expo\u002Fui\u002Fjetpack-compose package lets you use Jetpack Compose Views and modifiers in your app.","runecraftai\u002Farcanum","runecraftai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F279098826?v=4","01M71HBGS1RCAJ490RAYST7M00","01M71HBGT1CB94MNS6T6SGAZKW",1,"MIT","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Ffamiliar\u002Fskills\u002Fexpo-ui-jetpack-compose\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33],"compose","jetpack compose","expo ui","expo","expo ui jetpack compose","ui","jetpack","app","package","use","you","2026-11-10 10:12:30",false,"---\nname: expo-ui-jetpack-compose\ndescription: \"@expo\u002Fui\u002Fjetpack-compose package lets you use Jetpack Compose Views and modifiers in your app.\"\n---\n\n> The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI Jetpack Compose docs for that version for the most accurate information.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nA native rebuild is required after installation (`npx expo run:android`).\n\n## Instructions\n\n- Expo UI's API mirrors Jetpack Compose's API. Use Jetpack Compose and Material Design 3 knowledge to decide which components or modifiers to use. If you need deeper Jetpack Compose or Material 3 guidance (e.g. which component to pick, layout patterns, theming), spawn a subagent to research [Jetpack Compose](https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fui\u002Fcompose\u002Fcomponents) and [Material Design 3](https:\u002F\u002Fm3.material.io\u002F) best practices.\n- Components are imported from `@expo\u002Fui\u002Fjetpack-compose`, modifiers from `@expo\u002Fui\u002Fjetpack-compose\u002Fmodifiers`.\n- **Always read the `.d.ts` type files** to confirm the exact API before using a component or modifier. Run `node -e \"console.log(path.dirname(require.resolve('@expo\u002Fui\u002Fjetpack-compose')))\"` to locate the package, then read the relevant `{ComponentName}\u002Findex.d.ts` files. This is the most reliable source of truth.\n- When about to use a component, fetch its docs to confirm the API - https:\u002F\u002Fdocs.expo.dev\u002Fversions\u002Fv55.0.0\u002Fsdk\u002Fui\u002Fjetpack-compose\u002F{component-name}\u002Findex.md\n- When unsure about a modifier's API, refer to the docs - https:\u002F\u002Fdocs.expo.dev\u002Fversions\u002Fv55.0.0\u002Fsdk\u002Fui\u002Fjetpack-compose\u002Fmodifiers\u002Findex.md\n- Every Jetpack Compose tree must be wrapped in `Host`. Use `\u003CHost matchContents>` for intrinsic sizing, or `\u003CHost style={{ flex: 1 }}>` when you need explicit size (e.g. as a parent of `LazyColumn`). Example:\n\n```jsx\nimport { Host, Column, Button, Text } from \"@expo\u002Fui\u002Fjetpack-compose\";\nimport { fillMaxWidth, paddingAll } from \"@expo\u002Fui\u002Fjetpack-compose\u002Fmodifiers\";\n\n\u003CHost matchContents>\n  \u003CColumn verticalArrangement={{ spacedBy: 8 }} modifiers={[fillMaxWidth(), paddingAll(16)]}>\n    \u003CText style={{ typography: \"titleLarge\" }}>Hello\u003C\u002FText>\n    \u003CButton onPress={() => alert(\"Pressed!\")}>Press me\u003C\u002FButton>\n  \u003C\u002FColumn>\n\u003C\u002FHost>;\n```\n\n## Key Components\n\n- **LazyColumn** — Use instead of react-native `ScrollView`\u002F`FlatList` for scrollable lists. Wrap in `\u003CHost style={{ flex: 1 }}>`.\n- **Icon** — Use `\u003CIcon source={require('.\u002Ficon.xml')} size={24} \u002F>` with Android XML vector drawables. To get icons: go to [Material Symbols](https:\u002F\u002Ffonts.google.com\u002Ficons), select an icon, choose the Android platform, and download the XML vector drawable. Save these as `.xml` files in your project's `assets\u002F` directory (e.g. `assets\u002Ficons\u002Fwifi.xml`). Metro bundles `.xml` assets automatically — no metro config changes needed.\n","> The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI Jetpack Compose docs for that version for the most accurate information.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nA native rebuild is required after installation (`npx expo run:android`).\n\n## Instructions\n\n- Expo UI's API mirrors Jetpack Compose's API. Use Jetpack Compose and Material Design 3 knowledge to decide which components or modifiers to use. If you need deeper Jetpack Compose or Material 3 guidance (e.g. which component to pick, layout patterns, theming), spawn a subagent to research [Jetpack Compose](https:\u002F\u002Fdeveloper.android.com\u002Fdevelop\u002Fui\u002Fcompose\u002Fcomponents) and [Material Design 3](https:\u002F\u002Fm3.material.io\u002F) best practices.\n- Components are imported from `@expo\u002Fui\u002Fjetpack-compose`, modifiers from `@expo\u002Fui\u002Fjetpack-compose\u002Fmodifiers`.\n- **Always read the `.d.ts` type files** to confirm the exact API before using a component or modifier. Run `node -e \"console.log(path.dirname(require.resolve('@expo\u002Fui\u002Fjetpack-compose')))\"` to locate the package, then read the relevant `{ComponentName}\u002Findex.d.ts` files. This is the most reliable source of truth.\n- When about to use a component, fetch its docs to confirm the API - https:\u002F\u002Fdocs.expo.dev\u002Fversions\u002Fv55.0.0\u002Fsdk\u002Fui\u002Fjetpack-compose\u002F{component-name}\u002Findex.md\n- When unsure about a modifier's API, refer to the docs - https:\u002F\u002Fdocs.expo.dev\u002Fversions\u002Fv55.0.0\u002Fsdk\u002Fui\u002Fjetpack-compose\u002Fmodifiers\u002Findex.md\n- Every Jetpack Compose tree must be wrapped in `Host`. Use `\u003CHost matchContents>` for intrinsic sizing, or `\u003CHost style={{ flex: 1 }}>` when you need explicit size (e.g. as a parent of `LazyColumn`). Example:\n\n```jsx\nimport { Host, Column, Button, Text } from \"@expo\u002Fui\u002Fjetpack-compose\";\nimport { fillMaxWidth, paddingAll } from \"@expo\u002Fui\u002Fjetpack-compose\u002Fmodifiers\";\n\n\u003CHost matchContents>\n  \u003CColumn verticalArrangement={{ spacedBy: 8 }} modifiers={[fillMaxWidth(), paddingAll(16)]}>\n    \u003CText style={{ typography: \"titleLarge\" }}>Hello\u003C\u002FText>\n    \u003CButton onPress={() => alert(\"Pressed!\")}>Press me\u003C\u002FButton>\n  \u003C\u002FColumn>\n\u003C\u002FHost>;\n```\n\n## Key Components\n\n- **LazyColumn** — Use instead of react-native `ScrollView`\u002F`FlatList` for scrollable lists. Wrap in `\u003CHost style={{ flex: 1 }}>`.\n- **Icon** — Use `\u003CIcon source={require('.\u002Ficon.xml')} size={24} \u002F>` with Android XML vector drawables. To get icons: go to [Material Symbols](https:\u002F\u002Ffonts.google.com\u002Ficons), select an icon, choose the Android platform, and download the XML vector drawable. Save these as `.xml` files in your project's `assets\u002F` directory (e.g. `assets\u002Ficons\u002Fwifi.xml`). Metro bundles `.xml` assets automatically — no metro config changes needed.\n",{"name":5,"description":7},"main","33b040feb49e126600394272a8e321a3cd279e8b","packages\u002Ffamiliar\u002Fskills\u002Fexpo-ui-jetpack-compose",0,"https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum","https:\u002F\u002Fgithub.com\u002Frunecraftai","2026-07-29 22:08:52",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add runecraftai\u002Farcanum --skill expo-ui-jetpack-compose",{"tool":52,"command":53},"bunx","bunx skills add runecraftai\u002Farcanum --skill expo-ui-jetpack-compose",{"tool":55,"command":56},"pnpm","pnpm dlx skills add runecraftai\u002Farcanum --skill expo-ui-jetpack-compose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Ffamiliar\u002Fskills\u002Fexpo-ui-jetpack-compose\u002FSKILL.md",true,[],[61,93,117,143,164,188],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":73,"publishedAt":34},"01M71HGTN9FRQ3WEZMVVX7C3VZ","using-agent-skills","Discovers and invokes the right @runecraft\u002Fspells skill for the current task. Use when starting a session, when a request is ambiguous about which workflow to apply, or when you need to pick among the 13-skill Arcanum catalog. EN triggers: \u002Fskill, which skill, pick a skill, what skill should I use, skill discovery, meta skill. PT triggers: qual skill, qual habilidade, descobrir skill, qual fluxo usar. Do NOT use for: actual implementation work (route to the specific skill instead), unrelated standalone tasks outside the Arcanum catalog, or runtime-specific configuration (e.g., opencode.json \u002F Claude Code plugin paths).","CC-BY-4.0","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[74,75,76,77,78,79,80,81,33,82,83,84,85,86,87,88,89,90,91,92],"using agent skills","standalone","which","pt","pick","Meta","when","workflow","code","tasks","skill discovery","route","work","unrelated","opencode","request","paths","a skill","ambiguous",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":34},"01M71HGPD6N9JH2G8EVBXJR77X","typescript-patterns","TypeScript best practices and patterns for type-safe, maintainable code. Covers discriminated unions, generics, const assertions, type narrowing, and common anti-patterns. Extends (does not override) project tsconfig. EN triggers: \u002Ftypescript, TypeScript patterns, TS best practices, type safety, discriminated unions, generics, type narrowing. PT triggers: \u002Ftypescript, padrões TypeScript, boas práticas TS, segurança de tipos, unions discriminadas, genéricos. Do NOT use for: JavaScript-only projects, runtime performance, or replacing project tsconfig rules.","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Ftypescript-patterns\u002FSKILL.md",[],[100,101,102,103,104,105,77,106,107,108,109,110,111,112,32,113,114,115,82,116],"typescript","patterns","typescript patterns","do","projects","for","runtime","project","performance","en","maintainable code","triggers","only","assertions","Rules","best practices","common",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":129,"publishedAt":34},"01M71HGJAKX4TFN0PECYPJ9S38","test-driven-development","Drives development with tests — fail first, then make them pass, then refactor. Use when implementing any logic, fixing any bug, or changing any behavior. EN triggers: \u002Ftest, write tests first, TDD, prove it, 80\u002F15\u002F5 pyramid, Beyonce Rule. PT triggers: \u002Fteste, testes primeiro, provar com teste, pirâmide 80\u002F15\u002F5. Do NOT use for: production incident triage (use \u002Fdebug), or cosmetic-only changes with no behavioral surface.","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":127,"categoryName":128,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000008","测试与质量",[130,131,132,133,77,134,135,136,112,80,137,138,139,140,141,103,105,109,111,142],"test driven development","development","test","driven","incident","implementing","write tests","write","bug","refactor","behavioral","make","tests",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":34},"01M71HGC1H4JQFJWH613XTJC59","spec-driven","Feature planning and implementation with 4 adaptive phases — Specify, Design, Tasks, Execute. Auto-sizes depth by complexity. Creates atomic tasks with verification criteria, atomic git commits, and requirement traceability. Features an independent Verifier (author != verifier, evidence-or-zero), persistent decision log (STATE.md), and test-coverage-matrix-driven tests, plus a self-improving lessons layer that turns verification failures into reusable project-local guidance. Stack-agnostic. Use when planning features (requirements, design, task breakdown), implementing with verification and atomic commits, or validating\u002Fverifying an implementation against a spec. Triggers (PT\u002FEN): \"specify feature\", \"vamos especificar\", \"discutir feature\", \"discutir este caso\", \"design\", \"design da feature\", \"tarefas\", \"quebrar em tarefas\", \"implementar\", \"build\", \"validar\", \"verify work\", \"UAT\", \"validar implementação\", \"record decision\", \"pause work\", \"pausar trabalho\", \"resume work\", \"retomar trabalho\". Do NOT use for architecture decomposition analysis (use architecture skills) or technical design docs (treat as Complex scope: discuss gray areas + architecture-focused design).","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Fspec-driven\u002FSKILL.md",[],[150,151,133,152,153,154,155,77,107,156,135,157,158,159,160,161,80,162,83,163],"spec driven","spec","coverage","complexity","task breakdown","scope","decision","local","design","self-improving","auto","atomic commits","analysis","architecture",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":174,"publishedAt":34},"01M71HG5CSP04F29HRAG7XVYKG","skill-forge","Designs, authors, validates, and optimizes new Agent Skills from scratch. Use when creating a new skill, packaging a workflow as a skill, improving a skill's triggering accuracy, or evaluating whether a skill improves output quality. Covers the full lifecycle: DISCOVER, DESIGN, AUTHOR, VALIDATE, OPTIMIZE, DELIVER. Produces skills that follow the open SKILL.md format (YAML frontmatter + Markdown body, progressive disclosure, validation loops). EN triggers: \u002Fforge, create a skill, write a skill, build a skill, new skill, author a skill, package this as a skill, validate a skill, improve skill triggering, optimize skill description, evaluate skill quality. PT triggers: \u002Fforge, criar uma skill, escrever uma skill, construir uma skill, nova skill, empacotar como skill, validar skill, melhorar disparo, otimizar descrição de skill. Do NOT use for: discovering which existing skill to apply (use a dispatch\u002Fmeta skill), planning feature implementation, or designing software architecture.","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Fskill-forge\u002FSKILL.md",[170,173],{"categoryNo":171,"categoryName":172,"taxonomyType":71,"taxonomyTypeDesc":72},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":69,"categoryName":70,"taxonomyType":71,"taxonomyTypeDesc":72},[175,176,177,76,178,179,77,180,79,181,182,158,163,183,184,137,185,91,186,187],"forge","skill forge","deliver","new agent","feature implementation","packaging","improve","open","create","de","software","new skill","full",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":34},"01M71HG1RAQY3GXX0Q5TMW0XD6","shipping-and-launch","Prepares production launches with a pre-launch checklist, staged rollout, monitoring, and a rollback strategy — plus feature flag lifecycle (off → internal → beta → GA). Use when deploying a feature to production for the first time, releasing a significant change, or planning a rollout. EN triggers: \u002Fship, pre-launch checklist, staged rollout, feature flag, rollback plan, monitoring. PT triggers: \u002Fshippar, checklist pré-lançamento, rollout gradual, feature flag, plano de rollback. Do NOT use for: pre-production development work, or one-off internal tools with no user exposure.","https:\u002F\u002Fgithub.com\u002Frunecraftai\u002Farcanum\u002Fblob\u002Fmain\u002Fpackages\u002Fspells\u002Fskills\u002Fshipping-and-launch\u002FSKILL.md",[],[195,196,197,77,198,199,80,200,201,202,203,86,204,205,206,207,184,208,209,210],"shipping and launch","shipping","launch","time","beta","rollout","rollback plan","monitoring","rollback strategy","plan","change","exposure","plano","ship","Tools","pre-launch"]