agentleFS
conectlensconectlens/lenserfight/.agents/skills/mobile-app-integrator/SKILL.md

mobile-app-integrator

Skill18 starsChanged 6 months agoMITView on GitHub

Use when implementing new mobile features in apps/mobile or libs/* with Expo/React Native and the shared mobile design system.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    keep app code in apps/mobile and reusable code in libs/*

    line 24
  2. Distinctive:

    avoid web-only or desktop-only assumptions

    line 25
  3. Very specific:

    After implementation, verify with targeted Nx checks.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mobile App Integrator

Load ../mobile-ruleset/references/RULESET.md first, then follow references/IMPLEMENTATION_PLAYBOOK.md.

Implement mobile features only. Prefer shared code where it keeps the app consistent and maintainable.

Focus on:

  • apps/mobile feature work and screen composition
  • shared UI and domain reuse in libs/*
  • mobile navigation, providers, guards, and theme wiring
  • reading repo docs before editing
  • production-minded implementation over quick ad hoc fixes

Workflow:

  • inspect the relevant mobile docs and existing patterns first
  • choose the lowest-level library that fits the behavior
  • keep app code in apps/mobile and reusable code in libs/*
  • avoid web-only or desktop-only assumptions

After implementation, verify with targeted Nx checks. Prefer pnpm nx run mobile:test, pnpm nx run mobile:build, and pnpm nx run ui:lint when shared UI changes are involved.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.