com.recipebooq/recipebooq

Tools

• add_screen

  PAID. Add one new screen to an app that was already exported: the screen file, the route that mounts it, the exact line to register it, and how to navigate to it. Reads the .recipebooq/files.json manifest to work out the route tree — it never reads or rewrites your source, so the one edit to an existing file is handed to you as a line to add rather than a file to overwrite.

  shallow
• check_snippet

  Paste TSX that uses these components and get back the glass-safety problems in it — the animated opacity, the flex:1 collapse, the clipped lens, the conditional mount. Read-only: it never touches your repo. A heuristic text scan, not a structural guarantee.

  shallow
• emit_app

  PAID. Turn a recipebooq canvas into a working app: navigation, providers, tab bar, screens and the components they need. Returns a recipe — the exact files with their target paths, the dependency install line, and ordered steps — to apply to the current project. Files marked `skeleton` or `component` are hand-written and device-verified: copy them verbatim, never reformat or rewrite them. Needs the share code from the composer's "Share for agent" button.

  shallow
• emit_screen

  PAID. Turn one composed screen into a real TSX file you can drop into an app you already have — your navigator, your routes. Returns the complete file inline, the components to install first, and how to mount it. Use emit_app instead when the customer wants a whole app with navigation and a tab bar. Needs the share code from the composer.

  shallow
• find_component

  Describe a UI need in plain language and get ranked components — including an explicit answer when this catalog deliberately does NOT ship something and you should use the OS's own control instead. Call this before building any UI control by hand.

  shallow
• get_component

  Everything needed to write a correct call site for one component: props with types, defaults and value domains, platform applicability, dependencies — and the runtime rules that apply to it. Always read the rules; getting props right and rules wrong still ships a blank screen.

  shallow
• get_provider_tree

  The exact app-root provider nesting these components require, in the order that works. Getting this wrong fails at runtime, not at compile time. Optionally pass the components you are using to see which providers they each need.

  shallow
• get_rules

  The runtime rules for this catalog — the mistakes that make native Liquid Glass render blank with no warning, no error and no red box. Pass a slug to scope them to one component. Read these before writing animation or layout code against any glass component.

  shallow
• get_step

  FREE. Expand one step of an emit_app recipe: the full instruction, why it matters, how to know it worked, and what to do when it did not. emit_app returns steps in short form to stay inside the response budget — call this before any step you are not completely sure about. Needs the same share code and the step's id.

  shallow
• get_theme_tokens

  The theme system: which hooks to call, and the spacing, radius and typography scales. Reference token names rather than hex values so a retheme propagates.

  shallow
• install_component

  PAID. Add one component to an existing project, correctly. Returns the transitive registry closure in dependency-first install order, the single `expo install` line for the whole closure, every file with its exact target path, the provider nesting it needs, and the runtime rules for it. Use this instead of fetching /r/*.json by hand — a component is a closure, not a file, and the ways to get that wrong all fail silently. Foundation components need no licence key.

  shallow
• list_components

  List the shipped @recipebooq/ui components — slug, purpose, category, and which are real iOS system controls vs. our own glass. Call this first; it is cheap. Optionally filter by category or tech.

  shallow
• update_components

  PAID. Tell the customer what has changed in their recipebooq files since they exported, and hand back only what moved. Reads the .recipebooq/files.json the export wrote into their project — no share code needed, so it works months later. Never touches their own screens, and flags the rare change that needs a code edit rather than a re-copy. This is how an app stays current as iOS and Android move.

  shallow
• verify_app

  PAID. Check that an emitted app was actually applied correctly, before building it. Report what you wrote — file paths with byte sizes, your package.json dependencies, and the project config — and get back what is missing, which copy-verbatim files were altered, which packages are absent, and whether the config merge that expo-router needs was done. Catches the four ways a long recipe goes wrong, each of which fails silently or points somewhere else.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/1f453eeb-6b06-4d7b-b5dd-a5f8a5bf8c92/badge.svg)](https://vouch.tools/servers/1f453eeb-6b06-4d7b-b5dd-a5f8a5bf8c92)