# profiles/

Optional profiles adapt A2C defaults for specific contexts.

## Stack profiles

Stack profiles adapt repository structure, templates, rules, and tooling expectations to common technology stacks. They are **optional** — a docs-only or mixed project can adopt A2C without a stack profile.

| Profile | Stack |
|---------|-------|
| [python/](python/) | Python package (src layout, Ruff, pytest) — `a2c bootstrap --profile python` |
| [python-pypi/](python-pypi/) | Publishable Python package — composes `python` + release scripts |
| [cpp-cmake-conan/](cpp-cmake-conan/) | C++ / CMake / Conan |

## Task body profiles

Task body profiles (`task-body/`) define the expected `##` sections for planning task Markdown bodies. See [task-body/README.md](task-body/README.md).

Stack profiles define:

- expected repository structure extensions
- template and rule overlays
- shared pre-commit configuration expectations for the stack
- CI and documentation expectations
- prompt hints for bounded implementation

See [docs/workflow/reuse.md](../docs/workflow/reuse.md) for how to select and adapt a stack profile.