Recipe 06 / Mise en place

Everything in its place.

Mise en place means preparing the materials before the work begins. For coding, that means a runnable project, an honest example, and a clear boundary for the assistant.

Result: A prepared coding sessionGo to method
  1. Check the workspace

    Open a sample repository or a disposable copy. Run its existing command or tests so you know the starting state. Identify the entry point and any required configuration. Keep production credentials and private exports out of the first fixture. A failure that already exists should be recorded before generated changes enter the picture.

  2. Set out the model arrangement

    Confirm who operates the endpoint, the exact model identifier, and the API format the application expects. Record the connection details without placing secrets in prompts or source files. Model behavior and available tools depend on the chosen setup. A local endpoint does not automatically make external connectors local as well.

  3. Ask for an inspection

    Begin by asking the assistant to explain the project's input-to-output path without changing anything. Compare its account with the files you can read. If it invents functions or skips an important assumption, correct the context before moving on. A narrow, understood task is a better starting point for a recipe than an open-ended request to improve everything.

The serving check

The project runs, the fixture represents the task, and the assistant can explain the relevant path before editing it.

A brief for your assistant

Inspect this project and its sample input. Explain the entry point, transformation, and output. Identify missing configuration and one failure case. Do not edit files, run writes, or install dependencies.

At the workspace

Reference workspace showing a coding conversation and model selector. Available actions depend on the final application and configuration. Reference desktop preview; final product screens may differ.
Next at the counterRecipe index