Profiles are conservative stack-specific reference snippets for target repositories. They are not automatic migrations and should not replace the target repository's architecture, package manager, docs, commands, or conventions.
Available profiles:
genericpythontypescriptnextjsdjangoflaskfastapispringandroidreactvuego
During prompt-first adoption, agents read profile templates from a local kit clone:
harness-starter-kit/templates/profiles/<profile>/
When the optional installer copies profile snippets, it places them under the target repository for review:
docs/harness/profiles/<profile>/
In both cases, profile snippets are reference material. Agents should adopt, adapt, skip, or defer each snippet based on the target repository's existing tools and maintenance expectations.
A profile may include:
README.mdguidance for the stackcheck_harness.pyor another suggested local verification entrypoint- merge-only config snippets such as
pyproject.harness.toml,package-scripts.harness.json,eslint.config.harness.mjs, orpre-commit-config.harness.yaml gitignore.harness.txtentries for generated files, dependency directories, caches, and local reference clones
Merge-only snippets should be copied into existing target configs only after review. Do not replace target configs wholesale.
If a repository starts with the generic harness and later gains a real stack,
use docs/checklists/profile-absorption.md.
That checklist helps decide which snippets should become real commands, config,
ignores, documentation, or checks.