- Home
- Skills
- Mobile Development
- ALEConnect Mobile Builder
ALEConnect Mobile Builder
Build branded React Native apps with precise prompts, API contracts, durable offline flows, and practical delivery checks.
$2.49
Works with the AI Agents you already use
ALEConnect Mobile Builder
Example session with this skill installed
Use ALEConnect Mobile Builder to plan an Expo app called LightLink for residents to report streetlight faults. Include up to three photos, a map point, saved drafts, and report status. The brand should feel calm and dependable. Keep payments and staff dispatch outside this release. Produce a complete first-release plan with screen states, API ownership, design direction, implementation slices, and acceptance criteria. Do not write code yet.
- Read your context and instructions
- Compiled the aleconnect mobile builder
LightLink: first-release plan
Deliver one complete flow: compose a fault report, save it locally, send it deliberately, receive a server receipt, and track its current status. This is a planning example; no app was built or device-tested for this demo.
Assumptions
Residents sign in and have one active service account. The backend owns authorization, report IDs, status transitions, and attachment access. Confirm account-linking policy before implementation. Saved drafts do not automatically send in this release.
Screens and states
| Screen | Primary behavior | Required states |
|---|---|---|
| Reports | View account-scoped reports and open details | Loading, empty, cached/offline, refresh failure |
| New report | Enter a description, select a map point, attach 0–3 photos | Validation, permission denial, picker cancellation, local-save failure |
| Drafts | Resume or deliberately delete a local draft | Empty, saved timestamp, original account unavailable |
| Report detail | View receipt, current status, and evidence | Loading, not found/unauthorized, stale cached view, refresh failure |
Data and API contract
Mobile persists draft text, coordinates, owned local attachment references, original account identity, and update time before showing “Saved on this device.” Validate the same agreed description and attachment bounds on client and server; proposed limits must be confirmed with the backend.
POST /reports accepts an authenticated, account-scoped payload and stable clientMutationId. The server validates evidence ownership and permissions and returns { report: { id, status, createdAt }, receiptId }. Exact replay of the same mutation returns its prior receipt; reuse with a changed payload returns a conflict. This contract is proposed and must be agreed before coding.
GET /reports and GET /reports/:id return only records the current actor may access. The server controls canonical status. Cache keys include identity and account. After an account switch, ignore late responses from the previous scope and keep its drafts isolated.
A failed send retains the editable draft and files. After a lost response, retry/reconcile with the same mutation ID. Retain the accepted receipt before cleanup. Local-only drafts must never appear as “Submitted.”
Brand and interface direction
Use a calm civic-service identity: neutral surfaces, one accessible blue action color, clear status labels, and restrained illustration. Final color pairs need contrast checks. Use the existing component library if one exists. For a new app, begin with a 4-point spacing scale, 16-point content gutters, a readable body face, and a small title/body/metadata hierarchy; adjust against actual screens.
Keep report title and status easy to scan. Support light/dark themes, font scaling, real safe areas, and platform-appropriate touch targets. Permission-denied copy offers a useful manual path. A selected map coordinate corresponds to the pin tip in both picker and detail views.
Implementation slices
- Agree the identity, report, attachment, idempotency, and receipt contracts; create representative fixtures.
- Build navigation and the token-based screen shell with loading/empty/error states.
- Implement account-scoped durable drafts and attachment retention; verify restart and local-write failure.
- Integrate explicit submission, receipt persistence, and lost-response reconciliation.
- Integrate report list/detail refresh and scoped caching; finish native and accessibility checks.
Acceptance criteria
- A saved draft survives app restart with its text, point, and attachment references.
- Failed persistence shows an error and retains form input.
- Sending the same mutation twice creates one server report.
- A timeout after acceptance can recover the original receipt.
- Switching accounts does not display or submit another account's work.
- Denied photo/location permission leaves a useful recovery path.
- A failed initial load is distinguishable from an empty list; failed refresh retains labelled cached data.
- Small screens, large text, keyboard, and both themes remain usable.
Next step and evidence needed
Confirm account-linking and backend constraints, then implement slice 1. Source checks and browser layout previews will be useful during development. Android and iOS camera, location, file persistence, and lifecycle behavior still need matching native builds and device checks. Payments and dispatch remain outside this release.
Connects securely to your tools. The creator never sees your data.
About this skill
Build mobile apps with a clearer engineering workflow
ALEConnect Mobile Builder turns a product brief into a practical React Native and Expo feature: a clear user flow, an explicit mobile/server contract, a branded interface, and an implementation backed by appropriate evidence.
It distills reusable development lessons from ALEConnect Mobile, a consumer service app for reports, advisories, account information, and hotlines.
What you get
- A complete SKILL.md covering product slicing, API ownership, account-scoped state, durable drafts and queues, native integrations, and delivery checks.
- Seven reusable prompt recipes for planning, implementation, branded screens, offline submissions, shared cards, cross-project features, and readiness review.
- Design guidance for semantic tokens, typography, spacing, shared components, safe areas, large text, and light/dark themes.
- Practical rules for avoiding duplicate submissions, lost attachments, stale account data, and unsupported release claims.
Best for
Developers, solo builders, and small teams using AI coding agents to build or refine service apps, community apps, reporting tools, and other mobile products with real data and native features.
How to use it
Load the skill using your agent's supported skill mechanism, then describe the desired outcome, relevant repository, constraints, and acceptance criteria. Ask for a plan or an implementation. The skill adapts to your existing stack and brand.
Scope
This is an instructional skill package. It includes no ALEConnect application source, private data, credentials, brand assets, hosted backend, or paid tool access. It requires a capable agent and your own project/toolchain for implementation. Results depend on the supplied context and agent; browser previews and builds do not establish native device acceptance.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.
Instructional workflow, not a complete application or source-code template. Best aligned with React Native and Expo. Implementation needs project context and appropriate tools. No guarantee of agent output, app-store acceptance, native/provider behavior, performance, or commercial results. Compatibility has not been comprehensively tested across all agents. The demo is a planning example, not a shipped application.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
- Software
Node.jsReact NativeExpo
DeviceoremulatorNative build toolchain
Use the project's compatible versions for implementation. The device or emulator and build toolchain are for native acceptance.
Permissions
Planning can use supplied context alone. Repository reading, file edits, and shell commands are used when implementing or validating a requested change. Documentation lookup or dependency installation may require network access. No connected service account is intrinsically required. This skill does not grant permission to deploy, publish, erase device data, or modify production systems.