id stringlengths 10 17 | locale stringclasses 4
values | title stringlengths 2 14 | slug stringclasses 8
values | sectionCode stringclasses 8
values | order int64 0 7 | canonicalUrl stringclasses 8
values | sourcePath stringlengths 21 28 | summary stringlengths 29 162 | llmSummary stringlengths 42 282 | content stringlengths 321 49.5k | text stringlengths 361 49.6k | sourceCommit stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
en/overview | en | Overview | overview | 00 | 0 | https://www.harnessconfig.dev/specifications/v1/ | spec/en/00-overview.md | The source layout, activation model, projection controls, profile overlays, target-local controls, and practical operating benefits in one read. | Introduces .harness as a repository-owned source catalog for agent configuration, with dry-run activation, composable instruction files, profile overlays, target-local controls, and explicit runtime projections that make advanced configuration predictable, reviewable, and reusable. | # A neutral source layout for harness surfaces
Harnesses expose live files and folders such as `AGENTS.md`, `.agents`, `.claude`, `.gemini`, and `.cursor`. Those files and folders are useful harness surfaces, but they are a weak source of truth when several tools need the same skills, rules, plugins, and instruction f... | Overview
The source layout, activation model, projection controls, profile overlays, target-local controls, and practical operating benefits in one read.
# A neutral source layout for harness surfaces
Harnesses expose live files and folders such as `AGENTS.md`, `.agents`, `.claude`, `.gemini`, and `.cursor`. Those f... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/rationale | en | Rationale | rationale | 01 | 1 | https://www.harnessconfig.dev/specifications/v1/rationale/ | spec/en/01-rationale.md | Why the standard separates a durable source catalog from live harness surfaces. | Explains why live harness surfaces should be derived outputs while .harness remains the reviewable source of truth, including profiles, target-output controls, and composable instruction files. | # Harness config rationale
Harnesses need live repository surfaces. Teams need a stable, reviewable source
layout for the resources those harnesses consume. Harness config separates
those responsibilities without prescribing an application model for either.
The source catalog lives under configured source roots, with... | Rationale
Why the standard separates a durable source catalog from live harness surfaces.
# Harness config rationale
Harnesses need live repository surfaces. Teams need a stable, reviewable source
layout for the resources those harnesses consume. Harness config separates
those responsibilities without prescribing an... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/standard | en | Standard | standard | 02 | 2 | https://www.harnessconfig.dev/specifications/v1/standard/ | spec/en/02-standard.md | Normative definitions for terms, repository shape, TOML, projection, overrides, ignores, profiles, extensions, and conformance. | Defines the .harness repository shape, TOML contract, activation projection, target-derived overrides, ignore precedence, profile overlays, extension declarations, and conformance boundaries. | # Harness config standard
**Status:** Version 1 — Stable. The file shape, manifest schema, projection
contract, and ignore grammar described here are intended to be implementable
without consulting the reference code. Changes that would invalidate a v1
repository or v1 implementation are reserved for v2.
Harness conf... | Standard
Normative definitions for terms, repository shape, TOML, projection, overrides, ignores, profiles, extensions, and conformance.
# Harness config standard
**Status:** Version 1 — Stable. The file shape, manifest schema, projection
contract, and ignore grammar described here are intended to be implementable
w... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/extensions | en | Extensions | extensions | 03 | 3 | https://www.harnessconfig.dev/specifications/v1/extensions/ | spec/en/03-extensions.md | How declared extensions add registered behavior without expanding the core resource projection schema. | Describes how extensions are declared, versioned, activated, discovered, and kept separate from the core .harness projection model. | # Extensions
Extensions let tools add registered behavior without expanding the core resource and target projection schema. The base standard defines how extension declarations are discovered and when an implementation may run them; each extension owns its own schema, compatibility, diagnostics, planning, and writes.
... | Extensions
How declared extensions add registered behavior without expanding the core resource projection schema.
# Extensions
Extensions let tools add registered behavior without expanding the core resource and target projection schema. The base standard defines how extension declarations are discovered and when an... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/adoption | en | Adoption | adoption | 04 | 4 | https://www.harnessconfig.dev/specifications/v1/adoption/ | spec/en/04-adoption.md | Practical workflows for greenfield setup, migration, profiles, composable instructions, and cleanup. | Covers practical workflows for creating a .harness catalog, declaring targets, previewing activation, migrating harness surfaces, using profile overlays, and keeping target cleanup safe. | # Harness config adoption
This guide describes two paths: greenfield (no existing live agent folders)
and migration (a repository that already has `.claude/`, `.cursor/`,
`.agents/`, or similar).
## Greenfield
Harness config v1 starts from a small source contract:
1. Create `./.harness/harness.toml` with `version =... | Adoption
Practical workflows for greenfield setup, migration, profiles, composable instructions, and cleanup.
# Harness config adoption
This guide describes two paths: greenfield (no existing live agent folders)
and migration (a repository that already has `.claude/`, `.cursor/`,
`.agents/`, or similar).
## Greenfi... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/tooling | en | Tooling | tooling | 05 | 5 | https://www.harnessconfig.dev/specifications/v1/tooling/ | spec/en/05-tooling.md | The npx harnessc standard implementation: validation, profile discovery, planning, activation, and cleanup commands. | Describes tooling expectations for validation, profile overlays, dry-run planning, activation, diagnostics, cleanup, and implementation helpers around .harness. | # Harness config tooling
`npx harnessc` is the standard implementation of Harness config. It exists so
repositories can validate the file shape, preview activation, and materialize
copy projections without writing a custom tool first.
Any other implementation that meets tool conformance is equally valid. The
standard... | Tooling
The npx harnessc standard implementation: validation, profile discovery, planning, activation, and cleanup commands.
# Harness config tooling
`npx harnessc` is the standard implementation of Harness config. It exists so
repositories can validate the file shape, preview activation, and materialize
copy projec... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/conformance | en | Conformance | conformance | 06 | 6 | https://www.harnessconfig.dev/specifications/v1/conformance/ | spec/en/06-conformance.md | Testable claims for repositories, resources, targets, profiles, projections, and tools. | Lists testable conformance expectations for repository shape, resource paths, target projection, overrides, ignore behavior, profile overlays, extensions, and activation output. | # Harness config conformance
A claim of Harness config support should be testable from the file shape and
activation contract alone. A repository, tool, or organization policy may claim
support when the relevant checks below can be reproduced without depending on a
specific runtime, CLI, or hosted service.
## Conform... | Conformance
Testable claims for repositories, resources, targets, profiles, projections, and tools.
# Harness config conformance
A claim of Harness config support should be testable from the file shape and
activation contract alone. A repository, tool, or organization policy may claim
support when the relevant check... | 2094d04869f4137bb0dadc1e977adae35652ce57 |
en/patterns | en | Patterns | patterns | 07 | 7 | https://www.harnessconfig.dev/specifications/v1/patterns/ | spec/en/07-patterns.md | Concrete examples for combining ignores, profiles, dir composition, and cleanup safely. | "Shows practical Harness config patterns for target-output ignores, composable instructions, profile(...TRUNCATED) | "# Harness config Patterns\n\nThis page shows how to combine the standard pieces without losing the (...TRUNCATED) | "Patterns\n\nConcrete examples for combining ignores, profiles, dir composition, and cleanup safely.(...TRUNCATED) | 2094d04869f4137bb0dadc1e977adae35652ce57 |
es/overview | es | Vision general | overview | 00 | 0 | https://www.harnessconfig.dev/specifications/v1/ | spec/es/00-overview.md | Layout fuente, modelo de activacion, controles de proyeccion, perfiles y beneficios operativos. | "Presenta .harness como catalogo fuente del repositorio para configuracion de agentes con activacion(...TRUNCATED) | "# Una capa fuente neutral para superficies de harness\n\nLos harnesses exponen archivos y carpetas (...TRUNCATED) | "Vision general\n\nLayout fuente, modelo de activacion, controles de proyeccion, perfiles y benefici(...TRUNCATED) | 2094d04869f4137bb0dadc1e977adae35652ce57 |
es/rationale | es | Justificacion | rationale | 01 | 1 | https://www.harnessconfig.dev/specifications/v1/rationale/ | spec/es/01-rationale.md | Por que el estandar separa un catalogo fuente durable de superficies de harness vivas. | "Explica por que las superficies de harness deben ser salidas derivadas mientras .harness sigue sien(...TRUNCATED) | "# Justificacion\n\nLos harnesses necesitan superficies vivas en el repositorio. Los equipos necesit(...TRUNCATED) | "Justificacion\n\nPor que el estandar separa un catalogo fuente durable de superficies de harness vi(...TRUNCATED) | 2094d04869f4137bb0dadc1e977adae35652ce57 |
End of preview. Expand in Data Studio
Harness config v1 specification
This dataset is a generated mirror of the Harness config v1 specification for AI agents, retrieval systems, and documentation search.
Canonical source: https://www.harnessconfig.dev/specifications/v1/
Source repository: https://github.com/reachjalil/harness-config
Source commit: 2094d04869f4137bb0dadc1e977adae35652ce57
Harness config is a repository-local standard for keeping reusable AI agent
instructions, skills, rules, plugins, and related configuration in reviewed
source roots, then projecting them into explicit live harness surfaces such as
AGENTS.md, .agents, .claude, .cursor, and .gemini.
Files
spec/: localized markdown specification pages copied from the canonical repository.canonical/: canonical repository docs for the standard, conformance, tooling, adoption, and testing.examples/: small Harness config layouts for agents and retrieval tools.harness-config-v1.jsonl: LLM-friendly section rows with canonical URLs and metadata.harness-config-v1.documents.json: document-level JSON snapshot.metadata.json: generation metadata.
Canonical URL policy
This Hugging Face dataset is a discovery and retrieval mirror. The canonical specification remains at https://www.harnessconfig.dev/specifications/v1/. When citing or linking the standard, prefer the canonical website URL.
- Downloads last month
- 78