NeogenuityNeogenuity/harness-kit/.cursor/rules/templates.mdc

harness-kit / rules

Cursor rule0 starsChanged 4 months agoMITView on GitHub

Rules for editing the mechanism templates harness-kit ships into other repos

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- llms.txtllms.txt
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- doc-gardenSkill
- releaseSkill
- verify-liveSkill

The file

We split this templates.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Follow the conventions documented in docs/standards/templates.md.
line 9
Very specific:
Every new or changed guard hook ships with a test-<name>.sh beside it
line 12

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

templates.mdc

---
description: Rules for editing the mechanism templates harness-kit ships into other repos
globs:
  - "plugins/harness-kit/skills/harness-kit/templates/**"
---

# Shipped-template discipline

Follow the conventions documented in `docs/standards/templates.md`.

Key points:
- Every new or changed guard hook ships with a `test-<name>.sh` beside it
- Hooks fail open (exit 0 on missing deps/unknown payloads); denial is exit 2 via `hook_deny`
- Customization points live in marked TAILOR blocks or `harness.conf` — never in mechanism lines
- Provider-matrix facts carry a `verified YYYY-MM` stamp naming a primary source
- Mechanism behavior changes bump `plugins/harness-kit/.claude-plugin/plugin.json` before release

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free