Add a recipe
Each recipe is one Markdown file in src/recipes/. The file name becomes the URL, so connect-android-emulator.md is served at /r/connect-android-emulator/. Commit the file and the site rebuilds itself.
1. Frontmatter
src/recipes/your-recipe.mdYAML
---
title: Connect your desktop to an Android emulator with adb
summary: One or two sentences shown on the card and under the title.
category: Mobile dev # groups recipes into the filter chips
tags: [android, adb, emulator]
difficulty: Beginner # Beginner | Intermediate | Advanced
time: 15 min
os: [linux, macos, windows] # which OSes the recipe covers
verified: 2026-11-04 # date you last checked the commands
featured: true # optional, sorts it first
prerequisites:
- Android Studio installed
variables: # optional fill-in values
- key: SERIAL # use it as {{SERIAL}} inside code blocks
label: Emulator serial
default: emulator-5554
hint: From adb devices
sources: # at least one official source
- title: Android Debug Bridge (adb)
url: https://developer.android.com/tools/adb
publisher: Android Developers
date: July 2026 # optional: date of the source itself
---2. Steps and command blocks
BodyMarkdown
Short intro paragraph (shown above step 1).
## Install the tool <- every ## heading becomes a numbered step
```bash linux,macos <- language, then the OSes it applies to
adb -s {{SERIAL}} shell
```
```powershell windows
adb -s {{SERIAL}} shell
```
```bash <- no OS listed = same command everywhere
adb devices -l
```
```output <- expected output (not copyable)
{{SERIAL}} device product:...
```
> **Tip:** blockquotes become highlighted notes.
## Troubleshooting <- "Troubleshooting", "Next steps", "Clean up",
"Going further" and "Undo" are not numbered3. Rules of thumb
- One action per step. Show the expected output so people know it worked.
- Give every OS a command, or say clearly when a step doesn't apply. The page shows "Nothing to run on Windows" automatically.
- Only use commands you checked against an official source, and list that source with a date.
- Warn before anything destructive (
kill -9,rm,-wipe-data). - Run
npm run check:recipesbefore opening a pull request.