har
AGENTS.md133 starsChanged 3 months agoApache-2.0View on GitHub
Astro marketing site + Starlight documentation for HAR (<https://harproject.dev/>). Part of the har monorepo — this app has its own harness (docs/.har/). For the CLI package, Mission Control, or the index of all harnesses, see the root AGENTS.md. This repository uses a .har/ harness. It is how you run and verify this project — launch a slot for live apps, browsers and screenshots; never hand-roll docker or dev-server startup. If a harness command fails, fix the harness or report it;…
- Reads credentials
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- control/AGENTS.mdAGENTS.md
- .cursor/rules/har-workflow.mdcCursor rule
- factory-lineSkill
- new-pluginSkill
- v1-milestoneSkill
The file
Files
HAR docs site — Agent Development Guide
Astro marketing site + Starlight documentation for HAR (https://harproject.dev/).
Part of the har monorepo — this app has its own harness (docs/.har/). For the
CLI package, Mission Control, or the index of all harnesses, see the root
AGENTS.md.
Stack
- Astro 7 + Starlight, React islands, Playwright for browser-e2e / screenshots
- Node.js ≥ 22.12
Layout
src/pages/ landing + blog routes
src/content/docs/ Starlight documentation
src/styles/ landing + Starlight theme
tests/ Playwright (frontend, api, a11y, visual-proof)
.har/ agent harness (launch / verify / screenshots)Agent environment
<!-- har:agent-environment:start -->HAR / agent environment
This repository uses a .har/ harness. It is how you run and verify this
project — launch a slot for live apps, browsers and screenshots; never
hand-roll docker or dev-server startup. If a harness command fails, fix the
harness or report it; do not fall back to ad-hoc commands.
- Launch first —
har_launch_environment/har env launch <id>. Make ALL edits under the returned work dir, never the main checkout. Bind tracker work with--work-id/--work-urlwhen the task names an issue. - Verify before done —
har_run_verification(full: true) /har env verify <id> --full. Commit in the session worktree. - Stop at handoff — report summary, session branch and preview URLs, then
wait. Never autonomously
complete,teardown, push, or open a PR. - All slots taken? Occupied slots always block a launch, and you never free
one yourself. Run
har env status, then show the user every slot — branch, work unit, what it achieves, last verify, and whether its commits are merged, pushed or unpushed — and recommend which to close: merged or abandoned work with nothing left to do first; never one with unpushed commits. On approval:complete/teardown <id>, then launch.
Customize the harness only through harness.env, stages.json + .har/stages/,
.har/hooks/ and .har/plugins/ — there is no generated .har/*.sh entry-point
surface.
Full detail — slot environment, readiness, definition of done, project commands,
commit gate: .har/README.md and .har/stages.json.
<!-- har:agent-environment:end -->Project-specific notes
- Primary app: Astro site (
npm run dev/astro dev) — no database. - Ports: slot 1 defaults to 4321 (see
.har/harness.env); never hardcode. - Screenshots: launch →
.har/artifacts/browser-e2e/screenshots/before/; full verify →…/after/(paths are under the session work dir). - Session handoff: list every after-screenshot PNG from the work dir so UI changes are reviewable.
- Other harnesses: root
.har/(CLI) ·control/.har/(Mission Control).
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
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.

