The workflow passed static publication checks, but download remains disabled until its license and final release manifest are approved.
The outcome
Maintain commercial rationale, product intent, architecture, UX completeness, project-bound tooling, release identity, production diagnosability, channel truthfulness, and operating evidence across the entire mobile-app lifecycle without fragmenting the user-visible capability.
Use it when
- Use when a user wants to determine whether a mobile-app idea is commercially credible and then take it through complete implementation and the selected release channels.
- Use when an existing app must resume from product redesign, implementation, testing, release, submission, rejection, or post-launch iteration.
- Use when one durable workflow must coordinate business evidence, UX, engineering, commercial readiness, release evidence, and App Store review when iOS distribution is selected.
- Use when a commercial app must include release-aware, privacy-safe production diagnostics and operations evidence rather than shipping with only local tests or anecdotal support feedback.
It does not do
- Does not replace the user’s final authorization for project scope, account access, external changes, or business consequences.
- Does not represent repository static checks as runtime certification across every platform, provider account, or production environment.
Inputs
- Mobile-app idea or existing project, customer intent, constraints, target users, platforms, release channels, delivery context when selected, brand context, and available evidence.
- Approved decisions, repository state, relevant distribution-account context, and credentials supplied only through protected runtime channels when required.
- Critical journeys, privacy classifications, observability provider/storage choices, app and release identity, backend dependencies, central-operations requirements when applicable, alert ownership, and the requested observability stop state.
Outputs
- Approved commercial case, product baseline, prototype, implementation plan, commercial-quality source, tests, release artifacts, and traceable lifecycle records.
- Truthful selected-channel records and metadata, verified release or review-resolution state, and evidence-backed continue, narrow, pivot, or stop recommendations.
- A project-specific observability contract and verified evidence at the approved stop state, with unavailable, partial, stale, and production-verified states kept distinct.
Natural-language triggers
Use $xiaoyue-create-app to turn this idea into a commercial iOS app and take it through App Store review.
Use $xiaoyue-create-app to resume this existing Flutter app from its UX audit, keeping Flutter project-bound through FVM.
Use $xiaoyue-create-app to prepare this app for release, including privacy-safe production observability and verified failure diagnosis.
Permission map
Environment & requirements
Agents
- Codex
- Claude Code
Platforms
- macOS
- Linux
- Windows
Required tools
- Git
- target mobile toolchain
- selected distribution platform
Data handling
May process project source, build logs, store metadata, and authorized distribution-account state; credentials must remain in existing secure channels.
Credential handling
Uses only existing secure credential channels authorized by the user; tokens, keys, cookies, private keys, and real user data must not be copied into the Skill, logs, reports, or public artifacts.
Verification evidence
Passed repository structure, bilingual metadata, and reference checks; this Skill has not entered candidate-artifact generation or runtime verification.
- Level
- Checked
- Checked
- 2026-10-12
- Expires
- 2027-01-10
- Source revision
fac86e9d2646
Environment
- Repository structure and metadata validation on macOS
Targets checked
- source metadata
- package structure
Evidence IDs
public-catalog-schema-v3source-repository-validation
Limits & support
Known limitations
- The current verification level is a repository static check, not an end-to-end validation against a real provider account, physical device, or production environment.
- Agents, platforms, and provider interfaces continue to change; each run must inspect current state and respect explicit confirmation gates.
Permission changes
- No permission change is declared for this release; for a first public release, the permission map on this page is authoritative.
Channel
Submit through support@xiaoyuelabs.com or the on-site inquiry form.
Response target
Receipt is acknowledged within two business days; remediation timing is confirmed after reproduction and scope review.
Scope
Free support covers download integrity, documentation errors, and reproducible Skill defects; project adaptation, managed operation, and ongoing maintenance are separate services.
Release notes
- Added production observability as an explicit commercial lifecycle stage covering critical journeys, trusted app/release identity, correlated errors and backend requests, crash/performance evidence, alerts, and recovery verification.
- Added project-selectable app-owned, managed-provider, direct-central, and hybrid observability decisions without hard-coding a database, provider, consent model, or operating topology.
- Expanded implementation plans, development guidance, project state, commercial standards, and readiness evidence so an app cannot be called release-ready when material production failures are not attributable at the approved observability stop state.
- Added an evidence-backed commercial-case stage covering alternatives, acquisition, operating economics, validation signals, and explicit continue, narrow, pivot, or stop conditions.
- Changed decision guidance so the agent gives a clear professional recommendation while reserving material scope, cost, privacy, lock-in, brand, legal, and experience choices for user confirmation.
- Made delivery context selectable as solo, team, client, or undecided; solo-developer capacity constraints now apply only when that context is selected instead of being a universal requirement.
- Added release-channel routing so App Store procedures run only for iOS distribution in scope, while other channels require current official evidence and honest verification status.
- Expanded implementation, commercial-readiness, and production-insight records with operating costs, supplier outage behavior, channel consistency, and post-launch business decisions.
- Consolidated the previously separate Xiaoyue app-lifecycle skills into one user-confirmed, end-to-end app-creation capability.
- Preserved progressive stage guidance for product discovery, UX and prototyping, implementation planning, commercial development, independent testing, release preparation, App Store setup and submission, review resolution, and production learning.
- Kept Flutter versions project-bound through FVM and left monetization, StoreKit versus RevenueCat, AI, backend, analytics, and other providers as project decisions.
Install & verify
Available for evaluation, not yet packaged
This workflow is listed so its scope, permissions, and service fit can be evaluated. It has not entered the first downloadable release batch and no public artifact exists.