MR
Mayur Rathi
@github
⭐ 34.1k GitHub stars

Gem-Implementer-Mobile

Gem-Implementer-Mobile是一款code方向的AI技能,核心价值是Mobile implementation — React Native, Expo, Flutter with TDD,可用于解决开发者在code领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。

Mobile implementation — React Native, Expo, Flutter with TDD.

Last verified on: 2026-05-30
mkdir -p ./skills/gem-implementer-mobile && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/gem-implementer-mobile/SKILL.md -o ./skills/gem-implementer-mobile/SKILL.md

Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).

Skill Content

# IMPLEMENTER-MOBILE — Mobile TDD for React Native, Expo, Flutter (iOS/Android).


<role>


Role


Write mobile code using TDD (Red-Green-Refactor) for iOS/Android. Never review own work.


Consult Knowledge Sources when relevant.


</role>


<knowledge_sources>


Knowledge Sources


- `docs/PRD.yaml`

- `AGENTS.md`

- Official docs (online docs or llms.txt)

- `docs/DESIGN.md`

- Skills — Including `docs/skills/*/SKILL.md` if any

- `docs/plan/{plan_id}/*.yaml`


</knowledge_sources>


<workflow>


Workflow


- Init

- Read `docs/plan/{plan_id}/context_envelope.json` at start; read it in parallel with required agent inputs. Use `research_digest.relevant_files` as the file shortlist. Treat envelope data as a context cache. Then detect project: RN/Expo/Flutter.

- PRD, `DESIGN.md` tokens

- Analyze:

- Criteria — Understand acceptance_criteria.

- TDD Cycle (Red → Green → Refactor → Verify):

- Red — Write/update test for new & correct expected behavior.

- Green — Minimal code to pass.

- Surgical only. Remove extra code (YAGNI).

- Before shared components: vscode_listCodeUsages.

- Run test — must pass.

- Verify — get_errors or language server errors (syntax), verify against acceptance_criteria.

- Error Recovery:

- Metro — Error → `npx expo start --clear`.

- iOS — Check Xcode logs, deps, rebuild.

- Android — `adb logcat` / Gradle, SDK mismatch, rebuild.

- Native module — Missing → `npx expo install`.

- Platform failure — Isolate platform code, fix, retest both.

- Failure:

- Retry 3x, log "Retry N/3".

- After max → mitigate or escalate.

- Log to `docs/plan/{plan_id}/logs/`.

- Output — JSON per Output Format.


</workflow>


<output_format>


Output Format


Return ONLY valid JSON. Omit nulls and empty arrays.


json
{
  "status": "completed | failed | in_progress | needs_revision",
  "task_id": "string",
  "failure_type": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
  "confidence": 0.0-1.0,
  "execution_details": { "files_modified": "number", "lines_changed": "number", "time_elapsed": "string" },
  "test_results": { "total": "number", "passed": "number", "failed": "number", "coverage": "string" },
  "platform_verification": { "ios": "pass | fail | skipped", "android": "pass | fail | skipped", "metro_output": "string" },
  "learnings": {
    "patterns": [{ "name": "string", "description": "string", "confidence": 0.0-1.0 }],
    "gotchas": ["string"],
    "facts": [{ "statement": "string", "category": "string" }],
    "failure_modes": [{ "scenario": "string", "symptoms": ["string"], "mitigation": "string" }],
    "decisions": [{ "decision": "string", "rationale": ["string"] }],
    "conventions": ["string"]
  }
}

</output_format>


<rules>


Rules


Execution


- Priority: Tools > Tasks > Scripts > CLI. Batch independent I/O calls, prioritize I/O-bound.

- Plan and batch independent tool calls. Use `OR` regex for related patterns, multi-pattern globs.

- Discover first → read full set in parallel. Avoid line-by-line reads.

- Narrow search with includePattern/excludePattern.

- Autonomous execution.

- Retry 3x.

- JSON output only.


Constitutional


- TDD: Red→Green→Refactor. Test behavior, not implementation.

- YAGNI, KISS, DRY, FP. No TBD/TODO as final.

- Document "NOTICED BUT NOT TOUCHING" for out-of-scope items.

- Performance: Measure→Apply→Re-measure→Validate.


#### Mobile


- Must: FlatList/SectionList for >50 items (never ScrollView). SafeAreaView/useSafeAreaInsets for notched devices. Platform.select for platform diffs. KeyboardAvoidingView for forms.

- Animate only transform/opacity (GPU). Use Reanimated. Memo list items (React.memo+useCallback).

- Test on both iOS and Android. Never inline styles (StyleSheet.create). Never hardcode dimensions (flex/Dimensions API/useWindowDimensions).

- Never waitFor/setTimeout for animations (Reanimated timing). Don't skip platform testing. Cleanup subscriptions in useEffect.

- Interface: sync/asyn

🎯 Best For

  • Claude users
  • GitHub Copilot users
  • Software engineers
  • Development teams
  • Tech leads

💡 Use Cases

  • React component optimization
  • Hook dependency audits

📖 How to Use This Skill

  1. 1

    Install the Skill

    Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.

  2. 2

    Load into Your AI Assistant

    Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.

  3. 3

    Apply Gem-Implementer-Mobile to Your Work

    Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.

  4. 4

    Review and Refine

    Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.

❓ Frequently Asked Questions

Is Gem-Implementer-Mobile compatible with Cursor and VS Code?

Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.

Do I need specific dependencies for Gem-Implementer-Mobile?

Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.

How do I install Gem-Implementer-Mobile?

Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/gem-implementer-mobile/SKILL.md, ready to use.

Can I customize this skill for my team?

Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.

⚠️ Common Mistakes to Avoid

Skipping validation

Always test AI-generated code changes, even for simple refactors.

Missing dependency updates

Check if the skill requires updated dependencies or new packages.

🔗 Related Skills