[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77K06B1DBD0MPY4C88CVQ2C":3,"skill-same:01M77K06B1DBD0MPY4C88CVQ2C":62},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M77K06B1DBD0MPY4C88CVQ2C","mobiai-create-pr",null,"YOU MUST use this before ANY git push, branch push to remote, merge, or PR creation — regardless of phrasing or language. Covers all irreversible integration actions (committing, pushing, opening a PR, shipping finished work). Also triggers proactively after a fix when the user signals completion (still ask before pushing). Works with any git hosting provider.","AdriaanAt\u002FEcosystem-Manager","AdriaanAt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F170892248?v=4","01M77JXW5RB9W9WXQ7RS8ERQ6T","Adriaan","01M77JXW6V5MNR0P0F7D401Y7D",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fcore\u002Fskills\u002Fmobiai-create-pr\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mobiai-create-pr\ndescription: \"YOU MUST use this before ANY git push, branch push to remote, merge, or PR creation — regardless of phrasing or language. Covers all irreversible integration actions (committing, pushing, opening a PR, shipping finished work). Also triggers proactively after a fix when the user signals completion (still ask before pushing). Works with any git hosting provider.\"\nlicense: MIT\ncompatibility: [claude-code, cursor, copilot, codex]\nplatforms: [android, ios, kmp, flutter, react-native]\n---\n\n# Create PR\n\nCreate a well-structured pull request for mobile code changes.\n\n## When to Use\n\nMatch on **intent**, not specific words or languages. The user's phrasing is a signal, not a keyword match — read meaning in context.\n\n**Explicit intent** (user directly expresses they want to save, share, or submit changes):\n- Intent to commit the current work\n- Intent to push the current branch\n- Intent to open a pull request\n- Instruction to \"ship\", \"deliver\", \"submit\", or otherwise mark work as ready\n- Final step of the `mobiai-fix-issue` pipeline\n\nWhen intent is explicit, proceed through the workflow — but still confirm before pushing (see \"Never\" below).\n\n**Implicit intent after completed work** (user approves something you just finished):\nAfter you report a fix, review, or implementation as done, any user signal that the work is acceptable — approval, agreement, confirmation, green light, a simple \"ok\" in any language — is an implicit cue that the next action is probably to ship it. Do not act on implicit intent. Instead, ASK: propose creating the PR and wait for explicit confirmation. The language of your question should match the user's.\n\nDistinguish implicit approval from continued discussion: if the user keeps asking questions, requests more changes, or is still evaluating, do not offer a PR yet.\n\n**Never**:\n- Act on implicit intent without asking — always confirm before pushing or opening a PR\n- Commit directly to protected or long-lived branches (`main`, `master`, `develop`, `release\u002F*`, `staging`) — always move to a feature branch first\n- Push without explicit user confirmation\n- Skip the changelog\u002FREADME update step when the project has one\n\n## Workflow\n\n### Step 1: Prepare the Branch\n\n1. **Check the current branch first.** If you're on a protected or long-lived branch (`main`, `master`, `develop`, `release\u002F*`, `staging`), NEVER commit there — create a feature branch. Name it after the issue key: `fix\u002F\u003Cissue-key>`, `feat\u002F\u003Cissue-key>`, or `chore\u002F\u003Cdescription>`:\n   ```bash\n   git checkout -b fix\u002F\u003Cissue-key>\n   ```\n\n   If you've already committed to the wrong branch (e.g. a release branch), move the commit to a new feature branch before pushing:\n   ```bash\n   git branch fix\u002F\u003Cissue-key>                 # save the commit under a new branch name\n   git reset --hard origin\u002F\u003Ccurrent-branch>   # rewind the protected branch to the remote\n   git checkout fix\u002F\u003Cissue-key>               # switch to the feature branch\n   ```\n\n2. **Stage the changes**:\n   ```bash\n   git add \u003Cspecific-files>  # Prefer specific files over git add -A\n   ```\n\n3. **Commit with a descriptive message**:\n   ```bash\n   git commit -m \"fix: \u003Cshort description>\n\n   \u003Cissue-key>: \u003Cwhat was wrong and why>\n\n   - Root cause: \u003Cexplanation>\n   - Fix: \u003Cwhat was changed>\n   - Tests: \u003Cwhat tests were added>\"\n   ```\n\n### Step 2: Update Changelog (if applicable)\n\nIf the project has a changelog file (CHANGELOG.md, HISTORY.md, or a section in README.md):\n\n1. Read the changelog to understand the format\n2. Add an entry under the current\u002Funreleased version\n3. Follow the project's existing style (Keep a Changelog, custom format, etc.)\n4. Don't duplicate entries — check if the issue key already exists\n\n### Step 3: Determine the Base Branch\n\n**CRITICAL**: Do NOT assume the PR targets `main` or `master`.\n\n1. **Ask the user** if they haven't specified: \"What branch should this be merged into?\"\n2. If the current branch was created from another branch, use that as the base:\n   ```bash\n   # Check what branch this was branched from\n   git log --oneline --first-parent main..HEAD | tail -1  # if few commits → likely from main\n   git log --oneline --first-parent develop..HEAD | tail -1  # check develop too\n   ```\n3. Check the repo's default branch: `gh repo view --json defaultBranchRef`\n4. If the project uses gitflow or similar (develop, release\u002F*), respect that workflow\n\nUse `--base \u003Cbranch>` when creating the PR to target the correct branch.\n\n### Step 4: Push and Open the PR\n\nConfirm with the user before pushing (project rule: never push without explicit approval).\n\n#### Step 4.1: Identify the hosting provider\n\nInspect the remote to figure out which provider this repo uses:\n\n```bash\ngit remote get-url origin\n```\n\nAdapt the rest of the workflow to that provider. Prefer a native CLI when one is installed and authenticated (it lets you set title, body, and base branch in one shot). Fall back to constructing the provider's web URL for creating a PR\u002FMR when no CLI is available. You are expected to know the conventions for the major providers — if unsure, check the provider's docs rather than guessing URL formats.\n\n#### Step 4.2: Push the branch\n\n```bash\ngit push -u origin \u003Cfeature-branch>\n```\n\n#### Step 4.3: Create the PR \u002F MR\n\nProduce the PR with this exact title format and body template, regardless of provider:\n\n**Title**: `fix: \u003Cshort description>` (or `feat:`, `refactor:`, etc. per Conventional Commits, unless the project uses a different style — check `git log` for the pattern)\n\n**Body**:\n\n```markdown\n## Summary\n- **Issue**: \u003Cissue-key>\n- **Root cause**: \u003Cthe actual cause in plain language — not the symptom>\n- **Breaking commit**: \u003CSHA and subject of the commit that introduced the bug, e.g. `a1b2c3d \"feat: refactor user loader\"`. If the bug has always existed and is not a regression, write \"always-existed, not a regression\".>\n- **Fix**: \u003Cwhat was changed at a high level>\n\n## Why each change\n\u003CFor every distinct change in the diff, explain the reasoning that links the root cause to this specific modification. Do NOT restate what the diff already shows — explain *why* it had to change. One bullet per logical change. Example: \"`loadUser()` now checks `response.body == null` before dereferencing because the root cause is that the backend returns null bodies when the auth token is stale, which the caller did not anticipate.\">\n\n- \u003Creasoning 1>\n- \u003Creasoning 2>\n\n## Platform\n- **Affected platform**: Android \u002F iOS \u002F both\n- **Min SDK \u002F deployment target affected**: \u003Ce.g. API 24, iOS 15>\n- **New permissions or entitlements**: \u003Clist any, or \"none\">\n\n## Changes\n\u003CFile-by-file factual summary. Keep this factual — what, not why. The \"why\" is already above.>\n- `path\u002Fto\u002Ffile.kt` — \u003Ce.g. \"added null check on `response.body` before `.size()` call on line 42\">\n\n## Test Plan\n- [ ] Unit tests added for \u003Cwhat>\n- [ ] Existing tests pass\n- [ ] Compile check passes\n- [ ] Tested on device \u002F emulator: \u003Cmodel, OS version>\n- [ ] Tested both orientations (portrait & landscape)\n- [ ] Checked dark mode appearance\n- [ ] Accessibility reviewed (TalkBack \u002F VoiceOver, content descriptions)\n- [ ] \u003CManual test steps if applicable>\n\n## Regression Risk\n- [ ] Touches Activity\u002FFragment lifecycle or ViewController lifecycle\n- [ ] Touches threading \u002F coroutines \u002F Dispatchers \u002F GCD\n- [ ] Touches navigation graph or deep links\n- [ ] Modifies ProGuard \u002F R8 rules or iOS build settings\n- [ ] Changes dependency versions\n- **Risk notes**: \u003Cbrief explanation of what could break>\n\n## Screenshots \u002F Evidence\n\u003CIf visual change, add before\u002Fafter screenshots or screen recordings>\n```\n\n**Submit via CLI** if one is installed and authenticated for the provider — pass the title, body, and base branch as arguments so everything is set in a single command.\n\n**Submit via web URL** if no CLI is available. Push the branch first, then build the provider's \"new PR\u002FMR\" URL with source branch and target branch as query parameters. Give the user:\n1. The clickable URL (prefills source and target)\n2. The title to paste\n3. The full body to paste\n\nDo not omit the title or body in the web-URL case — most providers do not auto-populate them from commit messages, and the template is the main value this skill delivers.\n\n### Step 5: Verify\n\nAfter creating the PR:\n1. Verify the diff on the PR looks correct (no unintended files, no secrets)\n2. Report the PR URL to the user\n3. Check CI status if the provider's CLI supports it; otherwise ask the user to confirm the PR was created and CI passed\n\n## PR Title Conventions\n\nFollow [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) if the project uses them:\n- `fix: resolve crash when opening checkout with zero amount`\n- `feat: add dark mode support to settings screen`\n- `refactor: extract payment logic into separate use case`\n\nIf the project doesn't use conventional commits, follow whatever pattern exists in recent PRs:\n```bash\ngit log --oneline -20  # Check recent commit message style\n```\n\n## Commit Rules\n\n- **Never commit secrets** (.env, `google-services.json`, `local.properties`, signing keystores, API keys). Warn the user if they ask to.\n- **Prefer specific files** over `git add -A` or `git add .`\n- **One logical change per commit** — don't mix unrelated changes\n- **Never force push** unless the user explicitly asks\n","# Create PR\n\nCreate a well-structured pull request for mobile code changes.\n\n## When to Use\n\nMatch on **intent**, not specific words or languages. The user's phrasing is a signal, not a keyword match — read meaning in context.\n\n**Explicit intent** (user directly expresses they want to save, share, or submit changes):\n- Intent to commit the current work\n- Intent to push the current branch\n- Intent to open a pull request\n- Instruction to \"ship\", \"deliver\", \"submit\", or otherwise mark work as ready\n- Final step of the `mobiai-fix-issue` pipeline\n\nWhen intent is explicit, proceed through the workflow — but still confirm before pushing (see \"Never\" below).\n\n**Implicit intent after completed work** (user approves something you just finished):\nAfter you report a fix, review, or implementation as done, any user signal that the work is acceptable — approval, agreement, confirmation, green light, a simple \"ok\" in any language — is an implicit cue that the next action is probably to ship it. Do not act on implicit intent. Instead, ASK: propose creating the PR and wait for explicit confirmation. The language of your question should match the user's.\n\nDistinguish implicit approval from continued discussion: if the user keeps asking questions, requests more changes, or is still evaluating, do not offer a PR yet.\n\n**Never**:\n- Act on implicit intent without asking — always confirm before pushing or opening a PR\n- Commit directly to protected or long-lived branches (`main`, `master`, `develop`, `release\u002F*`, `staging`) — always move to a feature branch first\n- Push without explicit user confirmation\n- Skip the changelog\u002FREADME update step when the project has one\n\n## Workflow\n\n### Step 1: Prepare the Branch\n\n1. **Check the current branch first.** If you're on a protected or long-lived branch (`main`, `master`, `develop`, `release\u002F*`, `staging`), NEVER commit there — create a feature branch. Name it after the issue key: `fix\u002F\u003Cissue-key>`, `feat\u002F\u003Cissue-key>`, or `chore\u002F\u003Cdescription>`:\n   ```bash\n   git checkout -b fix\u002F\u003Cissue-key>\n   ```\n\n   If you've already committed to the wrong branch (e.g. a release branch), move the commit to a new feature branch before pushing:\n   ```bash\n   git branch fix\u002F\u003Cissue-key>                 # save the commit under a new branch name\n   git reset --hard origin\u002F\u003Ccurrent-branch>   # rewind the protected branch to the remote\n   git checkout fix\u002F\u003Cissue-key>               # switch to the feature branch\n   ```\n\n2. **Stage the changes**:\n   ```bash\n   git add \u003Cspecific-files>  # Prefer specific files over git add -A\n   ```\n\n3. **Commit with a descriptive message**:\n   ```bash\n   git commit -m \"fix: \u003Cshort description>\n\n   \u003Cissue-key>: \u003Cwhat was wrong and why>\n\n   - Root cause: \u003Cexplanation>\n   - Fix: \u003Cwhat was changed>\n   - Tests: \u003Cwhat tests were added>\"\n   ```\n\n### Step 2: Update Changelog (if applicable)\n\nIf the project has a changelog file (CHANGELOG.md, HISTORY.md, or a section in README.md):\n\n1. Read the changelog to understand the format\n2. Add an entry under the current\u002Funreleased version\n3. Follow the project's existing style (Keep a Changelog, custom format, etc.)\n4. Don't duplicate entries — check if the issue key already exists\n\n### Step 3: Determine the Base Branch\n\n**CRITICAL**: Do NOT assume the PR targets `main` or `master`.\n\n1. **Ask the user** if they haven't specified: \"What branch should this be merged into?\"\n2. If the current branch was created from another branch, use that as the base:\n   ```bash\n   # Check what branch this was branched from\n   git log --oneline --first-parent main..HEAD | tail -1  # if few commits → likely from main\n   git log --oneline --first-parent develop..HEAD | tail -1  # check develop too\n   ```\n3. Check the repo's default branch: `gh repo view --json defaultBranchRef`\n4. If the project uses gitflow or similar (develop, release\u002F*), respect that workflow\n\nUse `--base \u003Cbranch>` when creating the PR to target the correct branch.\n\n### Step 4: Push and Open the PR\n\nConfirm with the user before pushing (project rule: never push without explicit approval).\n\n#### Step 4.1: Identify the hosting provider\n\nInspect the remote to figure out which provider this repo uses:\n\n```bash\ngit remote get-url origin\n```\n\nAdapt the rest of the workflow to that provider. Prefer a native CLI when one is installed and authenticated (it lets you set title, body, and base branch in one shot). Fall back to constructing the provider's web URL for creating a PR\u002FMR when no CLI is available. You are expected to know the conventions for the major providers — if unsure, check the provider's docs rather than guessing URL formats.\n\n#### Step 4.2: Push the branch\n\n```bash\ngit push -u origin \u003Cfeature-branch>\n```\n\n#### Step 4.3: Create the PR \u002F MR\n\nProduce the PR with this exact title format and body template, regardless of provider:\n\n**Title**: `fix: \u003Cshort description>` (or `feat:`, `refactor:`, etc. per Conventional Commits, unless the project uses a different style — check `git log` for the pattern)\n\n**Body**:\n\n```markdown\n## Summary\n- **Issue**: \u003Cissue-key>\n- **Root cause**: \u003Cthe actual cause in plain language — not the symptom>\n- **Breaking commit**: \u003CSHA and subject of the commit that introduced the bug, e.g. `a1b2c3d \"feat: refactor user loader\"`. If the bug has always existed and is not a regression, write \"always-existed, not a regression\".>\n- **Fix**: \u003Cwhat was changed at a high level>\n\n## Why each change\n\u003CFor every distinct change in the diff, explain the reasoning that links the root cause to this specific modification. Do NOT restate what the diff already shows — explain *why* it had to change. One bullet per logical change. Example: \"`loadUser()` now checks `response.body == null` before dereferencing because the root cause is that the backend returns null bodies when the auth token is stale, which the caller did not anticipate.\">\n\n- \u003Creasoning 1>\n- \u003Creasoning 2>\n\n## Platform\n- **Affected platform**: Android \u002F iOS \u002F both\n- **Min SDK \u002F deployment target affected**: \u003Ce.g. API 24, iOS 15>\n- **New permissions or entitlements**: \u003Clist any, or \"none\">\n\n## Changes\n\u003CFile-by-file factual summary. Keep this factual — what, not why. The \"why\" is already above.>\n- `path\u002Fto\u002Ffile.kt` — \u003Ce.g. \"added null check on `response.body` before `.size()` call on line 42\">\n\n## Test Plan\n- [ ] Unit tests added for \u003Cwhat>\n- [ ] Existing tests pass\n- [ ] Compile check passes\n- [ ] Tested on device \u002F emulator: \u003Cmodel, OS version>\n- [ ] Tested both orientations (portrait & landscape)\n- [ ] Checked dark mode appearance\n- [ ] Accessibility reviewed (TalkBack \u002F VoiceOver, content descriptions)\n- [ ] \u003CManual test steps if applicable>\n\n## Regression Risk\n- [ ] Touches Activity\u002FFragment lifecycle or ViewController lifecycle\n- [ ] Touches threading \u002F coroutines \u002F Dispatchers \u002F GCD\n- [ ] Touches navigation graph or deep links\n- [ ] Modifies ProGuard \u002F R8 rules or iOS build settings\n- [ ] Changes dependency versions\n- **Risk notes**: \u003Cbrief explanation of what could break>\n\n## Screenshots \u002F Evidence\n\u003CIf visual change, add before\u002Fafter screenshots or screen recordings>\n```\n\n**Submit via CLI** if one is installed and authenticated for the provider — pass the title, body, and base branch as arguments so everything is set in a single command.\n\n**Submit via web URL** if no CLI is available. Push the branch first, then build the provider's \"new PR\u002FMR\" URL with source branch and target branch as query parameters. Give the user:\n1. The clickable URL (prefills source and target)\n2. The title to paste\n3. The full body to paste\n\nDo not omit the title or body in the web-URL case — most providers do not auto-populate them from commit messages, and the template is the main value this skill delivers.\n\n### Step 5: Verify\n\nAfter creating the PR:\n1. Verify the diff on the PR looks correct (no unintended files, no secrets)\n2. Report the PR URL to the user\n3. Check CI status if the provider's CLI supports it; otherwise ask the user to confirm the PR was created and CI passed\n\n## PR Title Conventions\n\nFollow [Conventional Commits](https:\u002F\u002Fwww.conventionalcommits.org\u002F) if the project uses them:\n- `fix: resolve crash when opening checkout with zero amount`\n- `feat: add dark mode support to settings screen`\n- `refactor: extract payment logic into separate use case`\n\nIf the project doesn't use conventional commits, follow whatever pattern exists in recent PRs:\n```bash\ngit log --oneline -20  # Check recent commit message style\n```\n\n## Commit Rules\n\n- **Never commit secrets** (.env, `google-services.json`, `local.properties`, signing keystores, API keys). Warn the user if they ask to.\n- **Prefer specific files** over `git add -A` or `git add .`\n- **One logical change per commit** — don't mix unrelated changes\n- **Never force push** unless the user explicitly asks\n",{"name":5,"license":15,"platforms":24,"description":7,"compatibility":30},[25,26,27,28,29],"android","ios","kmp","flutter","react-native",[31,32,33,34],"claude-code","cursor","copilot","codex","main","22db61fe1bb777d1dbf1c3bce1003b60399be288","skills\u002Fcore\u002Fskills\u002Fmobiai-create-pr","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager","https:\u002F\u002Fgithub.com\u002FAdriaanAt","Fun Funny and Insane.","2026-07-10 13:36:44",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add AdriaanAt\u002FEcosystem-Manager --skill mobiai-create-pr",{"tool":48,"command":49},"bunx","bunx skills add AdriaanAt\u002FEcosystem-Manager --skill mobiai-create-pr",{"tool":51,"command":52},"pnpm","pnpm dlx skills add AdriaanAt\u002FEcosystem-Manager --skill mobiai-create-pr","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fcore\u002Fskills\u002Fmobiai-create-pr\u002FSKILL.md",true,[56],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fchangelog.md","REFERENCE","参考文档",1178,"https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fcore\u002Fskills\u002Fmobiai-create-pr\u002Freferences\u002Fchangelog.md",[63,70,77,84,91,98],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M77K38CDKWPD7Q6G1DQ0CXBX","mobiai-react-native","Use when working on a React Native project — building, testing, debugging, understanding navigation and state management.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Freact-native\u002Fskills\u002Fmobiai-react-native\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M77K35JEE16T3ED4GRTVBRFY","mobiai-kmp","Use when working on a Kotlin Multiplatform project — shared code, expect\u002Factual declarations, platform-specific implementations, building and testing.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fkmp\u002Fskills\u002Fmobiai-kmp\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M77K31WB8FTX6MH5J9X7HDD8","mobiai-ios-testing","Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fios\u002Fskills\u002Fmobiai-ios-testing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M77K2XYFPQ48R3Z31F3W6RRK","mobiai-ios-device","Use when interacting with an iOS Simulator — run simctl commands, capture screenshots, read device logs, manage simulators.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fios\u002Fskills\u002Fmobiai-ios-device\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":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M77K2VGTE59KQDMBVRAQ22CN","mobiai-ios-build","Use when building an iOS project, configuring schemes, troubleshooting build failures, or managing dependencies with CocoaPods or SPM.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fios\u002Fskills\u002Fmobiai-ios-build\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M77K2RMDB69MRJZA5V9EBJGQ","mobiai-ios-architecture","Use when creating features, refactoring, or navigating an iOS codebase — understand project structure, find where to make changes, follow existing patterns.","https:\u002F\u002Fgithub.com\u002FAdriaanAt\u002FEcosystem-Manager\u002Fblob\u002Fmain\u002Fskills\u002Fios\u002Fskills\u002Fmobiai-ios-architecture\u002FSKILL.md",[],[]]