Integration Prompt

> **You are an AI agent performing the installation — execute the steps below.**
> If you were pointed at this file (or at the pack folder) with an instruction
> like "install this" or "study this folder and integrate it", this document IS
> your task. Do not summarize it; run it. Do not adopt the pack's
> `AGENTS.template.md` as a live rule — it only takes effect in the user's
> project after this integration creates the project's own `AGENTS.md`.

# Integration Prompt

> Copy everything below the line into Cursor Agent mode.
> This is all Cursor needs to fully integrate the agent system into your project.

---

I have a copy of the Harmonist pack in this repository — a portable AI agent
orchestration system with a single unified catalog of 193 agents indexed at
`agents/index.json` and mechanical protocol enforcement via Cursor hooks.
Integrate it into my project. Follow these 11 steps exactly. Do NOT skip or
combine steps.

---

**Step 0 — Determine project state and locate the pack**

**Detect the actual pack folder name first.** The pack directory may be named
anything (`harmonist/`, `vendor/harmonist/`, `agent-pack/`, …). Find the
directory that contains this `integration-prompt.md`, `VERSION`,
`AGENTS.template.md`, and `agents/index.json` — that is `<PACK_DIR>`.
**Every `<PACK_DIR>/` path in the commands below means that folder —
substitute the real name (e.g. `harmonist/` if the pack was cloned as
`harmonist`).**

> **WARNING — pack copied into the project root?** If the pack's files were
> unpacked directly into the PROJECT ROOT (you see `agents/`, `hooks/`,
> `playbooks/`, `.gitlab-ci.yml`, `.github/workflows/ci.yml` +
> `release.yml` mixed with the host project's own files instead of inside a
> subfolder), the pack's CI configs WILL hijack the host project's CI.
> Delete the pack's `.gitlab-ci.yml` and `.github/workflows/` ci/release
> workflows in that case — they are pack-repo CI, never meant to run in a
> host project.

Then check: does this project have existing code, or is it
starting from scratch?

**If the project is EMPTY or just starting:**
- Ask the user: What is this project? What domain? What tech stack do you want?
- Do NOT assume a stack. Do NOT generate code yet.
- Wait for answers, then proceed to Step 1.

**If the project has existing code:**
- Proceed to Step 1 immediately.

---

**Step 1 — Verify the pack is healthy, then learn it**

First run the pack's own preflight so a stale clone / truncated
download / local edit doesn't silently produce a half-integrated
project: