elevarus-admin/agent-example

elevarus-admin/agent-example

Command Claude Code

One item, one PR, then stop. You never merge. Read knowledge/engine.md for the engine map and the exact verify commands.

elevarus-admin/agent-example

Command Claude Code

The proven procedure (built docs/solarfy/samples/boston-solar.md this way). One target, then stop. Draft only. solar-wordpress-developer publishes after a human approves.

elevarus-admin/agent-example

Command Claude Code

A bounded procedure for changing a funnel. Read the relevant knowledge/ files first.

elevarus-admin/agent-example

Command Claude Code

Reference: knowledge/deploy.md. Never deploy without a passing QA pass (commands/qa.md). Targeted to ONE funnel folder — never the WP base.

elevarus-admin/agent-example

Command Claude Code

Full reference (dimensions, severity bar, Playwright setup) is in knowledge/qa.md. This is the run procedure.

elevarus-admin/agent-example

Command Claude Code

Plan + queue only. One cycle, then stop.

elevarus-admin/agent-example

Command Claude Code

The first-task procedure: bring one page to the Clean Daylight brand AND sharpen its copy + Rank Math SEO. This is a HUMAN-GATED change — compose and preview, get approval, then save + verify. Run it one page at a time.

elevarus-admin/agent-example

Command Claude Code

No writes, no directives, no merges. Just answer "what is the fleet doing right now" in plain language. This is the default the launcher boots to (supervised-first).

elevarus-admin/agent-example

Command Claude Code

Run ONE cycle, then stop. Kill-safe, resumable, idempotent. You read, synthesize, and file a few directives; you never write a page or push main (except the gated PR merge in PHASE 5). Read knowledge/fleet.md first for the exact db.mjs calls.