Choose a transformation
Start with the CSV recipe when you have structured text to convert, the API client when you need a response from a service, or the test batch when an implementation already exists. Each route names its runtime and result. Keep a realistic sample nearby so success means something more specific than code that looks plausible.
Read the recipe before starting
Check the required files, data shape, and assumptions. Create a disposable working directory and verify the runtime before generating changes. Ask the assistant to explain missing ingredients instead of inventing an endpoint, schema, or credential. If the task depends on a service, use a saved sample or mock while preparing the local logic.
Finish at the serving check
Run the stated example and compare the output with the expected result. Try the failure case too. Record any intentional limitations before adapting the recipe to a larger project. These recipes teach repeatable coding work; the kitchen language describes preparation and verification, not food ordering or a meal service.
Recipe 01 / Recipe index
Pick the result you want to make.
A code recipe is a complete task with ingredients you can inspect. Choose by the result you need, then work backward to the smallest useful input and implementation.
Recipe 02
CSV to JSON
Preserve text values, validate the rows, and turn a small export into a predictable JSON array.
Python / one JSON array
Open recipeRecipe 03
A small API client
Handle successful JSON, unsuccessful HTTP responses, and a request that takes too long.
JavaScript / one GET function
Open recipeRecipe 04
A focused test batch
Check the client with controlled responses and useful failure cases, without a live service.
Node.js / three behavior checks
Open recipeThe serving check
A good choice has a known input, a bounded implementation, and a result you can verify without trusting the assistant's summary.
A brief for your assistant
Help me choose a coding recipe for this recurring task. Identify the input, expected output, missing assumptions, and one failure case. Keep the first step read-only.
Next at the counterCSV to JSON