Scenario 32: Apply to instruction-tier harnesses
Use this when applying a layer to harnesses that load skills as always-on instructions or rules rather than agent-requested skill directories. Harnesses...
Frequency: Occasional · Status: Shipped
Use this when applying a layer to harnesses that load skills as always-on
instructions or rules rather than agent-requested skill directories. Harnesses
with registry skillEmission: instruction-only include windsurf, cline,
github-copilot, gemini-cli, and kiro.
Typical commands:
# Preview per-harness output paths
harnesstap layer apply my-setup --project . --harness windsurf,cline,github-copilot --dry-run
# Apply to instruction-tier harnesses alongside native-skill hosts
harnesstap layer apply my-setup --project . --harness claude-code,codex,windsurf,cursor
# List all harnesses; instruction-tier hosts have skillEmission: instruction-only
harnesstap harness list --format jsonExpected emission paths (instruction-tier hosts):
| Harness | Skills become |
|---|---|
windsurf | .windsurf/rules/{name}.md |
cline | .clinerules/{name}.md (or merged rules file) |
github-copilot | Sections in .github/copilot-instructions.md |
gemini-cli | Rules/instructions per Gemini serializer paths |
kiro | .kiro/steering/{name}.md |
Native-skill hosts (claude-code, codex, cursor with default mode, etc.)
continue to emit .claude/skills/, .agents/skills/, or harness-specific skill
directories.
Cursor cursor_skill_mode
Cursor is not instruction-only by default. Project apply and mirror read
cursor_skill_mode from project harness config and pass it to the serializer
as skillCursorMode:
cursor_skill_mode | Skill output |
|---|---|
agent-requested (default) | .cursor/rules/*.mdc, alwaysApply: false |
always-on | .cursor/rules/*.mdc, alwaysApply: true |
agents-skills | .agents/skills/{name}/SKILL.md |
harnesstap harness project status --project . --format jsonCompare dry-run output across harnesses before writing. See portability limits for intentional per-host tailoring vs hand-tuned adapter copies.
Scenario 31: Import dual-mode plugin repo
Use this when a repository contains both harness project files (for example AGENTS.md, CLAUDE.md) and a plugin manifest at the repo root (for example...
Scenario 33: Mirror with plugin-source fallback
Use this when mirror would fail because the project's main harness has no on-disk resource tree — common in plugin-only repos that ship...