菜单
Use when working in the harness-config repository on the Harness config v1 standard, conformance rules, specification wording, manifest/resource/dir/profile/ignore semantics, or docs ownership.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when working in the harness-config repository and Codex needs to validate, preview, activate, or explain Harness config dogfooding with the local @harnessconfig/cli package.
Use when migrating an existing repository to Harness config from ad hoc agent instructions, runtime folders, skills, plugins, prompts, commands, hooks, or local agent settings.
Use when working in the harness-config repository on implementation structure, projection architecture, resource and dir composition, target override precedence, profile and ignore integration, or code placement.
Use when working in the harness-config repository on test strategy, regression coverage, fixtures, docs/TESTING.md, CLI end-to-end checks, projection edge cases, profile and ignore scenarios, or focused quality commands.
Use when working with Harness config in a customer repository. Triggers include setting up, adopting, migrating, validating, activating, or troubleshooting .harness/harness.toml, .harness resources, AGENTS.md, CLAUDE.md, .agents, .claude, .cursor, .gemini, skills, rules, plugins, prompts, hooks, .harnessIgnore, .harnessMutable, mutable files, or CLI commands such as npx harnessc validate and npx harnessc activate.
| name | harness-config-specs |
| description | Use when working in the harness-config repository on the Harness config v1 standard, conformance rules, specification wording, manifest/resource/dir/profile/ignore semantics, or docs ownership. |
Use this skill when the task is about the v1 contract: what Harness config means, which behavior is normative, and which docs should carry the wording.
docs/STANDARD.md is the normative contract.docs/CONFORMANCE.md is the testable support checklist.docs/TOOLING.md and package READMEs describe CLI behavior.docs/TESTING.md maps scenarios to tests.Load only the reference needed:
references/docs-ownership.md for doc ownership decisions.references/v1-invariants.md for stable v1 projection rules.Useful checks:
rg -n "harnessProfileRoot|harnessProfileIsolation|harnessIgnore|target.*parent|wildcard|harnessComposable|\\.harnessRef" docs packages
pnpm --filter @harnessconfig/core test
pnpm --filter @harnessconfig/cli test
docs/STANDARD.md.