AtomaLive showcase
← All finished work

Node.js recipe scaling and shopping list tool

Software2 deliveries8 min 55 s in total$0.23 in total

Step 1 of 2

The request

Node.js recipe scaling and shopping list tool

Read the full request

Build a self-contained Node.js command-line application for scaling recipes and consolidating a shopping list. Use one documented JSON input file containing recipes with id, name, original servings, and ingredients (name, numeric quantity, unit), plus a plan listing each selected recipe id and desired servings. The CLI reads that file, scales quantities by desired/original servings, combines entries only when normalized ingredient name and unit match, sorts output deterministically, and prints a JSON shopping list. Refuse malformed JSON, unknown recipe ids, non-positive servings or quantities, and unsupported units with actionable errors. Include a small example input, README usage, and automated tests for scaling, consolidation, unit separation, and invalid inputs. Use only local files and no external service or API. Do not modify mgtf/atoma.

The journey

  1. Read the requestTurned it into a list of things it would have to prove before calling the work done.
  2. Did the workPlanned the pieces, built them and checked the result as it went.
  3. Delivered5 files handed over.

The result

  • example.json647 B
  • index.js4.2 KB
  • package.json244 B
  • README.md1.2 KB
  • test.js2.1 KB
Time4 min 16 s
Cost$0.05
Finished2026-10-06

Step 2 of 2

The request

Write user guide for recipe scaling tool

Read the full request

Continue the existing recipe scaling and shopping list tool from its delivered workspace. Do not change the tool's behaviour. Write a user guide as docs/USER-GUIDE.md that explains, from the actual source and the existing README, the JSON input format with one complete annotated example, every command and option the tool accepts with its exact output for the bundled example data, how quantities are rounded and units consolidated, and the error messages a person can meet and what to do about each. Every command and output in the guide must be verified against the real tool before being written down, and the README gains a short link to the guide. Completion is observable by following the guide from a clean checkout and seeing the documented outputs.

The journey

  1. Read the requestTurned it into a list of things it would have to prove before calling the work done.
  2. Did the workPlanned the pieces, built them and checked the result as it went.
  3. Delivered6 files handed over.

The result

  • docs/USER-GUIDE.md8.5 KB
  • example.json647 B
  • index.js4.5 KB
  • package.json244 B
  • README.md1.6 KB
  • test.js3.0 KB
Time4 min 39 s
Cost$0.18
Finished2026-10-10

Have a request of your own?

Describe the outcome you want. Atoma works on it in a private project and gives you the same story: every step, every check, and the finished result.

Start your own