Mealio Developer SKILL.md
Give this one file to your coding agent. It learns how your app is built, asks you a few design questions, then adds Mealio so it looks like your own team built it.
Works with Claude Code and any agent that can read your files. For React Native, Expo, iOS, Android and Flutter apps.
Download the skill
In Claude Code, run this from the root of your app:
curl -fsSL --create-dirs -o .claude/skills/mealio-integrate/SKILL.md https://developers.mealio.co/SKILL.mdUsing a different agent? Save the file wherever it keeps skills. If it has no skills folder, skip this step. Your agent can read the file from our site in step 2.
Start it
Open your agent at the root of your app and run the skill:
/mealio-integrateOn any other agent, paste this:
Read https://developers.mealio.co/SKILL.md and follow it to add Mealio to this app.Answer its questions
Your agent changes nothing at first. It reads the Markdown files in your repo, from README.md and CLAUDE.md to your architecture notes. Then it maps your screens, recipe model, sign-in, server and design tokens, and tells you what it found.
Here is how I understand your app.
Platform: Expo, new architecture, dev builds in use
Recipes: src/types/recipe.ts, with stable ids
Screens: RecipeScreen, HomeScreen, PlanScreen
Design: src/theme/tokens.ts, dark mode on
A few questions. Say "go with your picks" to take them all.
1. Where should the button go?
I recommend RecipeScreen, next to the ingredients,
plus one button on PlanScreen for the whole week.
2. Which button?
I recommend your shared <Button>, so it matches.It only asks what your code cannot answer.
| It works out | It asks you |
|---|---|
| Your platform and how to install the SDK | Drop-in sheet or your own screens |
| How your recipes map to Mealio | Which screens get the button |
| Colors, corners and fonts from your tokens | One cart per recipe, or one from a whole meal plan |
| Which user id to use | What guests see |
| Sign-out and account deletion | Whether carts are part of a paid plan |
Then it writes a plan into your repo. You read it and change anything you like. No code gets written until you approve it.
Watch Mealio land in your app
Your agent builds what you approved, checking its work as it goes:
- The one endpoint your server needs
- The SDK, set up at the root of your app in your colors
- A small function that turns your recipes into Mealio recipes, with tests
- The button on the screens you chose
- The extras you asked for, like analytics, store settings and translated text
It finishes with a short test to run on a real phone and a go-live checklist. Then your users can fill their grocery cart from your recipes.
Prefer to do it by hand? The quickstart covers the same steps.