Warehouse Mobile App
Customize the D365FO warehouse app / mobile device flows — the stateless screen protocol, the ProcessGuide framework (controller/step/page builder/data processor/navigation agent/action), the legacy WHSWorkExecuteDisplay hierarchy, and the work-execution rules a scanner step must respect. Invoke when the user mentions the warehouse app, mobile device menu items, RF/handheld flows, ProcessGuide, work execution, or scanner screens.
Install
npx skills add dynamics365ninja/d365fo-cli --skill warehouse-mobile-appgit clone --depth 1 https://github.com/dynamics365ninja/d365fo-cli.git /tmp/d365fo-cli
mkdir -p ~/.claude/skills
cp -r /tmp/d365fo-cli/skills/anthropic/warehouse-mobile-app ~/.claude/skills/warehouse-mobile-appPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
> ⛔ **NEVER write X++ AOT XML files directly** via PowerShell, terminal file commands (`Set-Content`, `Out-File`, `New-Item`), editor write tools, or any raw text approach. The XML schema is proprietary. **ALWAYS use `d365fo generate …` commands** to produce correct AOT XML. If `d365fo` is unavailable in PATH, stop and ask the user to install it. # Warehouse app & mobile device flows The warehouse app (and its predecessor, the warehouse mobile device portal) is **not a form**. It is a stateless request/response protocol: the server builds a screen as a container, the device posts the whole screen back, and the next round trip may land on a different AOS. Menu items, menus, app steps and field names are **configured data** — the only AOT surface you customize is the flow-class hierarchy plus the extensible activity enum. Treating a step like a form (member state, form events, direct table writes) is the failure mode this topic exists to prevent. ## 1. Two frameworks — know which one owns the flow FIRST D365FO builds the same mobile screens with **two frameworks**, and picking the wrong one is a rewrite rather than a refactor: - **ProcessGuide** (current) — controller → step → page builder → data processor → navigation agent → action, one responsibility per class, each an extension point. It carries **no WHS prefix** on purpose: production and inventory flows use it too. - **Legacy `WHSWorkExecuteDisplay`** — one `displayForm()` per work-execute
Details
- Skill name
warehouse-mobile-app- Repository
- dynamics365ninja/d365fo-cli
- Path
skills/anthropic/warehouse-mobile-app/SKILL.md- Repo updated
- 16 November 2026
FAQ
What does the Warehouse Mobile App skill do?
Customize the D365FO warehouse app / mobile device flows — the stateless screen protocol, the ProcessGuide framework (controller/step/page builder/data processor/navigation agent/action), the legacy WHSWorkExecuteDisplay hierarchy, and the work-execution rules a scanner step must respect. Invoke when the user mentions the warehouse app, mobile device menu items, RF/handheld flows, ProcessGuide, work execution, or scanner screens.
How do I install the Warehouse Mobile App skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dynamics365ninja/d365fo-cli --skill warehouse-mobile-app. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Warehouse Mobile App popular?
It lives in dynamics365ninja/d365fo-cli, which has 49 GitHub stars and 26 forks.
Related skills
Analytics and Er
49dynamics365ninja/d365fo-cli
Model the D365FO analytical and document-generation surfaces — aggregate measurements and the entity store, tiles/cues and KPIs, and Electronic Reporting (ER). Invoke when the user asks about a workspace tile, a KPI, an aggregate measurement, the entity store, Power BI content, or running/binding an ER format.
Barcode Scanning
49dynamics365ninja/d365fo-cli
Barcodes and scanner input in D365FO — printing vs scanning are unrelated code paths, GS1-128 application identifiers, item-barcode resolution, and where the platform parses a scan for you. Invoke when the user mentions barcodes, GS1, GTIN, SSCC, scanning, scanners, item barcodes, or barcode setup.
Build Error Triage
49dynamics365ninja/d365fo-cli
Turn a D365FO compiler, best-practice, or runtime error into the specific fix it calls for. Invoke when the user pastes a build log, an xppc message, a BP violation, or an infolog stack trace and asks what it means or how to fix it.
Expo API Routes
49robinebers/skills
Guidelines for creating API routes in Expo Router with EAS Hosting
React Native Playbook
49toffyui/ccteams
Operational playbook for Expo + React Native + TypeScript — SDK/workflow detection first, the native escalation ladder, mobile-specific failure catalog (lists, keyboard, safe areas, Expo Go limits), and a two-platform verification recipe. Read in full at the start of every task on this team.
Expo Deployment
49robinebers/skills
Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
Browse the most popular Claude skills, all mobile development skills, or write your own with the skills generator.