# Recipes — per-tool snippets and configs

A recipe is **practical configuration and code for a specific tool**. It answers
*"how do I actually set up X to get Y?"* with config blocks, snippets, and the
small set of gotchas that matter. It is not a method explainer or a
quality-dimension overview; those live in [Methods](https://quality.stereobooster.com/methods.md) and
[Quality dimensions](https://quality.stereobooster.com/quality-dimensions.md).

Each recipe is opinionated. A reader should be able to
copy-paste a recipe into a new project and get a working baseline.
The opinions are explicit so they can be
argued with; they aren't presented as universal best practice.

- The **[ESLint](https://quality.stereobooster.com/eslint.md)** recipe sets up ESLint 9 flat config with
  `typescript-eslint`, keeps the logical rules, and leaves formatting to a
  formatter.
- The **[TypeScript](https://quality.stereobooster.com/typescript.md)** recipe turns on the strictness the
  default `tsconfig.json` leaves off.
- The **[Playwright](https://quality.stereobooster.com/playwright.md)** recipe runs whole-system example tests
  in a real browser, with the configuration and CI workflow they need.
- The **[Monocart](https://quality.stereobooster.com/monocart.md)** recipe merges the V8 coverage of several
  test runners into a single report.

## What a recipe is *not*

- Not a tutorial. We assume a reader knows what the tool is for;
  the relevant [Methods](https://quality.stereobooster.com/methods.md) page covers that.
- Not an exhaustive reference. The tool's own docs are exhaustive;
  this is an opinionated condensation.
- Not version-pinned at the project level. Most recipes name the
  major version they target.

## Referenced by

- [Software Quality](https://quality.stereobooster.com/index.md) · Overview