For capable collaborators

The App Jam
builder kit.

Build, deliver, and evolve a personal app. No private repository or prior chat history needed.

Read the builder skill ↗Download portable skill ZIP ↓Client connection recipes ↗Service metadata ↗

Connect with account authorization.

MCP endpoint: https://oneapp-prototype.vercel.app/mcp. Use remote MCP and normal account OAuth. Customers do not enter relay addresses or admin tokens on their phones. Inspect the existing connection before adding a duplicate. Follow the client’s own supported configuration and reload steps.

Start with live tools, the host catalog, and capability discovery. Documented setup recipes are not universal client compatibility evidence. Never request passwords, plaintext provider keys, tokens, or recovery kits in hosted tool arguments.

Author against real contracts.

Complete authoring guide ↗Package JSON schema ↗Build-time capabilities ↗Engineering sample catalog ↗Read an installed app’s source ↗Backup and restore boundaries ↗

Native apps use bounded built-in actions and declarative trees; never downloaded React Native JavaScript. Packaged HTML apps use isolated browser storage without the development bridge. Discover host adapters and permission support before promising a feature. Build local-first, keep credential values on-device, and preserve app identity, schemas and saved records during updates.

Remix a showcase copy.

The person signs in, chooses a showcase app, and adds one stable account-specific copy to an enrolled phone. A fresh account has no preinstalled collection. Read the installed clone through read_experience_package with packages:read authorization. Keep its experienceId, runtime, existing table IDs and storage names; use its actual revision as baseRevision. Never republish the public template over an edited clone.

The source read waits for foreground phone synchronization. Follow chunk hashes and expected revision checks in the source-handoff guide. The public showcase catalog provides ideas and remix prompts, not access to personal app records or source.

Publish, then report the real status.

Validate the package and assets. Publish immediately when authorized, even if the phone is closed or a newer host is required. A receipt can say queued and awaiting host; install the compatible host and open it online. No extra chat confirmation is required. Do not equate queued delivery with installation, or technical checks with Apple review.

Try the original authoring exercise.

The legacy learning exercise remains available for testing discovery, questions and source generation. It has no completed Chinese curriculum or imported vocabulary bundled.

Copyable user request

Help me build a personal Chinese vocabulary app inside App Jam. You do not need any earlier chat history or the host repository. Start by reading https://oneapp-prototype.vercel.app/oneapp-builder/SKILL.md and https://oneapp-prototype.vercel.app/service.json , following the skill's relevant references. This is a first-time bootstrap: do not assume App Jam is already connected. Inspect this client's existing MCP configuration and available tools. If App Jam is missing, follow the hosted connection recipe for this client to add the metadata's MCP endpoint and use its supported normal OAuth sign-in. If you cannot configure MCP from this session, give me the exact supported client command/settings step. If a client restart/reload is required, say so and tell me how to resume; do not pretend an unavailable tool exists.

Once connected, discover the actual App Jam tool catalog, package schema, capabilities, device list, authoring resources, current app/table catalog, and available example apps. Read relevant full example packages before choosing an implementation. If the portable oneapp-builder skill is available for invocation, use it.

Use normal App Jam account OAuth sign-in when needed. Do not ask me for a relay URL, owner/admin token, MCP bearer token, or AI-provider key to build and publish this app. The operator supplies the service endpoint through the connection kit. After discovery, ask a few plain-language questions before building: confirm any missing source permission, how I want to practice, and any offline requirement not already answered here. Ask which device only if ambiguous. Recommend useful defaults and explain meaningful tradeoffs; do not make me choose APIs, backends, or frameworks. Briefly describe your proposed experience and any real limitations before authoring it.

The source I am supplying is https://duome.eu/vocabulary/en/zs/skills . Inspect its actual vocabulary/section structure and applicable access/use restrictions, and preserve source/section provenance. Ask for an authorized export if direct access is unavailable. Do not substitute a sample deck or claim you imported this page without doing so. Support quizzes for one section, a section range, and all words through section N. Save quiz runs, every answer/correctness, scores and history. Include a review of incorrect items and keep prior attempts after later correct answers. Work offline after installation/import, resume an unfinished run, and preserve history and the last working app across updates. Keep learning history on-device by default, explain any data that would leave the device, and do not publish my vocabulary or results publicly. A simple multiple-choice quiz can grade locally and needs no paid AI API.

Do not assume native flashcards or matching components provide range quizzes or attempt history. Discover what the installed host really supports. If native primitives cannot deliver the complete behavior, recommend a locally packaged HTML quiz with persistent local data, or explain what platform upgrade would be needed. Confirm any material compromise before building. Do not modify App Jam's host screens, load a downloaded React Native bundle, invent unsupported props, generate a separate Next.js/Swift/Expo project, or disguise a demo as a newly published app.

Use stable experience/table identities, compatible schemas and the current base revision. Publish the validated app through the actual service immediately; do not wait for me to confirm that I opened or upgraded App Jam. Inspect the operation acknowledgement and distinguish queued from applied. If installation is awaiting_host, tell me to install the required App Jam update and open it online. Compatible queued apps install automatically on opening; no further chat confirmation is needed. If the phone is unavailable, report the queued operation rather than claiming installation. Explain exactly what was tested and any remaining offline, device, or App Store limitations.

Open the exercise as Markdown.

Complete engineering examples.

These twelve original platform fixtures have native and web variants. They are source examples for agents. Provider integrations require their own setup; mock output must never be described as a successful live call.

Little LanguageTurn a section of vocabulary into a pocket practice session.native package · web package
Out ThereLeave the signal behind, keep the route with you.native package · web package
Good PlateA food diary built around the way you actually eat.native package · web package
Worth a LookAn agent-built camera app with your own AI model.native package · web package
Match DayMake the smallest scoreboard you actually need.native package · web package
One Good MoveA lesson a day, written for your next good move.native package · web package
Your DayLet your agent bring the pieces of your day together.native package · web package
Field NotesYour itinerary, packing list, and memories in one place.native package · web package
Paper TrailCapture a receipt before it disappears in your pocket.native package · web package
A Gentle NudgeA thoughtful reminder from a tool you made.native package · web package
Find Your LevelLine up a photo with a tiny motion-powered level.native package · web package
Cloud PocketSign in once and bring useful files along.native package · web package

Direct links are publicly readable. Search indexing controls do not restrict access. No secrets, personal records, private vocabulary imports or licensed financial datasets belong in this kit.

Agent link index · Artifact checksums · Build provenance

The App Jambuilder kit.